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

RE: [xmlblaster-devel] Webservice XMLBlaster subscriber can't rec eive messages

To: xmlBlaster-devel <xmlblaster-devel at server.xmlblaster.org>
Subject: RE: [xmlblaster-devel] Webservice XMLBlaster subscriber can't rec eive messages
From: Heinrich Götzger <goetzger at gmx.net>
Date: Wed, 12 Jun 2002 21:05:22 +0200 (MEST)
In-reply-to: <69230B2D239ED311BEC700C00D01199DC3433A at ns1.progeny.net>
Reply-to: xmlblaster-devel at server.xmlBlaster.org
Sender: owner-xmlblaster-devel at server.xmlBlaster.org

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(AbstractCall
>b
>>ackExtended.java:71)
>>        at
>>org.xmlBlaster.client.protocol.AbstractCallbackExtended.update(AbstractCall
>b
>>ackExtended.java:132)
>>        at
>>org.xmlBlaster.client.protocol.corba.CorbaCallbackServer.update(CorbaCallba
>c
>>kServer.java:243)
>>        at
>>org.xmlBlaster.protocol.corba.clientIdl.BlasterCallbackPOATie.update(Blaste
>r
>>CallbackPOATie.java:52)
>>        at
>>org.xmlBlaster.protocol.corba.clientIdl.BlasterCallbackPOA._invoke(BlasterC
>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.
>>
>

References:
- RE: [xmlblaster-devel] Webservice XMLBlaster subscriber can't rec eive messages
  - From: "Potts, Tom" <tom.potts at progeny.net>

Prev by Date: RE: [xmlblaster-devel] Webservice XMLBlaster subscriber can't rec eive messages
Next by Date: RE: [xmlblaster-devel] Webservice XMLBlaster subscriber can't rec eive messages
Previous by thread: RE: [xmlblaster-devel] Webservice XMLBlaster subscriber can't rec eive messages
Next by thread: RE: [xmlblaster-devel] Webservice XMLBlaster subscriber can't rec eive messages
Index(es):
- Date
- Thread