[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1681) fetch based on messageId doesn't work

[Konstantin Pupkov (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBMESSAGING-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12475492#action_12475492 ] 

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