[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38433
 ] 

Adrian Co commented on AMQ-1142:
--------------------------------

Also, I'm not sure if this is a bug or not. :)

> TemporaryQueue communication not working
> ----------------------------------------
>
>                 Key: AMQ-1142
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1142
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, JMS client
>    Affects Versions: 4.1.0
>         Environment: WinXP, Java 1.4.2
>            Reporter: Jos
>         Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion                 - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter      - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to