You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Gary Brown (JIRA)" <qp...@incubator.apache.org> on 2006/12/01 18:27:24 UTC
[jira] Created: (QPID-149) Invalid replyTo destination when
temporary queue is used
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
[jira] Resolved: (QPID-149) Invalid replyTo destination when
temporary queue is used
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-149?page=all ]
Martin Ritchie resolved QPID-149.
---------------------------------
Resolution: Duplicate
This is a duplicate of QPID-148
> 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
[jira] Assigned: (QPID-149) Invalid replyTo destination when
temporary queue is used
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-149?page=all ]
Martin Ritchie reassigned QPID-149:
-----------------------------------
Assignee: Martin Ritchie
> 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
> Assigned To: Martin Ritchie
> 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
[jira] Reopened: (QPID-149) Invalid replyTo destination when
temporary queue is used
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ 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
[jira] Resolved: (QPID-149) Invalid replyTo destination when
temporary queue is used
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-149?page=all ]
Martin Ritchie resolved QPID-149.
---------------------------------
Resolution: Fixed
Completed: At revision: 486647
> 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
> Assigned To: Martin Ritchie
> 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
[jira] Commented: (QPID-149) Invalid replyTo destination when
temporary queue is used
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-149?page=comments#action_12456351 ]
Martin Ritchie commented on QPID-149:
-------------------------------------
The getJMSReplyTo in AbstractJMSMessage uses a static destinationCache to prevent excessive object creation.
Problem is that setJMSReplyTo uses:
final AMQDestination amqd = (AMQDestination) destination;
final String encodedDestination = amqd.getEncodedName();
and for the case of a AMQQueue this does:
public String getEncodedName()
{
return 'Q' + getQueueName();
}
and the _queueName is set to be null in an AMQTemporaryQueue. This causes a problem with the _destinationCache as all the values are entered with key 'Q' this make the cache return invalid values.
> 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
[jira] Commented: (QPID-149) Invalid replyTo destination when
temporary queue is used
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-149?page=comments#action_12455252 ]
Martin Ritchie commented on QPID-149:
-------------------------------------
I believe this is related to QPID-148 as that reply to address looks like it has been instantiated with null values.
> 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
[jira] Commented: (QPID-149) Invalid replyTo destination when
temporary queue is used
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-149?page=comments#action_12458106 ]
Martin Ritchie commented on QPID-149:
-------------------------------------
The EncodedName was an older mechanism of determining what the destination type was. This should use the BindingURL format.
> 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
> Assigned To: Martin Ritchie
> 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