Marcel, i cant seem to be able to reproduce the same behaviour again under the extended logging conditions, and i cant seem to be able to reproduce it either in another app that does the same thing... i'll keep you informed if anything shows up again (hope i will have the needed logs at that time). thanks so far.
r Radu Maierean JamboTECH phone: 818-676-3452 email: [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marcel Ruff Sent: Sunday, December 05, 2004 11:59 PM To: [EMAIL PROTECTED] Subject: Re: [xmlblaster] publishing a message for a subscriber that doesnt run Radu Maierean wrote: > hi there, Hi, could you please send me (to [EMAIL PROTECTED]) the err.log file of java org.xmlBlaster.Main -dump[socket] true -call[core] true -call[dispatch] true -logFile err.log -logDevice file,console when the problem occurs? It should contain the login sequences of A and B and the publishes and subscribes when the error happens, thanks Marcel > > i'm pretty sure this is about my lack of understanding about how > XMLblaster messages work, but i cant figure it out at all. here's what > happens. > > in my environment, application A (which is a publisher) needs to send > some commands to application B (which is a subscriber); application B > should respond with a ptp message back to A upon executing the > command. when it is first started, application A needs to make sure > that application B is alive, therefore it goes into a loop and posts > dummy commands for application B, every 3 seconds, until it gets a > response. these dummy messages are sent with the following <qos> tag: > <qos><expiration lifetime="3000"/></qos> (i also tried adding the > <forceUpdate>false</forceUpdate> with the same results). B subscribes > to the messages published by A with the following > <qos>: > <qos> > <persistent/> > <multiSubscribe>false</multiSubscribe> > <initialUpdate>false</initialUpdate> > <local>false</local> > </qos> > (again, i also tried adding a <history numEntries='20' > newestFirst='true'/> - same results). > > everything is fine if application B is already started when A starts - > a response is sent back from B to A, and A breaks off that loop and > enters normal operation. however, if A (the publisher) starts before > B, a lot of times B doesnt seem to receive the messages published by A > (i can say this since B would log every single message that it > receives). again - sometimes it does receive them, sometimes it doesnt > - and i cant understand why this is happening. both my apps are > written with the C sockets library. > > can anybody help with an advice to make this work consistently?... > thanks. (let me know if more information is needed from me.) > > > Radu Maierean > JamboTECH > phone: 818-676-3452 > email: [EMAIL PROTECTED] > > -- http://www.xmlBlaster.org
