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 > > > > > -- Ruwan Linton Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: [email protected]; cell: +94 77 341 3097 blog: http://ruwansblog.blogspot.com
