I have similar problem with poor jboss performance.
I tried a simple example with 2 library sets - let's call them jboss & sun
common libraries :
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?
Profiling would probably help in understanding what's happing there. When wsdl contracts with huge type models are involved, the port creation can be quite time consuming because a lot of classes are created. Perhaps you could evaluate re-using the port instance once it has been created.
In case you're seeing different performance between the first invocation and following ones, instead, please refer to http://jbossws.jboss.org/mediawiki/index.php?title=Tuning.
Finally, regarding the library comparison, I'd say also try using recent version of jbossws (from the libs names I'd say you're using old ones).
I tested it with latest 3.0.5GA.
It seems it's not a bug but just annoying way of working. Debugging it showed that the eagerInitialize() is the evil.
It's not a fun to wait 60 seconds for the first call to the eBay SDK.