[
https://issues.apache.org/jira/browse/SYNAPSE-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591434#action_12591434
]
Ruwan Linton commented on SYNAPSE-174:
--------------------------------------
Fixed, after a long time with Mercury (A new WS-RM implementation resides on
WSO2 for the moment and under apache license v2)
> The non-blocking http/s transports cannot handle WS-RM requests
> ---------------------------------------------------------------
>
> Key: SYNAPSE-174
> URL: https://issues.apache.org/jira/browse/SYNAPSE-174
> Project: Synapse
> Issue Type: Bug
> Affects Versions: 1.1-RC1
> Reporter: Asankha C. Perera
> Assignee: Ruwan Linton
> Fix For: 1.2
>
>
> This is caused by Sandesha2 trying to use the non-blocking NIO http/s
> transport in an inconsistent way. Fixing this would require re-evaluation of
> the Sandesha2 requirements and implementation of necessary support in the NIO
> transport.
> Synapse can still initiate WS-RM on an outgoing connection, but cannot
> terminate a WS-RM session
--
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]
