Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Setting Timeout with WebSphere generated services

 
Scott Camilleri
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am working on an application where I generated source code off of an existing WSDL using the WebSphere 6.1 WSDL2Java task. I am trying to set the timeout value for the web service call in the client code by using the typical setTimeout() method on the service stub, but that does not seem to be working as it does with Axis generated code. By default, it seems that the connection to the web service takes about 20 seconds before timing out, but I am not exactly sure where this default of 20 seconds is being set just yet.

Is there a way to set this timeout in the client code so that it does not default to 20 seconds?

Thank you in advance!
 
R Srini
Ranch Hand
Posts: 215
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi. I do not have experience with setting client timeouts in WAS, but this may be what you are looking for. Please let us know if this works out
 
Scott Camilleri
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This is setting it for JAX-WS web services. The web services that I generated off of a WSDL were using the WebSphere's WSDL2Java task. I did try this on JAX-WS generated web service and it does indeed work. Any other suggestions on getting a timeout set for a WAS generated web service? Should I perhaps post this in the WebSphere forum and try my luck there?
 
R Srini
Ranch Hand
Posts: 215
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes, you could try asking in a Websphere forum. Please do share the solution once you have it. All the best!
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic