synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Upul Godage (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SYNAPSE-254) Unable to send responses to new JMS queues since new queues are not created properly
Date Fri, 04 Apr 2008 08:33:24 GMT

    [ https://issues.apache.org/jira/browse/SYNAPSE-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585444#action_12585444
] 

Upul Godage commented on SYNAPSE-254:
-------------------------------------

Fixed jms reply destination setting. Also in the jms: url you can give the reply destination
as "transport.jms.ReplyDestination=Name"

Changing to a different protocol To address using the <header /> only does not work
may be because the underlying transportOut is still is the old one. Instead you can archieve
this as follows.

<out>
               <send>
                 <endpoint>
                   <address uri="jms:/dynamicQueues/NewQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&amp;java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&amp;java.naming.provider.url=tcp://localhost:61616&amp;transport.jms.DestinationType=queue"/>
                 </endpoint>
              </send>
</out>

> 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&amp;java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&amp;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&amp;java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&amp;java.naming.provider.url=tcp://localhost:61616&amp;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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


Mime
View raw message