[jboss-jira] [JBoss JIRA] (WFLY-3369) Performance issue of jaxws-client on JDK 1.7.0_55

[Jim Ma (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972172#comment-12972172 ] 

Jim Ma commented on WFLY-3369:
------------------------------

It turns out the root cause is the jdk7 performance regression which happens since jdk7u40. When the HttpURLConnection.setFixedLengthStreamingMode() is called before connect , jdk7u55 is about 6 times slower than jdk7u25 to respond for HttpURLConnection.getOutputStream(). I've reported this issue to Oralce and wait jdk team's response. Once the jdk bug is confirmed and created, I'll let you know. 

> 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) 
>          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.2.3#6260)