Update 8/15, SamV:
I resolved this issue by upgrading the JVM inside EAServer to Java 1.5.0_22. Though this is not the supported version in EAS 5.5, we decided to try it. Worked out OK. I did upgrade the OJDBC to OJDBC14.jar (instead of Classese12.zip used previously) to match it.
FYI, this meant tweaking the below batch files inside EAServer\bin -
serverstart.bat
setenv.bat
user_setenv.bat
Notes:
1. In Deployed EAServers we are running it as a Windows Service. You will have to uninstall and re-install the Jaguar service after making the above changes.
2. Though the Java runtime version is upgraded, I continue to compile all the Java classses to Java 1.2 level as was done previously, though. Most of the classes inside EAServer seem to be compiled to 1.2 level.