[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xmlblaster] Problem with GET with <history numEntries='5'>

Giambattista Saldi wrote: 
I'm trying Xmlblaster with TCP socket in C
XmlBlaster 0.85b


Hi Giamba,


I'm interesting in message history
i publish with queue history and work fine, but in subscibe or in get like
this

key = "<key oid='HelloWorld'/>";
qos = "<qos><history numEntries='5'> <qos/>";


This is not well formed XML, please add a '/' like this:

"<qos><history numEntries='5' /> <qos/>"

msg = xa.get(xa, key, qos, &xmlBlasterExcp);

get the following exception, in the client:

Caught exception during GET errorCode=resource.configuration
message=XmlBlasterException errorCode=[resource.configuration]
serverSideException=true node=[xmlBlaster_192_168_100_20_3412]
location=[SaxHandlerBase.parse()] message=[Error while SAX parsing: :1:-1:
org.xml.sax.InputSource at 4c47db : org.xml.sax.SAXParseException:
org.apache.crimson.parser/P-035]

and this is the console output in xmblaster server (running with default
configuration  java -jar lib/xmlBlaster.jar -cluster false)

[10-ott-03 14.29.54 ERROR SaxHandlerBase.fatalError] :1:-1:
org.apache.crimson.p
arser/P-035
<qos><history numEntries='5'> <qos/>
org.xml.sax.SAXParseException: org.apache.crimson.parser/P-035
        at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3030)
        at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3018)
        at org.apache.crimson.parser.Parser2.content(Parser2.java:1753)
        at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1461)
        at org.apache.crimson.parser.Parser2.content(Parser2.java:1695)
        at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1461)
        at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:499)
        at org.apache.crimson.parser.Parser2.parse(Parser2.java:304)
        at
org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)

        at org.xmlBlaster.util.SaxHandlerBase.parse(SaxHandlerBase.java:146)
        at org.xmlBlaster.util.SaxHandlerBase.parse(SaxHandlerBase.java:110)
        at org.xmlBlaster.util.SaxHandlerBase.init(SaxHandlerBase.java:93)
        at
org.xmlBlaster.util.qos.QueryQosSaxFactory.readObject(QueryQosSaxFact
ory.java:86)
        at
org.xmlBlaster.engine.qos.GetQosServer.<init>(GetQosServer.java:50)
        at org.xmlBlaster.engine.XmlBlasterImpl.get(XmlBlasterImpl.java:342)
        at
org.xmlBlaster.protocol.socket.Executor.receive(Executor.java:301)
        at
org.xmlBlaster.protocol.socket.HandleClient.run(HandleClient.java:206
)
        at java.lang.Thread.run(Unknown Source)


There is also a problem with unsubscribe topic
if i do 2 time the unsubribe commmand on the same topic

key = "<key oid='HelloWorld'/>";
qos = "<qos/>";
response = xa.unSubscribe(xa, key, qos, &xmlBlasterExcp);

the second time the program is blocked and get the following exception :
Caught exception during unsubscibe errorCode=resource.exhaust
message=[C:\mom\XMLBLA~2\src\c\socket\XmlBlasterAccessUnparsed.c:345]
Waiting on response for 'unSubscribe()' with requestId=6 timed out after
blocking 60000 millis

The second unsubscribe is an errore because i have already unsubcribed the
topic, but
blocking the program for 1 min. i think is not a correct answare.


No, this looks like a bug,

thanks for reporting,

best regards

Marcel 

Thank's in advance
Giamba







--
http://www.xmlBlaster.org