Hi, You will have to check two things:
1) Does the remote service honor the ReplyTo JMS header, or does it put the response to a predefined queue? 2) Does the remote service correctly set the correlation ID in the response message. Andreas On Fri, Dec 19, 2008 at 13:11, Java Programmer <[email protected]> wrote: > Hi, > I am using proxy for recieving data from external site with help of > JMS queue - everything work till sending to remote site (without JMS > this scenario work, when adding JMS support stops with message: > 2008-12-19 12:24:06,843 [192.168.3.36-main-36] [SynapseWorker-2] WARN > JMSSender Did not receive a JMS response within 30000 ms to > destination : temp-queue://ID:main-36-3190-122968 > 5810109-0:3:1 with JMS correlation ID : > ID:main-36-3190-1229685810109-0:3:1:1:1 > > The code for proxy: > <proxy name="FlightsProxy" trace="enable" transports="jms"> > <target> > <inSequence> > <!-- this log works --> > <log level="custom"> > <property name="text" expression="child::*" /> > </log> > <send> > <endpoint> > <address uri="http://remote.site.com/"; format="pox"/> > </endpoint> > </send> > </inSequence> > <outSequence> > <!-- this log DOESN'T work --> > <log level="custom"> > <property name="text" expression="child::*" /> > </log> > <send/> > </outSequence> > </target> > </proxy> > > Can anybody help, or give an example of such scenario when JMS is > transport and remote webservice site is an endpoint, and response from > it should get into JMS queue again? > Best regards, > Adr >
