I can only offer a workaround in case you need to clear the open members. For an issue I had in an earlier version, I learned that I could go to the workspace, and clear the cached source member directory, which would let RDi open without trying to open any source members.
For me, the source member cache is in:
C:\Users\darren\IBM\rationalsdp\workspace\RemoteSystemsTempFiles\SYSTEMNAME\QSYS.LIB
-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Joe Pluta
Sent: Monday, June 10, 2019 6:42 PM
To: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: [WDSCI-L] 9.6.0.6 infinite loop hanging unable to use
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
The original issue, which I've actually submitted to IBM, was that when I switched from a machine on VPN1 to a machine on VPN2 with source members open on both machines, RDi would attempt to log into the VPN1 machine, seemingly to attempt to live parse one of the source members I had open. After 30 seconds or so, it would fail and then go on to the next member. This could take several minutes if I had a number of source members open. Discussion with the lab centered on trying to get that failure to only occur once.
Well, 9.6.0.6 has made this immeasurably worse. Now, it goes through a couple of the source members, and then sits on one and keeps looping.
30 seconds, then "Connection could not be established" then "Enter Password". Lather, rinse and repeat. On the bottom of the display, I can see that it's live parsing the same member, sitting at 0%. The only answer is to terminate the Java process. But if I start RDi again, I get the same endless loop.
The lab says they're trying to address it, but I'm very frustrated at this point. The simple answer is, if you get an error on a connection, stop trying to connect to it. If I close every member every time I shut down, I'm fine, but that defeats the purpose of being able to switch to a different connection. I might as well have one workspace for each connection.
I'm looking at reinstalling RDi because of a problem that I already reported and has gotten worse. Not my best day.
UPDATE: While I was typing this, the loop finally ended. It looped through the last member of VPN1 about 8 times and then finally gave up.
Interestingly, there were about that many member open on VPN2. I won't even hazard a guess, and I'm going to move on. I will, though, consider the one workspace per VPN connection gambit, inconvenient though it might be.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/wdsci-l.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com
midrange.com
