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.
