[ https://issues.jboss.org/browse/WFLY-3369?page=com.atlassian.jira.plugin.... ] 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. -- This message was sent by Atlassian JIRA (v6.2.3#6260)