Attempts to start an Eclipse shell of IBM Rational Functional Tester (RFT) result in error "Java was started but returned ... "
The Java error occurs just after you start RFT.
You can start RFT in a new workspace successfully, but if you start RFT again in the same workspace, the Java error occurs again.
After RFT's abnormal end, you get a Java core.
In the Java core you see the following entry.
3XMTHREADINFO3 Java callstack:
4XESTACKTRACE at sun/net/www/protocol/http/ntlm/NTLMAuthSequence.getNextToken(Native Method)
4XESTACKTRACE at sun/net/www/protocol/http/ntlm/NTLMAuthSequence.getAuthHeader(NTLMAuthSequence.java:80)
4XESTACKTRACE at sun/net/www/protocol/http/ntlm/NTLMAuthentication.setHeaders(NTLMAuthentication.java:217)
5XESTACKTRACE (entered lock: sun/net/www/protocol/http/ntlm/NTLMAuthentication@0x425DDB08, entry count: 1)
The following actions do not improve the situation.
- -Clean start
- Disabling the virus scanner.
- Deleting temp files.
- Log in as admin user.
RFT 220.127.116.11 functions error free.
The cause was identified as a defect in the Java Runtime Environment (JRE) under APAR PM81263.
Resolving the problem
Change the network connections.
- Click Window > Preferences > General > Network Connections.
- Change the Active Provider to Direct.
In this way RFT will not connect to a proxy server.
To deploy a fixed JRE, you need to use the JRE with the fix implemented. RFT cannot run with a JRE with a test fix.