JAX-WS Performance Pooling (etc)
--------------------------------
Key: AXIS2-1601
URL: http://issues.apache.org/jira/browse/AXIS2-1601
Project: Apache Axis 2.0 (Axis2)
Issue Type: Improvement
Components: jaxws
Reporter: Rich Scheuerle
The following changes will be made:
1) JAXB Pooling Optimization
JAXBContext objects are now pooled in a WeakHashMap.
2) JAXB Advanced Pooling Optimization:
Added code to pool JAXB Unmarshaller, Marshaller, and JAXBIntrospector.
Pooling is initially
disabled for these objects until we get more information from the IBM
performance team.
To enable the pooling, set JAXBUtils.ENABLE_ADV_POOLING=true
3) MTOM Travesal Optimization
Changed the MTOM traversal code to use the more performant OMNavigator
utility.
4) XMLInputFactory/XMLOutputFactory Pooling Optimization:
Refactored this code to use OM StAXUtils. OM StAXUtils contains code to pool
these objects.
5) XMLStreamReader/XMLStreamWriter closing:
Scrubbed jaxws component and added close() calls where appropriate.
6) Servicability:
* Additional servicability is added to identify why a message is consumed.
The "Message is already consumed" error is changed to advise the user to
run with
debug. Running with debug will highlight the place in the code where the
message is
first consumed...which will greatly aid in error detection.
* Added more trace
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
