Hi guys.
I am using your library in a application that i am a developer.
In the application We have wrapped class with internal attribute of type NamedMutex (we use the newInstance to create the implementation) and in this wrapped class we create a waitOne method thar call the NamedMutexPosixImpl.waitOne original method:
public boolean waitOne(long timeout, TimeUnit unit) {
boolean acquired = false;
try {
//Where mutex is of type NamedMutex
acquired = mutex.waitOne(timeout, unit);
} catch (AbandonedMutexException ame) {
System.out.println(ame.getMessage());
} catch (IOException ioe) {
System.out.println(ioe.getMessage());
} catch (Exception e) {
System.out.println(e.getMessage());
}
if (!acquired) {
close();
mutex = createMutex(); //Recreate the mutex using NamedMutex.newInstance method
}
return acquired;
}
We use this code to lock file read/write operations. Sometimes the application crash with the repeated method call waitOne. We are using the following os: Red Hat Enterprise Linux 7 (7.2).
The the usage of method waitOne is crashing the aplication ans always generating a thread dump with the following stack:
Hi guys. I am using your library in a application that i am a developer. In the application We have wrapped class with internal attribute of type NamedMutex (we use the newInstance to create the implementation) and in this wrapped class we create a waitOne method thar call the NamedMutexPosixImpl.waitOne original method:
We use this code to lock file read/write operations. Sometimes the application crash with the repeated method call waitOne. We are using the following os: Red Hat Enterprise Linux 7 (7.2). The the usage of method waitOne is crashing the aplication ans always generating a thread dump with the following stack:
Do anyone face this issue before?