Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.java.machine > #20

Is there any known issue about mutex lock used via JNI on Solaris 10?

From Krit <krit.kasemosoth@gmail.com>
Newsgroups comp.lang.java.machine
Subject Is there any known issue about mutex lock used via JNI on Solaris 10?
Date 2011-08-02 01:12 -0700
Organization http://groups.google.com
Message-ID <dd02e89a-08ec-493e-9861-77ccfdc1319a@gz10g2000vbb.googlegroups.com> (permalink)

Show all headers | View raw


Dear Java Experts,

I'm facing a strange behavior when running a JNI application that use
the mutex lock. The application hanged after running for a while on
one of our Solaris 10 machines. After investigating the stack trace of
the application, it shows that one of all the application's threads
that access the JNI hold the mutex lock forever, and that cause the
other threads cannot access the JNI. The same application works fine
on other Solaris 10 machines.

The mutex function I used as show below:

mutex_lock(&mutex)


The application hanged at this line:

0xff2cc940        ___lwp_mutex_timedlock + 0x8


The Kernel version is SunOS 5.10 Generic_142900-14
JDK 1.6 update 17 b04


Since this issue occurrs on only one Solaris 10 machine in our
environment, I'm wondering if there is any known issue regarding the
mutex lock used in JNI on Solaris 10. I tried to search the Internet
and the Java Bug database but found nothing related to this issue.


Best regards,
Krit K.

Back to comp.lang.java.machine | Previous | Next | Find similar


Thread

Is there any known issue about mutex lock used via JNI on Solaris 10? Krit <krit.kasemosoth@gmail.com> - 2011-08-02 01:12 -0700

csiph-web