[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [xmlblaster-devel] Webservice XMLBlaster subscriber can't rec eive messages
Heinrich,
We discovered that the problem was Xerces itself. Evidentally
xmlBlaster perfers Crimson for all XML parsing. However, it is set up such
that changing two system properties can change the parser. When parser.jar
is loaded, those system properties are set to specify Crimson as the SAX
parser.
However, Tomcat itself prefers Xerces to be the XML parser. When
xerces.jar is loaded, the system properties are set up to specify Xerces as
the SAX parser. We are also using Axis as part of our webservices, and that
prefers Xerces as well.
Here's the problem. When parser.jar is loaded first, Crimson is
specified as the SAX parser and either Tomcat or Axis breaks. However, when
Xerces.jar is loaded first, Xerces is specified as the SAX parser and
xmlBlaster throws the StopParseException.
Evidentally there are two solutions to this problem. One is to set
up Tomcat to run xmlBlaster in a completely separate realm from everything
else. Another is to specify in the subscriber client that Crimson is to be
the SAX parser by changing the system property in the code. The first is
the correct way to do it, the second is a quick-and-dirty solution to the
problem.
Thanks for your help.
Tom
-----Original Message-----
From: Heinrich Götzger [mailto:goetzger at gmx.net]
Sent: Wednesday, June 12, 2002 15:05
To: xmlBlaster-devel
Subject: RE: [xmlblaster-devel] Webservice XMLBlaster subscriber can't
rec eive messages
Tom,
But I would check why the Callback Server is loosing connection and is it
loosing connection because of the SAX-Error or vice versa?
How about ORBS?
Do you have different ORB's in the same VM?
xmlBlaster uses jacorb.
What if you switch of Corba for xmlBlaster and use some other
communication protocol? RMI or XML-RPC for example, just to see what
happens.
Hope this helps a bit.
regards
Heinrich
--
http://www.xmlBlaster.org
On Wed, 12 Jun 2002, Potts, Tom wrote:
>Heinrich,
>
>That was one of our first thoughts. We tracked through our classpath and
>got rid of all XML-Parsers except for Xerces, which is required for another
>project we have running on the same server.
>
>We've also tried rebuilding XMLBlaster with that version of Xerces instead
>of the version that is supplied with XMLBlaster, but had no luck with that
>either.
>
>Thanks,
>
>Tom
>
>-----Original Message-----
>From: Heinrich Götzger [mailto:goetzger at gmx.net]
>Sent: Wednesday, June 12, 2002 14:09
>To: xmlBlaster-devel
>Subject: Re: [xmlblaster-devel] Webservice XMLBlaster subscriber can't
>receive messages
>
>
>Tom,
>
>may it be the case that you have two concurrent XML-Parsers in the same
>VM?
>How's your $CLASSSPATH looking?
>
>regards
>
>Heinrich
>--
>http://www.xmlBlaster.org
>
>On Wed, 12 Jun 2002, Potts, Tom wrote:
>
>>Hi all,
>>
>> We're using XMLBlaster in a web-services based project. We've been
>>able to successfully publish and subscribe using the system. However,
>>whenever a message is sent to the subscriber, a StopParseException is
>thrown
>>and the below messages are displayed.
>>
>> We believe the SAX Parser is having a problem parsing the Key, but
>>we can't track down why. The same message is received fine by
>>non-webservices subscribers. We're using Tomcat 4.0.3 as our webserver.
>>
>> Anyone have any ideas?
>>
>>Server Side Message:
>>
>>[Jun 12, 2002 1:15:18 PM INFO Authenticate] Successful login for client
>>guest, session:3 expires after [ 24 h 0 millis ], 2 of 10 sessions are in
>>use.
>>[Jun 12, 2002 1:15:18 PM INFO XmlKeyDom] 0 MessageUnits matched to
>>subscription "/xmlBlaster/key/ClientSub-AGENT"
>>[Jun 12, 2002 1:15:24 PM INFO XmlKey] XPath subscription
>>'/xmlBlaster/key/ClientSub-AGENT' matches message
>>'http://10.0.1.34:3412-1023902124046-2'
>>[ New connection to 10.0.1.34:3674 ]
>>[Jun 12, 2002 1:15:24 PM WARN CbConnection-session:3] Callback transition
>>IS_ALIVE -> IS_DEAD: Callback server of client guest is unaccessible.
>>[Jun 12, 2002 1:15:24 PM WARN MsgQueue:session:3] Callback server is
lost,
>>killing login session of client guest.
>>[Jun 12, 2002 1:15:24 PM INFO Authenticate] Disconnecting client guest,
>>instanceId=3, sessionId=IIOP:0110472D181503282B47
>>[Jun 12, 2002 1:15:24 PM INFO Authenticate] loginNameSubjectInfoMap has 2
>>entries and sessionInfoMap has 2 entries
>>[Jun 12, 2002 1:15:24 PM WARN CbWorker:session:3] Callback failed:
>>id=CallbackFailed reason=CORBA Callback of 1 messages
>>'http://10.0.1.34:3412-1023902124046-2' to client [unknown] from [guest]
>>failed.
>>Exception thrown by client: id=Parsing Error reason=check the key
>>passedid=SaxHandlerBase reason=Error while SAX parsing:
>>org.apache.xerces.readers.DefaultEntityHandler at 5ff916:
>>org.xmlBlaster.util.StopParseException
>>
>>
>> <key oid="http://10.0.1.34:3412-1023902124046-2";
contentMime="text/xml">
>>
>> <ClientSub-AGENT id="192.168.124.10" subId="1" type="generic">
>> <ClientSub-DRIVER id="FileProof" pollingFreq="10">
>></ClientSub-DRIVER>
>> </ClientSub-AGENT>
>> </key>
>>
>>[Jun 12, 2002 1:15:24 PM WARN MsgQueue:session:3] The queue is shutdown,
>>putMsgs() of 1 messages failed, starting error handling ...
>>[Jun 12, 2002 1:15:24 PM WARN RequestBroker-http://10.0.1.34:3412]
>>Generating dead letter oid=http://10.0.1.34:3412-1023902124046-2 from
>>publisher=guest because delivery to 'guest' cbQueue=session:3 failed.
>>[Jun 12, 2002 1:15:24 PM WARN MsgQueue:session:3] Lost callback
connection
>>for session:3 errorCounter=1
>>
>>
>>
>>
>>Client Side Message:
>>
>>[Jun 12, 2002 1:15:24 PM ERROR SaxHandlerBase] Error while SAX parsing:
>>org.apache.xerces.readers.DefaultEntityHandler at 5ff916:
>>org.xmlBlaster.util.StopParseException
>>
>>
>> <key oid="http://10.0.1.34:3412-1023902124046-2";
contentMime="text/xml">
>>
>> <ClientSub-AGENT id="192.168.124.10" subId="1" type="generic">
>> <ClientSub-DRIVER id="FileProof" pollingFreq="10">
>></ClientSub-DRIVER>
>> </ClientSub-AGENT>
>> </key>
>>
>>org.xmlBlaster.util.StopParseException
>> at
org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1111)
>> at
org.xmlBlaster.util.SaxHandlerBase.parse(SaxHandlerBase.java:93)
>> at org.xmlBlaster.util.SaxHandlerBase.init(SaxHandlerBase.java:70)
>> at org.xmlBlaster.client.UpdateKey.<init>(UpdateKey.java:73)
>> at
>>org.xmlBlaster.client.protocol.AbstractCallbackExtended.update(AbstractCal
l
>b
>>ackExtended.java:71)
>> at
>>org.xmlBlaster.client.protocol.AbstractCallbackExtended.update(AbstractCal
l
>b
>>ackExtended.java:132)
>> at
>>org.xmlBlaster.client.protocol.corba.CorbaCallbackServer.update(CorbaCallb
a
>c
>>kServer.java:243)
>> at
>>org.xmlBlaster.protocol.corba.clientIdl.BlasterCallbackPOATie.update(Blast
e
>r
>>CallbackPOATie.java:52)
>> at
>>org.xmlBlaster.protocol.corba.clientIdl.BlasterCallbackPOA._invoke(Blaster
C
>a
>>llbackPOA.java:61)
>> at
>>org.jacorb.poa.RequestProcessor.invokeOperation(RequestProcessor.java:207)
>> at
>>org.jacorb.poa.RequestProcessor.process(RequestProcessor.java:404)
>> at org.jacorb.poa.RequestProcessor.run(RequestProcessor.java:513)
>>[Jun 12, 2002 1:15:24 PM ERROR AbstractCallbackExtended.update] Parsing
>>error: id=SaxHandlerBase reason=Error while SAX parsing:
>>org.apache.xerces.readers.DefaultEntityHandler at 5ff916:
>>org.xmlBlaster.util.StopParseException
>>
>>
>> <key oid="http://10.0.1.34:3412-1023902124046-2";
contentMime="text/xml">
>>
>> <ClientSub-AGENT id="192.168.124.10" subId="1" type="generic">
>> <ClientSub-DRIVER id="FileProof" pollingFreq="10">
>></ClientSub-DRIVER>
>> </ClientSub-AGENT>
>> </key>
>>
>>[Jun 12, 2002 1:15:24 PM ERROR CorbaCallbackServer-guest] Delivering
>message
>>to client failed, message is lost.
>>
>