Win a copy of Micro Frontends in Action this week in the Server-Side JavaScript and NodeJS forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

GWT, AXIS2 and Timeouts

Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm building a system that uses GWT as the front end and the RemoteServlet layer uses AXIS2 and WSDLs to grab data and return it to the front end. This entire system is deployed on my own machine however I'm having almost constant timeout errors. Virtually every time I try to run my system I can single step through the code and see the request go out. I even see it arrive at the web service layer and be answered. But it frequently seems to leave my code and gets bogged down in the AXIS2 code where the response is being built. The data being fetched seems to happen pretty fast when I observe via single stepping but the response seldom returns. I'm only returning a single String from most of my services so the load of the response should not be a factor. Because this is all happening on local host I don't believe increasing the timeout interval is the right answer, something must be wired improperly.
I'm using generic Tomcat for my web container and all my servlets are just generic extensions of RemoteServlet that use AXIS2 to access the WebService layer.

So far I've tried a few tricks with saving a reference to the ServiceStub object as a singleton so I'm not constantly reinstantiating it but it didn't help.
This problem doesn't seem to build up in anyway. What I mean is its just as likely to happen when I first start Tomcat on the first request. I'm not sure what to make of all this.

I tried removing the GWT from the equation and using a simple comandline system to invoke the web services. So far this has not had any timeout issues. However I'm not sure if I can chalk this up to an issue with GWT because I see the request arrive at the Service layer and get bogged down after the service itself is complete but before the response is sent. I believe the code seems to die in RPCUtils.

Any help would be most appreciated as I'm coming up on a deadline and the current system is unusable like this.

This is one of my stack traces:
He repaced his skull with glass. So you can see his brain. Kinda like this tiny ad:
Thread Boost feature
    Bookmark Topic Watch Topic
  • New Topic