noon
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
12:09 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1681) fetch based on messageId doesn't work
[
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
1:23 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1681) fetch based on messageId doesn't work
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1681?page=com.atlassian.ji...
]
Konstantin Pupkov commented on JBMESSAGING-1681:
------------------------------------------------
You didn't get my complain.
I tried JMSMessageID as well - it doesn't work. It works fine with JBOSS 4.1.GA.
I tried to find workaround that is why I tried "JBMessageID" in my sample.
here is link to JBMessageID:
JavaDoc class:
org.jboss.messaging.core.filter.impl.FilterImpl
public class FilterImpl
extends java.lang.Object
implements Filter
This class implements a JBoss Messaging filter
Version:
$Revision: 3569 $ $Id: Selector.java 3569 2008-01-15 21:14:04Z timfox $
Author:
Tim Fox, Jeff Mesnil JBM filters have the same syntax as JMS 1.1 selectors, but the
identifiers are different. Valid identifiers that can be used are:
*******!!!!!!!JBMessageID!!!!!!!!******** - the message id of the message JBMPriority -
the priority of the message JBMTimestamp - the timestamp of the message JBMDurable -
"DURABLE" or "NON_DURABLE" JBMExpiration - the expiration of the
message JBMSize - the encoded size of the full message in bytes Any other identifers that
appear in a filter expression represent header values for the message String values must
be set as SimpleString, not java.lang.String (see JBMESSAGING-1307). Derived from JBoss MQ
version by, Norbert Lataille, Juha Lindfors, Jason Dillon, Scott Stark, Tim Fox
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
1:39 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1681) fetch based on messageId doesn't work
[
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
6:36 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1681) fetch based on messageId doesn't work
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1681?page=com.atlassian.ji...
]
Konstantin Pupkov updated JBMESSAGING-1681:
-------------------------------------------
Attachment: mdb-with-error.zip
Please take a look on my sample. I rework it based on original mdb sample from
ejb3-tutorial
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
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
9:51 p.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-1681) fetch based on messageId doesn't work
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1681?page=com.atlassian.ji...
]
Howard Gao reassigned JBMESSAGING-1681:
---------------------------------------
Assignee: Howard Gao (was: Tim Fox)
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
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
9:53 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1681) fetch based on messageId doesn't work
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1681?page=com.atlassian.ji...
]
Howard Gao updated JBMESSAGING-1681:
------------------------------------
Fix Version/s: 1.4.0.SP3.CP09
1.4.5.GA
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
10:51 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1681) fetch based on messageId doesn't work
[
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
10:53 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1681) fetch based on messageId doesn't work
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1681?page=com.atlassian.ji...
]
Howard Gao closed JBMESSAGING-1681.
-----------------------------------
Resolution: Rejected
rejected as it's not an issue.
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
11:47 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1681) fetch based on messageId doesn't work
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1681?page=com.atlassian.ji...
]
Konstantin Pupkov commented on JBMESSAGING-1681:
------------------------------------------------
Yes. You are correct. Then I added cnn.start(). All things works. But that mean your
sample is not correct. Please correct example. As far as I rework your example.
ejb3-tutorial.....mdb
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
1:28 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1681) fetch based on messageId doesn't work
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1681?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1681:
-----------------------------------------
Hi can you kindly point me where I can get ejb3-tutorial example and see if it has the
problem? Thanks.
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
5:36 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1681) fetch based on messageId doesn't work
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1681?page=com.atlassian.ji...
]
Konstantin Pupkov commented on JBMESSAGING-1681:
------------------------------------------------
here is link: http://www.jboss.org/ejb3/docs.html
search for "Tutorials (Source)" section.
Then download source in zip archive. In source follow by
"/ejb3-tutorials/source/mdb/" path.
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
10:34 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1681) fetch based on messageId doesn't work
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1681?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1681:
-----------------------------------------
Thanks!
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
1:47 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1681) fetch based on messageId doesn't work
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1681?page=com.atlassian.ji...
]
Tim Fox commented on JBMESSAGING-1681:
--------------------------------------
Konstantin-
The ejb tutorial is not written or managed by the JBoss Messaging team, it's handled
by the EJB3 team.
If you think it is wrong, then you can raise an issue on the EJB forum and hopefully they
will correct 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: 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
11:45 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1681) fetch based on messageId doesn't work
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1681?page=com.atlassian.ji...
]
Konstantin Pupkov commented on JBMESSAGING-1681:
------------------------------------------------
Well,
I don't come up with jboss' forums+products+packages... structures. I just want to
improve product itself. From my prospective you are one team. I think jboss need to
improve internal communications to avoid situations like that.
When I will have time I can rise that issue in other forum group, but I guess you can do
that faster. Just reassign this issue to other team what ever it is.
Konstantin
P.S. Thank you for quick respond and help!
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
5665
days inactive
5667
days old
14 comments
3 participants
participants (3)
-
Howard Gao (JIRA) -
Konstantin Pupkov (JIRA)
-
Tim Fox (JIRA)