[
https://issues.jboss.org/browse/WFLY-3369?page=com.atlassian.jira.plugin....
]
Jim Ma commented on WFLY-3369:
------------------------------
After some jdk code analysis , it turns this performance regression is introduced by
[
https://bugs.openjdk.java.net/browse/JDK-7199862] which is added to check if httpclient
is still available for streaming post. From changeset
[
http://hg.openjdk.java.net/jdk7u/jdk7u40/jdk/rev/e6dc1d9bc70b], each time client
connects to server , it will try to get inputstream from serverSocket and read to know if
the connection is still alive. I am not sure if this is the ideal approach to check.
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
Components: Web Services
Affects Versions: JBoss AS7 7.1.1.Final
Environment: Red Hat Enterprise 6.4, Solaris 10, JBoss AS 7.1.3
Reporter: Zhang Boya
Assignee: Jim Ma
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.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)