I have similar problem with poor jboss performance. I tried a simple example with 2 library sets - let's call them jboss & sun | | jboss: | | | jboss-jaxrpc.jar | | jboss-jaxws.jar | | jboss-saaj.jar | | | | sun: | | | jaxb-xjc.jar | | jaxws-api.jar | | jaxws-rt_sun.jar | | jsr181-api.jar | | saaj-api.jar | | saaj-impl.jar | | stax-1.2.0.jar | | stax-ex.jar | | streambuffer.jar | | | | common libraries : | | | activation.jar | | commons-logging.jar | | concurrent.jar | | ebaycalls.jar | | javassist.jar | | jaxb-api.jar | | jaxb-impl.jar | | jboss-common.jar | | jboss-remoting.jar | | jboss-xml-binding.jar | | jbossws-client.jar | | jbossws-common.jar | | jbossws-spi.jar | | jsr173_api.jar | | log4j.jar | | mail.jar | | policy.jar | | wsdl4j-1.6.2.jar | | xercesImpl.jar | | | | With common+sun_libs the initial call takes 8.2sec and consumes 34MB | With common+jboss_libs it takes 60sec and consumes 150MB | | Does anyone have an idea what's going on? Why the JBoss WS implementation is so slow? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208406#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...