This content has been marked as final. Show 1 reply
876587 wrote:Different environments mean just that. So something could be causing it outside java.
... and that cause the other threads cannot access the JNI. The same application works fine on other Solaris 10 machines.
Additionally if anything at all is different in the execution data, such as even a name having a different size, then it would change the execution path.
Which would cause a problem in the JNI code to manifest itself on only one box. Probably isn't a pointer bug but all sorts of odd behavior can result from that.