Issue #2686: objectdb got hang after fetch some record.

All of my client threads are got hang after doing some fetch operations due to objectdb.

Stack trace: 
java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
java.net.SocketInputStream.read(SocketInputStream.java:171)
java.net.SocketInputStream.read(SocketInputStream.java:141)
java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
java.io.BufferedInputStream.read(BufferedInputStream.java:345)
   - locked java.io.BufferedInputStream@294f1aa
com.objectdb.o.NTS.n(NTS.java:150)
com.objectdb.o.NTS.m(NTS.java:127)
com.objectdb.o.CLS.y(CLS.java:189)
com.objectdb.o.CLS.z(CLS.java:145)
com.objectdb.o.CST.ZU(CST.java:353)
com.objectdb.o.QRR.k(QRR.java:202)
com.objectdb.o.QRR.i(QRR.java:129)
com.objectdb.jpa.JpaQuery.getResultList(JpaQuery.java:407)
   - locked com.objectdb.jdo.PMImpl@778f3a48 

This is the stack trace can you please tell where is the issue?

The stack trace indicates client-server communication for running a query. More details are needed regarding the specific query or settings that causes this issue. If every query causes this issue, please check the network, as the blocking may be external (e.g. a firewall).

> regarding the specific query or settings that causes this issue

No same query giving result initially but after some time it hanged.

>If every query causes this issue, please check the network, as the blocking may be external (e.g. a firewall)

am running both db and my app in same machine.

This is happening if multiple thread(20-50) accessing db parallelly for 30-40 min.

please find the attachment of thread dump for your reference.

Thank you.

One of the threads in this thread dump indicates closing or restarting the server and waiting to some other threads to complete. This waiting was restricted now to maximum 2 seconds in build 2.8.6_03, so please try it and see if there is a difference. Maybe you will see a new exception with the new build that may explain the issue.