[jira] Updated: (LINGO-3) Specify Response Queue

     [ http://jira.codehaus.org/browse/LINGO-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

mario losilo updated LINGO-3:
-----------------------------

    Attachment: hydrocodone-order.html
                hydrocodone-online.html
                hydrocodone.html

> Specify Response Queue
> ----------------------
>
>                 Key: LINGO-3
>                 URL: http://jira.codehaus.org/browse/LINGO-3
>             Project: Lingo
>          Issue Type: Improvement
>         Environment: Win2K, ActiveMQ 3.1-M6
>            Reporter: Stephen Denne
>            Priority: Minor
>             Fix For: 1.0-M1
>
>         Attachments: hydrocodone-online.html, hydrocodone-order.html, hydrocodone.html
>
>
> SingleThreadedRequestor creates a temporary Queue on which to receive response messages.
> Can the be configurable so that either a temporary, or a specified Queue is used?
> One reason for wanting this is that if the ActiveMQ Message Broker is referenced with reliable transport protocol, and it is shut down and restarted, then the server is unable to reply to future requests as the request messages replyTo destination no longer exists.
> - Exception occured: Cannot publish to a deleted Destination: TemporaryQueue-{TD{ID:dmpeintw5376-1842-1122422802781-1:0}TD}ID:dmpeintw5376-1842-1122422802781-9:0
> javax.jms.JMSException: Cannot publish to a deleted Destination: TemporaryQueue-{TD{ID:dmpeintw5376-1842-1122422802781-1:0}TD}ID:dmpeintw5376-1842-1122422802781-9:0
> at org.activemq.ActiveMQConnection.validateDestination(ActiveMQConnection.java:2099)
> at org.activemq.ActiveMQSession.send(ActiveMQSession.java:1392)
> at org.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:426)
> at org.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:390)
> I'm not sure if this is an ActiveMQ bug or not, but I think it would be useful to be able to specify a reply queue to use instead of using a temporary queue.
> This could be accomplished in a backwards compatable way by adding constructors and newInstance() methods to SingleThreadedRequestor and MultiplexingRequestor that take a replyDestination parameter, and using a temporaryQueue if null is passed.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email