• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Setting Timeout with WebSphere generated services

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • 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?

I tried posting in the Web Services forum, but this may be a WebSphere specific thing seeing how I am able to set the timeouts using Axis and JAX-WS generated web services.

Thank you in advance!
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic