You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Bill Nagy (JIRA)" <ji...@apache.org> on 2006/11/08 15:00:51 UTC
[jira] Created: (AXIS2-1649) Invocation with useSeparateListener
option set will never complete if an error occurs in the outbound transport
Invocation with useSeparateListener option set will never complete if an error occurs in the outbound transport
---------------------------------------------------------------------------------------------------------------
Key: AXIS2-1649
URL: http://issues.apache.org/jira/browse/AXIS2-1649
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Reporter: Bill Nagy
Assigned To: Bill Nagy
If the useSeparateListener option is set, MessageContext.TRANSPORT_NON_BLOCKING will, in turn, be set forcing the actual message transmission to occur on another thread via the TransportNonBlockingInvocationWorker. However, the TransportNonBlockingInvocationWorker swallows all exceptions, so if an error occurs during the outbound transport, the callback will never be notified and the requestor will hang indefinately. I will modify the TransportNonBlockingInvocationWorker to invoke Callback.onError(), if it exists, passing the exception and eliminating the hang.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-1649) Invocation with useSeparateListener
option set will never complete if an error occurs in the outbound transport
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS2-1649:
------------------------------------
Priority: Blocker (was: Major)
> Invocation with useSeparateListener option set will never complete if an error occurs in the outbound transport
> ---------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-1649
> URL: https://issues.apache.org/jira/browse/AXIS2-1649
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Bill Nagy
> Assignee: Bill Nagy
> Priority: Blocker
>
> If the useSeparateListener option is set, MessageContext.TRANSPORT_NON_BLOCKING will, in turn, be set forcing the actual message transmission to occur on another thread via the TransportNonBlockingInvocationWorker. However, the TransportNonBlockingInvocationWorker swallows all exceptions, so if an error occurs during the outbound transport, the callback will never be notified and the requestor will hang indefinately. I will modify the TransportNonBlockingInvocationWorker to invoke Callback.onError(), if it exists, passing the exception and eliminating the hang.
--
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
[jira] Assigned: (AXIS2-1649) Invocation with useSeparateListener
option set will never complete if an error occurs in the outbound transport
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe reassigned AXIS2-1649:
----------------------------------------
Assignee: Deepal Jayasinghe (was: Bill Nagy)
> Invocation with useSeparateListener option set will never complete if an error occurs in the outbound transport
> ---------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-1649
> URL: https://issues.apache.org/jira/browse/AXIS2-1649
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Bill Nagy
> Assignee: Deepal Jayasinghe
> Priority: Blocker
>
> If the useSeparateListener option is set, MessageContext.TRANSPORT_NON_BLOCKING will, in turn, be set forcing the actual message transmission to occur on another thread via the TransportNonBlockingInvocationWorker. However, the TransportNonBlockingInvocationWorker swallows all exceptions, so if an error occurs during the outbound transport, the callback will never be notified and the requestor will hang indefinately. I will modify the TransportNonBlockingInvocationWorker to invoke Callback.onError(), if it exists, passing the exception and eliminating the hang.
--
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
[jira] Commented: (AXIS2-1649) Invocation with useSeparateListener
option set will never complete if an error occurs in the outbound transport
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503145 ]
Davanum Srinivas commented on AXIS2-1649:
-----------------------------------------
Can we please fix this for 1.3?
thanks,
dims
> Invocation with useSeparateListener option set will never complete if an error occurs in the outbound transport
> ---------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-1649
> URL: https://issues.apache.org/jira/browse/AXIS2-1649
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Bill Nagy
> Assignee: Bill Nagy
> Priority: Blocker
>
> If the useSeparateListener option is set, MessageContext.TRANSPORT_NON_BLOCKING will, in turn, be set forcing the actual message transmission to occur on another thread via the TransportNonBlockingInvocationWorker. However, the TransportNonBlockingInvocationWorker swallows all exceptions, so if an error occurs during the outbound transport, the callback will never be notified and the requestor will hang indefinately. I will modify the TransportNonBlockingInvocationWorker to invoke Callback.onError(), if it exists, passing the exception and eliminating the hang.
--
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
[jira] Resolved: (AXIS2-1649) Invocation with useSeparateListener
option set will never complete if an error occurs in the outbound transport
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe resolved AXIS2-1649.
--------------------------------------
fixed in the current SVN
> Invocation with useSeparateListener option set will never complete if an error occurs in the outbound transport
> ---------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-1649
> URL: https://issues.apache.org/jira/browse/AXIS2-1649
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Bill Nagy
> Assignee: Deepal Jayasinghe
> Priority: Blocker
>
> If the useSeparateListener option is set, MessageContext.TRANSPORT_NON_BLOCKING will, in turn, be set forcing the actual message transmission to occur on another thread via the TransportNonBlockingInvocationWorker. However, the TransportNonBlockingInvocationWorker swallows all exceptions, so if an error occurs during the outbound transport, the callback will never be notified and the requestor will hang indefinately. I will modify the TransportNonBlockingInvocationWorker to invoke Callback.onError(), if it exists, passing the exception and eliminating the hang.
--
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