pelikan wrote: > > The problem comes when I run the exact same code within Tomcat 5.5.20 in > our WebApp which has many additional libraries (usual stack of hibernate, > mysql, spring, etc), I can always connect to the .NET service fine the > very first time.
I think you're going to need to use process of elimination here--keep removing functionality until you can get your Tomcat app working, so we can figure out what library is the culprit--or another idea: try my DoubleIt web service[1] (just replace it with your WSDL) on Tomcat 5.5.20 vs. .NET service. See if you can get that working--it doesn't have mysql or hibernate or whatever so it's very simple. You may also want to try Metro (follow the DoubleIt instructions)--since you are apparently in the middle of JAR hell if that web service stack works for you, consider yourself liberated. Yet another option--is debug your Tomcat web app and/or use Wireshark--it can be done from within Eclipse[2]. Glen [1] http://www.jroller.com/gmazza/date/20080417 [2] http://www.jroller.com/gmazza/date/20071212 -- View this message in context: http://www.nabble.com/Intermittent-Tomcat-Problem-tp19007231p19007784.html Sent from the cxf-user mailing list archive at Nabble.com.
