You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@synapse.apache.org by kbohnenberger <ke...@mantech.com> on 2009/04/21 00:38:54 UTC
jms proxy problem with snapshot build
I'm listening to a queue using the proxy jms transport like this:
<proxy name="queueListener1" transports="jms">
<target>
<inSequence>
<property action="set" name="OUT_ONLY" value="true"/>
<sequence key="sequences/receiveJmsKosList.xml"/>
</inSequence>
</target>
<parameter name="transport.jms.ContentType">
<rules>
<jmsProperty>contentType</jmsProperty>
<default>application/xml</default>
</rules>
</parameter>
<parameter
name="transport.jms.ConnectionFactory">incomingQueueFactory</parameter>
<parameter
name="transport.jms.Destination">cn=incomingQueue</parameter>
</proxy>
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?
Thanks
Keith
--
View this message in context: http://www.nabble.com/jms-proxy-problem-with-snapshot-build-tp23145941p23145941.html
Sent from the Synapse - User mailing list archive at Nabble.com.
Re: jms proxy problem with snapshot build
Posted by Andreas Veithen <an...@gmail.com>.
FYI: Since the JMS transport is built on AbstractTransportListener,
recent snapshots would be impacted by the issue described in
WSCOMMONS-466/SYNAPSE-542. This might explain why the transport is
malfunctioning in such a catastrophic way.
Andreas
On Tue, Apr 21, 2009 at 20:04, Asankha C. Perera <as...@apache.org> wrote:
> Hi Keith
>>
>> Sorry for the confusion. The message should read:
>>
>> I pulled SNAPSHOT build 608.
>> I publish 40 messages to my "incoming queue" before I start Synapse.
>> When I start Syanpse, I no longer see the "FATAL synapse is not
>> initialized"
>> problems that I was seeing with a previous snapshot build. However it
>> takes
>> an insanely long time to process the messages. Only 19 of the 40 messages
>> got processed and it took about 20 minutes. The other 21 messages got
>> dropped on the floor somewhere.
>>
>
> Do you know what is responsible for the delays? i.e. waiting for backend
> messages that never arrive?? Can you attach your synapse.xml and axis2.xml
> and a brief description of the problem you are trying to solve and the
> overview of the configuration you have thus implemented?
>>
>> The other problem that I see is that is seems to pull all the messages off
>> the incoming queue into memory as soon as Synapse comes up. So Synapse
>> comes up, I see my 40 messages get removed from the "incoming queue." At
>> this point the messages seem to be in memory and are getting processed by
>> Synapse. If synapse would go down all the messages in memory would be
>> lost
>> because they were already ripped off the incoming queue.
>>
>
> Are you reading messages transactionally?
>>
>> A further problem I am having is that in my sequence flow the messages end
>> up getting cloned to 6 sequences. The cloning loses a bunch of messages.
>> In the synapse.log, I see "... 1 of 6..." 40 times but then I only see "2
>> of
>> 6" and 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.
>>
>
> Hmm.. this would need further analysis..
>>
>> 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)
>>
>
> Seems like you are encountering faults, and the fault sequence is not
> found.. sharing the resources I asked for could be helpful. Please remove
> any passwords etc before posting these publicly
>
> cheers
> asankha
>
> --
> Asankha C. Perera
> AdroitLogic, http://adroitlogic.org
>
> http://esbmagic.blogspot.com
>
>
>
>
>
Re: jms proxy problem with snapshot build
Posted by "Asankha C. Perera" <as...@apache.org>.
Hi Keith
> Sorry for the confusion. The message should read:
>
> I pulled SNAPSHOT build 608.
> I publish 40 messages to my "incoming queue" before I start Synapse.
> When I start Syanpse, I no longer see the "FATAL synapse is not initialized"
> problems that I was seeing with a previous snapshot build. However it takes
> an insanely long time to process the messages. Only 19 of the 40 messages
> got processed and it took about 20 minutes. The other 21 messages got
> dropped on the floor somewhere.
>
Do you know what is responsible for the delays? i.e. waiting for backend
messages that never arrive?? Can you attach your synapse.xml and
axis2.xml and a brief description of the problem you are trying to solve
and the overview of the configuration you have thus implemented?
> The other problem that I see is that is seems to pull all the messages off
> the incoming queue into memory as soon as Synapse comes up. So Synapse
> comes up, I see my 40 messages get removed from the "incoming queue." At
> this point the messages seem to be in memory and are getting processed by
> Synapse. If synapse would go down all the messages in memory would be lost
> because they were already ripped off the incoming queue.
>
Are you reading messages transactionally?
> A further problem I am having is that in my sequence flow the messages end
> up getting cloned to 6 sequences. The cloning loses a bunch of messages.
> In the synapse.log, I see "... 1 of 6..." 40 times but then I only see "2 of
> 6" and 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.
>
Hmm.. this would need further analysis..
> 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)
>
Seems like you are encountering faults, and the fault sequence is not
found.. sharing the resources I asked for could be helpful. Please
remove any passwords etc before posting these publicly
cheers
asankha
--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org
http://esbmagic.blogspot.com
Re: jms proxy problem with snapshot build
Posted by Keith Bohnenberger <ke...@mantech.com>.
Sorry for the confusion. The message should read:
I pulled SNAPSHOT build 608.
I publish 40 messages to my "incoming queue" before I start Synapse.
When I start Syanpse, I no longer see the "FATAL synapse is not initialized"
problems that I was seeing with a previous snapshot build. However it takes
an insanely long time to process the messages. Only 19 of the 40 messages
got processed and it took about 20 minutes. The other 21 messages got
dropped on the floor somewhere.
The other problem that I see is that is seems to pull all the messages off
the incoming queue into memory as soon as Synapse comes up. So Synapse
comes up, I see my 40 messages get removed from the "incoming queue." At
this point the messages seem to be in memory and are getting processed by
Synapse. 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 am having is that in my sequence flow the messages end
up getting cloned to 6 sequences. The cloning loses a bunch of messages.
In the synapse.log, I see "... 1 of 6..." 40 times but then I only see "2 of
6" and 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:40 PM, "Asankha C. Perera" <as...@apache.org> wrote:
> Hi Keith
>> Sorry, I didn't clean that email up properly. Please disregard the "Now I'm
>> not getting any messages at all." At first that was the case but then I
>> figured out that the axis2.xml file changed from the build I had to the 608
>> build.
>>
> Does this mean you are all set? If not, please shout out..
>
> cheers
> asankha
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.
Re: jms proxy problem with snapshot build
Posted by "Asankha C. Perera" <as...@apache.org>.
Hi Keith
> Sorry, I didn't clean that email up properly. Please disregard the "Now I'm
> not getting any messages at all." At first that was the case but then I
> figured out that the axis2.xml file changed from the build I had to the 608
> build.
>
Does this mean you are all set? If not, please shout out..
cheers
asankha
--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org
http://esbmagic.blogspot.com
Re: jms proxy problem with snapshot build
Posted by Keith Bohnenberger <ke...@mantech.com>.
Sorry, I didn't clean that email up properly. Please disregard the "Now I'm
not getting any messages at all." At first that was the case but then I
figured out that the axis2.xml file changed from the build I had to the 608
build.
On 4/21/09 12:04 PM, "Keith Bohnenberger" <ke...@mantech.com>
wrote:
>
> 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" <ru...@gmail.com> 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 <as...@apache.org>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.
>
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.
Re: jms proxy problem with snapshot build
Posted by Keith Bohnenberger <ke...@mantech.com>.
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" <ru...@gmail.com> 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 <as...@apache.org>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.
Re: jms proxy problem with snapshot build
Posted by Ruwan Linton <ru...@gmail.com>.
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 <as...@apache.org>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: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com
Re: jms proxy problem with snapshot build
Posted by "Asankha C. Perera" <as...@apache.org>.
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