axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Asankha C. Perera (JIRA)" <>
Subject [jira] Resolved: (AXIS2-4025) Using JMSMessageID as correlationID for JMS messages
Date Fri, 27 Feb 2009 02:26:01 GMT


Asankha C. Perera resolved AXIS2-4025.

    Resolution: Won't Fix
      Assignee: Asankha C. Perera

The JMS transport is not within the Axis2 project anymore. If there is any issue, please use
the latest version from WS-Commons

> Using JMSMessageID as correlationID for JMS messages
> ----------------------------------------------------
>                 Key: AXIS2-4025
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: kernel, transports
>         Environment: OS: Windows XP Pro 2002 Service Pack 2
>            Reporter: Cathal Callaghan
>            Assignee: Asankha C. Perera
>             Fix For: 1.4
>         Attachments:,
> The correlationID solution currently in place in Axis2 version 1.4 does not work.
> Currently the option is available to specify a correlationID but when the MessageConsumer
is created no MessageSelector is specified. This means that the MessageConsumer will take
any message off the queue.
> Also, currently the only way to use a correlationID is to explicity specify an ID via
the JMSConstants.JMS_COORELATION_ID property. This is very restrictive for those who wish
to use the option of using the JMSMessageID of the message as the correlationID.
> I have attached a proposed solution which firstly ensures that the MessageConsumer is
created using a MessageSelector. Also i have given the user a choice, if they explicity specify
a correlationID then this will be used otherwise the JMSMessageID of the message will be used
as the correlationID.
> Thanks,
> Cathal

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message