Ruwan, I pulled build 608. Now I'm not getting any messages at all. There are messages on my "incoming queue" now but it takes an insanely long time to pull in 40 messages that were on the queue before I started synapse. The other problem that I see is that is seems to pull all the messages off the incoming queue into memory as it processes them. If synapse would go down all the messages in memory would be lost because they were already ripped off the incoming queue. A further problem I having is that in my flow the messages end up getting cloned to 6 sequences. The cloning loses a bunch of messages. I see "... 1 of 6..." 40 times but then I only see "2 of 6" so on 19 times. I don't see any errors it just seems that the cloning isn't happening as much as it should and I lose messages.
Also, can someone shed some light on what the ..../repository/fault should be. I get this error in the synpase.log 2009-04-21 09:41:22,342 [-] [main] DEBUG SynapseConfigUtils Can not open a connection to the URL with a path :file:./repository/fault 2009-04-21 09:41:22,342 [-] [main] DEBUG SynapseConfigUtils Trying to resolve an absolute path of the URL using the synapse.home : /opt/ads/icdl/synapseMediators/dist/synapse-icdl 2009-04-21 09:41:22,343 [-] [main] DEBUG SynapseConfigUtils Failed to resolve an absolute path of the URL using the synapse.home : /opt/ads/icdl/synapseMediators/dist/synapse-icdl 2009-04-21 09:41:22,343 [-] [main] WARN SynapseConfigUtils IO Error reading from URL : /opt/ads/icdl/synapseMediators/dist/synapse-icdl/./repository/faultjava.io.F ileNotFoundException: /opt/ads/icdl/synapseMediators/dist/synapse-icdl/./repository/fault (No such file or directory) On 4/21/09 1:44 AM, "Ruwan Linton" <[email protected]> wrote: > Yes Asankha this should be fixed now. > > Keith, can you please verify this over a latest SNAPSHOT..., > > Thanks, > Ruwan > > On Tue, Apr 21, 2009 at 8:29 AM, Asankha C. Perera <[email protected]>wrote: > >> Hi Ruwan >> >>> If there are already messages on the "incoming queue" before I bring >>> synapse >>> up I lose messages. It seems that as synapse comes up, my proxy above >>> will >>> start receiving messages but synapse is not all the way up yet so I get >>> the >>> following messages in the log: >>> 2009-04-20 18:14:52,883 [-] [jms-Worker-1] DEBUG >>> ProxyServiceMessageReceiver >>> Proxy Service queueListener3 received a new message... >>> 2009-04-20 18:14:52,883 [-] [jms-Worker-1] DEBUG >>> ProxyServiceMessageReceiver >>> Message To: null >>> 2009-04-20 18:14:52,883 [-] [jms-Worker-1] DEBUG >>> ProxyServiceMessageReceiver >>> SOAPAction: urn:mediate >>> 2009-04-20 18:14:52,883 [-] [jms-Worker-1] DEBUG >>> ProxyServiceMessageReceiver >>> WSA-Action: urn:mediate >>> 2009-04-20 18:14:52,883 [-] [jms-Worker-1] FATAL >>> MessageContextCreatorForAxis2 Synapse environment has not initialized >>> properly.. >>> >>> Can someone point me in the right direction so I can have that "FATAL" >>> exception thrown back to the jms server so my message doesn't get dropped >>> on >>> the floor? >>> >>> Is there any other configuration item I can set to force the jms proxy to >>> not "listen" until synapse is all the way up? >>> >>> >> I believe this is a temporary issue which should have been resolved with >> the correct startup order changes? .. or is this a bug that slipped through? >> >> Keith - from your pov, this is a bug which we will handle for the 1.3 >> release. >> >> cheers >> asankha >> >> -- >> Asankha C. Perera >> AdroitLogic, http://adroitlogic.org >> >> http://esbmagic.blogspot.com >> >> >> >> >> > This communication, along with any attachments, is covered by federal and state law governing electronic communications and may contain company proprietary and legally privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, use or copying of this message is strictly prohibited. If you have received this in error, please reply immediately to the sender and delete this message. Thank you.
