[
https://jira.jboss.org/jira/browse/JBMESSAGING-1681?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1681:
-----------------------------------------
Hi Konstantin,
I know what the problem is - you didn't call connection.start() before you receive the
message. If you don't start the connecton, message will never be delivered to the
consumer.
So I'm going to reject this jira.
Howard
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: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
Attachments: mdb-with-error.zip
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