[jira] Resolved: (AXIS2-2277) JMS Message Id in request message context

["Asankha C. Perera (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AXIS2-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Asankha C. Perera resolved AXIS2-2277.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2

Fixed on trunk to be included for 1.2 release (Already included in first RC)

> JMS Message Id in request message context
> -----------------------------------------
>
>                 Key: AXIS2-2277
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2277
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: transports
>    Affects Versions: 1.1.1
>         Environment: Windows XP
>            Reporter: John Turner
>         Assigned To: Asankha C. Perera
>             Fix For: 1.2
>
>
> The correlation id on a JMS  message is not set correctly.  It appears that this is occuring because the mesage id is not set on creation of the request message context (JMSMessageReceiver.createMessageContext).  I added the following line of code and it appears to have fixed the problem.
> private MessageContext createMessageContext(Message message) {
>   InputStream in = JMSUtils.getInputStream(message);
>   try {
>     MessageContext msgContext = new MessageContext();
>     .....
>     msgContext.getOptions().setMessageId(message.getJMSMessageID());

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


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org