[jira] Commented: (SYNAPSE-418) JMSSender#processSyncResponse incorrectly sets serverSide to true

["Ruwan Linton (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SYNAPSE-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758955#action_12758955 ] 

Ruwan Linton commented on SYNAPSE-418:
--------------------------------------

Folks, this is fixed on the synapse trunk as well as on the 1.3 branch and will be available with the synapse-1.3 release.

Ruwan

> JMSSender#processSyncResponse incorrectly sets serverSide to true
> -----------------------------------------------------------------
>
>                 Key: SYNAPSE-418
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-418
>             Project: Synapse
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: NIGHTLY
>         Environment: N/A
>            Reporter: Andreas Veithen
>            Assignee: Ruwan Linton
>             Fix For: 1.3
>
>
> JMSSender#processSyncResponse always calls MessageContext#setServerSide(true). This causes a failure in one of the recently added JMS unit test that uses code similar to ServiceClient#sendReceive. Indeed, if serverSide is true, AxisEngine.receive will try to invoke a MessageReceiver which doesn't exist in this case.
> Since the meaning of the serverSide property is not entirely clear (see also AXIS2-2096), I'm not sure about the correct solution for this issue.
> Asankha, can you have a look at this?

-- 
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org