Corrections to the JAX-WS Async Engpoint thread switching code.
---------------------------------------------------------------
Key: AXIS2-3298
URL: https://issues.apache.org/jira/browse/AXIS2-3298
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: jaxws
Reporter: Rich Scheuerle
Assignee: Rich Scheuerle
The recent changes to perform a thread switch on the Async Endpoint has
revealed several problems.
Nick Gallardo has provided patches for these issues, which I will integrate
after I finish testing.
Problem 1:
There is a lack of toggling for this new code. In some cases, the code that
embeds Axis2 may
want to change the capabilities.
Solution 1:
A SERVER_DISABLE_THREAD_SWITCH property is exposed on the MessageContext. If a
consumer sets this property to
Boolean.TRUE, then the threadswitch is disabled.
A change is also made to use separate thread Executor factories for the client
and the server.
Problem 2:
Due to a typo, the JavaDispatcher oneWay processing has a return inside a debug
clause.
Solution 2:
The return is moved outside of the debug clause.
Problem 3:
Attachments are not being cleaned up properly on the server due to the thread
switch.
Solution 3:
After the worker thread processing is complete, clean up the attachments.
--
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]
