Most likely it is the firewall closing the idle connection. Your 5250 sends keep alive packets so that stays up but the WDS must not be sending any keep alive packets. See if you can configure WDS for keep alive packets. Anyone know how??
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John R. Smith, Jr.
Sent: Thursday, November 20, 2014 7:51 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Websphere Development Studio dropping connection
When I use WDS at one of my clients, my session disconnects after an idle
period (not sure how long, maybe 30 minutes) and I have to close and restart
WDS to get reconnected. When I get reconnected and try to reopen the source
member that I had open it tells me the member is already open and gives me
an option to kill the old job. It is also worth mentioning that I do not
lose my 5250 connection when this happens so it is not a network dropping
issue.
When I am connected to my company's iSeries, I can leave WDS idle for hours
and I never lose the connection. Is there some kind of timeout on my
client's iSeries that is causing the disruption?
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.
midrange.com
