[
https://jira.jboss.org/jira/browse/JBMESSAGING-1681?page=com.atlassian.ji...
]
Tim Fox commented on JBMESSAGING-1681:
--------------------------------------
Konstantin - if you're using the JMS API, then you should be using JMSMessageID, not
JBMessageID, as per JMS spec.
Can you tell me where in the docs does it say to use JBMessageID?
Also can you please post a full test program that demonstrates the issue. Your code
snippet does not go into enough detail.
fetch based on messageId doesn't work
-------------------------------------
Key: JBMESSAGING-1681
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1681
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.3.GA
Environment: Linux, Ubuntu 9, JBoss 5.1.0.GA, My SQL 5, Java 6
Reporter: Konstantin Pupkov
Assignee: Tim Fox
here is me code on client:
String msgId="ID:JBM-511cfd0b-b4a8-4148-bd69-127a1fdeecfe";-->no worries
that message has been just created and 100% exists in my DB
QueueReceiver recv= ConnectionFactory.getInstance().getSession().createReceiver(queue,
"JMSMessageID='"+msgId+"'");
Message msg1= recv.receive();---->hungs on forever
I tied
QueueReceiver recv= ConnectionFactory.getInstance().getSession().createReceiver(queue,
"JBMessageID='"+msgId+"'"); --> this is according to
documentation. failed as well
Please fix it and keep standard approach: JMSMessageID not JBMessageID.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira