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

Rostislav Svoboda (JIRA) issues at jboss.org
Thu Jan 22 04:51:49 EST 2015


     [ https://issues.jboss.org/browse/WFLY-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rostislav Svoboda reopened WFLY-3369:
-------------------------------------


Re-openning after discussion on irc.
This affects JDK8 too - https://bugs.openjdk.java.net/browse/JDK-8044726

Data from https://github.com/jimma/jdk7u40-httpurlconnection-issue test
{code}
-------------------------------------------------------------------
***** Test with java version : 1.7.0_25 *****
!!! connection.setFixedLengthStreamingMode() has been set !!!
CallNum: [300] SuccessNUM: [300] Time: [198]  Total getOutputStream Time : [57]
-------------------------------------------------------------------
***** Test with java version : 1.7.0_25 *****
!!! connection.setFixedLengthStreamingMode()  is  NOT set !!!
CallNum: [300] SuccessNUM: [300] Time: [151]  Total getOutputStream Time : [21]
  
***** Test with java version : 1.7.0_67 *****
!!! connection.setFixedLengthStreamingMode() has been set !!!
CallNum: [300] SuccessNUM: [300] Time: [638]  Total getOutputStream Time : [641]
-------------------------------------------------------------------
***** Test with java version : 1.7.0_67 *****
!!! connection.setFixedLengthStreamingMode()  is  NOT set !!!
CallNum: [300] SuccessNUM: [300] Time: [155]  Total getOutputStream Time : [21]
  
***** Test with java version : 1.8.0_20 *****
!!! connection.setFixedLengthStreamingMode() has been set !!!
CallNum: [300] SuccessNUM: [300] Time: [587]  Total getOutputStream Time : [633]
-------------------------------------------------------------------
***** Test with java version : 1.8.0_20 *****
!!! connection.setFixedLengthStreamingMode()  is  NOT set !!!
CallNum: [300] SuccessNUM: [300] Time: [187]  Total getOutputStream Time : [13]
{code}

> 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.11#6341)


More information about the jboss-jira mailing list