Sorry, I do not see any deadlock there ((
Could you also create issue about this bug ?
On Tue, Feb 24, 2015 at 1:15 PM, Kareem Jabr wrote:
> Full thread dump OpenJDK 64-Bit Server VM (24.65-b04 mixed mode):
>
> "OrientDB WAL Flush Task (sport)" daemon prio=10 tid=0x7f3fa8246000
> nid=0x77f2
Full thread dump OpenJDK 64-Bit Server VM (24.65-b04 mixed mode):
"OrientDB WAL Flush Task (sport)" daemon prio=10 tid=0x7f3fa8246000
nid=0x77f2 waiting on condition [0x7f3feadea000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking t
HI,
Could you send me thread dump then ?
On Sat, Feb 21, 2015 at 11:05 AM, Kareem Jabr wrote:
> Hi, I already set in the properties of *orientdb-server-config.xml* and
> I removed from my code this part:
> OGlobalConfiguration.STORAGE_LOCK_TIMEOUT.setValue(5 * 60 * 1000);
> I am also facing an
Hi, I already set in the properties of *orientdb-server-config.xml* and I
removed from my code this part:
OGlobalConfiguration.STORAGE_LOCK_TIMEOUT.setValue(5 * 60 * 1000);
I am also facing another issue when stopping the orientdb server I still
can see the process running when I execute: ps au
Hi,
I am tried the following after seeing it somewhere here:
OGlobalConfiguration.STORAGE_LOCK_TIMEOUT.setValue(5 * 60 * 1000);
but the same issue occurs.
How and where to set storage.record.lockTimeout? Do I have to do it in
inside the orientdb-server-config.xml?
On Friday, February 20, 2015
Hi,
I do not think that it is deadlock, it is timeout exception could you set
storage.record.lockTimeout property to 20 to double check ?
On Fri, Feb 20, 2015 at 1:08 AM, Kareem Jabr wrote:
> I am facing this exception a lot now,
>
> in context with path [/aa-sport] threw exception
> [com.o
I am facing this exception a lot now,
in context with path [/aa-sport] threw exception
[com.orientechnologies.orient.core.exception.ODatabaseException: Error on
retrieving record #27:165831 (cluster: event)] with root cause
com.orientechnologies.common.concur.OTimeoutException: Can not lock reco
