[
https://issues.apache.org/jira/browse/AXIS2-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481576
]
Asankha C. Perera commented on AXIS2-2277:
------------------------------------------
Dims, Rajith
I was working on this and 2030 and would fix both during this weekend
asankha
> 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: Rajith Attapattu
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
