×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Thanks Matt, I'll forward this information to our consultant.
Dean Eshleman,
MMA, Inc.
"Haas, Matt (CL Tech Sv)" <matt.haas@xxxxxxxxxxx>
Sent by: web400-bounces@xxxxxxxxxxxx
02/09/2009 02:17 PM
Please respond to
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
To
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
cc
Subject
Re: [WEB400] Websphere question
You have to set the timeout in the code. What you have to do depends upon
the tool you used to generate the client stubs. Here is an example using a
WebSphere generated stub:
private static final int MILLISECONDS_IN_A_SECOND = 1000;
MyProxy proxy = new MyProxy();
((Stub)proxy.getSSOwsPort()).setTimeout(wsTimeoutSeconds *
MILLISECONDS_IN_A_SECOND);
wsTimeoutSeconds is read from a property file.
Matt
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Dean.Eshleman@xxxxxxxxxxxxxx
Sent: Monday, February 09, 2009 1:56 PM
To: web400@xxxxxxxxxxxx
Subject: [WEB400] Websphere question
Hi,
We have a consultant that has written some java code that is running in
Websphere v6.1(?) on Windows. This code is calling some of our web
services that are running in another instance of Websphere on the System
i. Periodically, his call to the web service times out because the web
service is kind of slow. Does anyone know if there is a setting in
Websphere to control how long his code waits for a response?
I tested my web services using SOAPUI and they have never timed out there.
Running a load test, one of them took up to 35 seconds, but it did
complete successfully so I know the timeout issue isn't occurring in
Websphere on the System i.
Dean Eshleman,
MMA, Inc.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.