Re: Member lock when using iSphere compare utility

Hi John,

As I mentioned before, I cannot see anything wrong in iSphere. Of course that does not mean, that there is not a bug, thow, which I did not yet find.

But for now I have to assume, that the IPartListener is reliably called by Eclipse when closing the compare editor.

So maybe you are right and you lost connection to the host without noticing it.

Regards,

Thomas.

Am 05.11.2020 um 11:52 schrieb john erps:

Hi Thomas,

Thanks for responding.

The problem happened without the connection being lost.

However, i just tested again and there was no issue, after comparing and
closing the compare window i could open the compared member for edit
without issue.

So i don't know what happened, but for now just ignore my mail, maybe it
was a one-off thing, or maybe the connection did drop without me noticing
it.



On Wed, Nov 4, 2020 at 7:59 PM Tools/400 <thomas.raddatz@xxxxxxxxxxx> wrote:

Hi John,

I very carefully checked and tested the iSphere Java code again without
having found anything noticeable there.

But there is a problem, when your connection to the IBM server gets
dropped. In that case a new connection is establish and RDi cannot close
the remote member when the compare editor is closed. I produced that
issue with the following steps:

1) Open the compare editor, eg. for members DEMO1 (left) and DEMO2.
2) Dropped the connection to the IBM i by shutting down the VPN client.
3) Reconnected the VPN client.
4) Closed the compare editor.

In that case there is an error entry in the Eclipse error log with
message "*** Could not close stream of left file ***".

The stack trace (taken from RPD 8.0) looks like this:

java.net.SocketException: Software caused connection abort: recv failed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at com.ibm.jsse2.a.a(a.java:166)
at com.ibm.jsse2.a.a(a.java:8)
at com.ibm.jsse2.tc.a(tc.java:542)
at com.ibm.jsse2.tc.a(tc.java:195)
at com.ibm.jsse2.e.read(e.java:3)
at com.ibm.as400.access.DataStream.readFromStream(DataStream.java:52)
at com.ibm.as400.access.DDMDataStream.construct(DDMDataStream.java:89)
at

com.ibm.as400.access.ClassDecoupler.constructDDMDataStream(ClassDecoupler.java:128)
at
com.ibm.as400.access.AS400ThreadedServer.run(AS400ThreadedServer.java:361)
at java.lang.Thread.run(Unknown Source)

Could that explain the problems at your side?

Regards,

Thomas.