The company machine that is not having the problem is set at 120. I don't
have access to that on the client so will have to track someone done that
can look at it.
Also, thanks for pointing out that there is a WDSC group. I was unaware.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Kurt
Anderson
Sent: Friday, November 21, 2014 10:16 AM
To: Midrange Systems Technical Discussion
Subject: RE: Websphere Development Studio dropping connection
Hi John,
This question was just asked on the WDSCi-L list.
Check this option out:
"CFGTCP
Option #3
TCP keep alive . . . . . . . . . TCPKEEPALV
The default value for TCPKEEPALV on our system was 120 (minutes). I changed
it to 5, and so far so good. I just sent an unrelated message to this list
and it occurred to me that I did leave RDi alone for a good hour and came
back to it without issues."
Kurt Anderson
Sr. Programmer/Analyst - Application Development, Service Delivery Platform
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John
R. Smith, Jr.
Sent: Thursday, November 20, 2014 12:53 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Websphere Development Studio dropping connection
OK, more details.
You are correct and I apparently did not hit the C hard enough. :) I am
running WDSC - IBM Websphere Development Studio Client for iSeries version
7.0.0.
The client iSeries OS is 6.1.
The company iSeries is 6.1 and 7.1 (different LPars of course). There is
also an antique in the corner running V5R4M0 that doesn't have a problem
either.
I'm not sure about the product release levels and which ones I should look
at.
I really think there is a weird network problem here and was hoping I could
point them in the right direction. I have hit other problems with then
where they are not "blocking" any outbound traffic but I can't VPN into my
company without connecting to my hotspot instead of their network.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
DeLong, Eric
Sent: Thursday, November 20, 2014 11:56 AM
To: Midrange Systems Technical Discussion
Subject: RE: Websphere Development Studio dropping connection
John,
WDS is the product name for SEU, SDA, RLU, and whatever else exists under
that "Websphere Development Studio" banner...
There USED to be an eclipse based client that was labeled as "Websphere
Development Studio Client", or WDSC for short... This product has been
replaced (several times) by "Rational Developer for POWER systems", commonly
referred to as RDi. Current version is 9.1. I assume that when you say
WDS, you really mean RDi.
OS and product release levels?
Firewall is still probably the culprit. We maintain an internal "PCI
Segment" to rigidly control network access across this "boundary". If your
host stores PCI controlled data (Credit Card anything), then it is likely
behind another firewall.
-Eric
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John
R. Smith, Jr.
Sent: Thursday, November 20, 2014 9: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?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
