You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Ruwan Linton (JIRA)" <ji...@apache.org> on 2008/05/28 07:19:45 UTC

[jira] Commented: (SYNAPSE-327) Invalid ERROR level log message shown in the console when using RM

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

Ruwan Linton commented on SYNAPSE-327:
--------------------------------------

I had a deep look at this, and it is non trivial to fix this issue. That is because of the NIO behavior of the HTTP transport. Here is the issue;

Mercury module is checking whether the message is on the server side or client side by using the axis2 MessageContext.isServerSide() method but our NIO transport and the behavior of synapse (acting as a client and the server at the same time) conflicts with the above specified check. There fore Mercury thinks that the response from the actual server to synapse (at which synapse is acting as a client) as a server side message.

One more thing is that this behavior is not harmful because RM is working and the additional message initiated by Mercury is blocked because the transport connection is closed by the time transport tries to send it (this is consistent).

There fore I think we can live with this issue for the 1.2 release and of course we should try to fix this after the release.

> Invalid ERROR level log message shown in the console when using RM
> ------------------------------------------------------------------
>
>                 Key: SYNAPSE-327
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-327
>             Project: Synapse
>          Issue Type: Bug
>    Affects Versions: NIGHTLY
>            Reporter: Asankha C. Perera
>            Assignee: Ruwan Linton
>            Priority: Blocker
>             Fix For: 1.2
>
>
> Run sample 101
> You will see "[HttpClientWorker-2] ERROR HttpCoreNIOSender No valid destination EPR or OutputStream to send message" on the console, although RM sequences work as expected. Seems like an unwanted RM control message got injected into Synapse for mediation, and if so, should be skipped - as this could lead to a possibly dangerous situation

-- 
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