[
https://issues.apache.org/jira/browse/SYNAPSE-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evanthika Amarasiri closed SYNAPSE-254.
---------------------------------------
Tested on synapse1.2. The response is received to the client when the following
configuration was used. The issue will be closed
<definitions xmlns="http://ws.apache.org/ns/synapse";>
<sequence name="jms_sequence">
<in>
<property name="OUT_ONLY" value="true"/>
<send>
<endpoint>
<address
uri="jms:/Adding?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616"/>
</endpoint>
</send>
</in>
<out>
<send>
<endpoint>
<address
uri="jms:/dynamicQueues/NewQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616&transport.jms.DestinationType=queue"/>
</endpoint>
</send>
</out>
</sequence>
</definitions>
> Unable to send responses to new JMS queues since new queues are not created
> properly
> ------------------------------------------------------------------------------------
>
> Key: SYNAPSE-254
> URL: https://issues.apache.org/jira/browse/SYNAPSE-254
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: 1.1.1
> Environment: Ubuntu7.04, JDK1.5.0_14
> Reporter: Evanthika Amarasiri
> Assignee: Upul Godage
> Fix For: 1.2
>
>
> Created a configuration as follows where a request message is taken in and
> sent to a JMS endpoint and the response is being pointed to a new queue (and
> not the same queue) which is created by specifying it in the out mediator.
> The configuration is as follows.
> **************************************************************************************************
> <syn:sequence name="jms_sequence">
> <syn:in>
> <syn:property name="OUT_ONLY" value="true"/>
> <syn:send>
> <syn:endpoint>
> <syn:address
> uri="jms:/Adding?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616"/>
> </syn:endpoint>
> </syn:send>
> </syn:in>
> <syn:out>
> <syn:header name="To"
> value="jms:/NewAddingQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616&transport.jms.DestinationType=queue"/>
> <syn:send/>
> </syn:out>
> </syn:sequence>
> **************************************************************************************************
> When a request is sent a JMS queue will be created by the name Adding and
> then the response will be written to a temp queue. Instead the response in
> the above configuration is directed to a new JMS queue by specifying it in
> the out mediator. But it seems that a new queue is not created as expected
> and the client did not receive the response as well
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
