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

[Zhang Boya (JIRA)]

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

Zhang Boya commented on WFLY-3369:
----------------------------------

Q1: The performance of JAX-WS invocation declined obviously on Solaris.

Q2: 
- Deploy one JAX-WS on web application server, this WS needs authorization. Please don't care about the the type of operation system and the type of web application server. It can be Linux/Solaris and Tomcat/Weblogic/JBoss. The issue occurred on JAX-WS client side.
- The WSDL of this JAX-WS can be access by browser or SOAP UI. Make sure this service can be access by SOAP UI. Then to generate the WS client codes through WSDL.
- Write one simple class using Java, this class only provides main method, you can refer the codes what I have described on steps to reproduce. This main method consist of two parts. Firstly, to initialize the web service client and web service endpoint, then write a for loop of 100 times, to invoke the remote JAX-WS 100 times, and calculate average response time.
- Run this class using JDK_1.7.0_25_Solaris_64 and  JDK_1.7.0_55_Solaris_64, to compare the response time.

Q3: Of course. Warm up is mandatory and necessary for our performance test.


> 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)