Bugzilla – Bug 2683
rft client never terminates even after transfer is complete
Last modified: 2005-02-18 11:36:17
You need to
before you can comment on or make changes to this bug.
When I run the GT 3.9.4 rft client on SLES8/IA-64 using IBM's Java2 1.4.2
the client doesn't display the usual progress to stdout and never terminates
even though the transfers do complete. An identical build on SLES8/IA-32
also using IBM's Java2 1.4.2 behaves normally. IBM's Java is apparantly based
on Sun's Java. Sun Java2 1.4.2_07 has the same problem.In the very likely scenario
that this is a Java problem, is their any chance you could isolate the broken
behavious so we can report the problem to Sun and/or IBM? Thanks.
When things appear hung, can you please issue kill -QUIT <jvm process> for the
client and server process? That will cause the JVM the dump its threads (to
stdout/err). Can you capture that output and send it to us.
Created an attachment (id=500) [details]
kill -QUIT <master_java_process>
Is the thread dump for the client enough, or do you really need the server side
You'll notice in the log two different transfers. The first one worked, which
surprised me because it's the first time I've seen it work on IA-64 (~4
The second rft hung as expected.
Yes, the server side is the one I'm really interested in.
Created an attachment (id=502) [details]
Server kill -QUIT javacore...txt
This server is running on SLES8 IA-32 which is different than the hanging
client which is SLES8 IA-64.
Created an attachment (id=503) [details]
Client kill -QUIT corresponding to previous server attachment
This client kill -QUIT corresponding to server javacore attachment 502 [details].
This is a SLES8 IA-64 client.
The logs look good to me... so it might be some issue in RFT or dependent code
related to the JVM.
Will it be possible for me to try 3.9.5 on this platform ?
If this question was for me. I'll install 3.9.5 as soon as it's released. You
can also install any version
you'd like in your home directory. JP
We've tested all of the following Java's with identical results:
- IBM Java2 1.4.2 build cxia64142-20040917
- Sun Java2 1.4.2_07
- Bea JRockit 1.4.2_05
- Bea JRockit 1.5.0
Once GT 3.9.x is deployed using a specific Java, is it OK for me to switch at runtime which Java
is used by the RFT client, for example, or do I need to re-deploy GT 3.9.x using every Java I
want to use/test?
No. you don't have to redeploy gt every time you deploy a new jdk.
Turns out it was a networking configuration issue and not an acrchitecture
issue. If JP can add more
details, i can close the bug
Looks like this was a host misconfiguration problem. The failing IA-64 machine
a bad IP address for itself in /etc/hosts. Admin error.