[
https://jira.jboss.org/jira/browse/JBMESSAGING-1681?page=com.atlassian.ji...
]
Tim Fox commented on JBMESSAGING-1681:
--------------------------------------
Konstantin-
That class FilterImpl is in the *JBM 2.0* code base. According to your report you are
using JBM 1.4. JBM 1.4 and JBM 2.0 are pretty much completely different
projects/codebases. Moreover that class is a *core filter* - it has nothing to do with
JMS, however that's not relevant since you're not using JBM 2.0 anyway.
Regarding using JMSMessageID, we're still waiting for your test program that
demonstrates the issue. It should just be a small program with a few lines of JMS code.
Once you have provided that someone will investigate it.
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