[ http://issues.apache.org/jira/browse/QPID-149?page=all ]
Martin Ritchie reopened QPID-149:
---------------------------------
Now that the temporary queue is correctly transfered it appears that the queue
name is changing.. perhaps because it will be recreating an AMQTemporaryQueue
which takes the current System time as part of its name. So in some of the
tests it passes if the message is transported within 1 ms.
> Invalid replyTo destination when temporary queue is used
> --------------------------------------------------------
>
> Key: QPID-149
> URL: http://issues.apache.org/jira/browse/QPID-149
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: M1
> Environment: Java 1.5.0_04 Windows XP
> Reporter: Gary Brown
> Priority: Minor
>
> When sending a JMS message with a replyTo field set to a JMS temporary queue.
> At the point the message is sent in the client, it has the following details:
> INFO: Sending JMS message: Body:
> hello
> JMS timestamp: 0
> JMS expiration: 0
> JMS priority: 0
> JMS delivery mode: 0
> JMS reply to:
> direct://amq.direct/TempQueue1164991547153/tmp_127.0.0.12068_1?exclusive='true'&autodelete='true'
> AMQ message number: -1
> However, when it is received it has the details:
> INFO: Handle message: Body:
> hello
> JMS timestamp: 1055409977
> JMS expiration: 0
> JMS priority: 0
> JMS delivery mode: 2
> JMS reply to: direct://amq.direct/null/null?durable='true'
> AMQ message number: 1
> When I do the same test with a defined queue (i.e. not temporary), it works
> correctly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
