]
Jim Ma edited comment on WFLY-3369 at 5/19/14 1:28 AM:
-------------------------------------------------------
Do you have a test case to reproduce this issue ?
was (Author: jim.ma):
Do you have some test case that help reproduce this issue ?
Performance issue of jaxws-client on JDK 1.7.0_55
-------------------------------------------------
Key: WFLY-3369
URL:
https://issues.jboss.org/browse/WFLY-3369
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Environment: Red Hat Enterprise 6.4, Solaris 10, JBoss AS 7.1.3
Reporter: Zhang Boya
Assignee: Jason Greene
Priority: Critical
Assume that a JAX-WS deploys on somewhere else, developer generates the JAX-WS client
side classes by using wsdl2java tools. These classes have been exported as
'exmaple-ws-client.jar'. When developer needs to access this JAX-WS in their web
application, this JAR file would be published with WAR file together. By default, the
JBoss AS would supply an instance of CXF's implementation for the JAX-WS client when
web application be deployed to JBoss AS. The class name of this JAX-WS client would be
'org.apache.cxf.jaxws.JaxWsClientProxy'. The JAX-WS invocations of client side got
a very bad performance since I upgraded JDK from 1.7.0_25 to 1.7.0_55, especially on
Solaris.