Lavanya

Seeing this issue on AIX machines. Looks like trove jar behaves diffrently based on Open JDK and Oracle JDK. Any thoughts on this? java.lang.Thread.State: RUNNABLE at gnu.trove.impl.hash.TObjectHash.insertKeyRehash(TObjectHash.java:348) at gnu.trove.impl.hash.TObjectHash.insertKey(TObjectHash.java:294) at gnu.trove.map.custom_hash.TObjectIntCustomHashMap.put(TObjectIntCustomHashMap.java:252) at gnu.trove.map.custom_hash.TObjectIntCustomHashMap.readExternal(TObjectIntCustomHashMap.java:1141) at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:2076)...

Seeing this issue on few servers. Does usage of different JDKs cause this issue? Because of this the server is not coming up. java.lang.Thread.State: RUNNABLE at gnu.trove.impl.hash.TObjectHash.insertKeyRehash(TObjectHash.java:348) at gnu.trove.impl.hash.TObjectHash.insertKey(TObjectHash.java:294) at gnu.trove.map.custom_hash.TObjectIntCustomHashMap.put(TObjectIntCustomHashMap.java:252) at gnu.trove.map.custom_hash.TObjectIntCustomHashMap.readExternal(TObjectIntCustomHashMap.java:1141) at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:2076)...

Seeing this issue in few servers. Does usage of different JDKs cause this issue? java.lang.Thread.State: RUNNABLE at gnu.trove.impl.hash.TObjectHash.insertKeyRehash(TObjectHash.java:348) at gnu.trove.impl.hash.TObjectHash.insertKey(TObjectHash.java:294) at gnu.trove.map.custom_hash.TObjectIntCustomHashMap.put(TObjectIntCustomHashMap.java:252) at gnu.trove.map.custom_hash.TObjectIntCustomHashMap.readExternal(TObjectIntCustomHashMap.java:1141) at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:2076)...