[OLINGO-1344] Deadlocking in internal ThreadPool

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: (Java) V4 4.5.0, (Java) V4 4.6.0
• Fix Version/s: (Java) V4 4.6.0
• Component/s: odata4-client
• Labels: patch
• Flags: Patch
• Assignee: mibo
• Reporter: Aleksandr Zaigraev
• Created: 04/Mar/19 13:27
• Updated: 26/Apr/19 18:51
• Resolved: 26/Apr/19 18:23

Description

Deadlocking in internal ThreadPool often happens in case of connection errors (e.g. proxy timeouts):

"spring_batch56" #86 prio=5 os_prio=0 tid=0x0000000021577800 nid=0x8388 waiting on condition [0x000000002cefe000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)

• parking to wait for <0x00000007608ec330> (a java.util.concurrent.FutureTask)
  at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
  at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:426)
  at java.util.concurrent.FutureTask.get(FutureTask.java:204)
  at org.apache.olingo.client.core.communication.request.AbstractODataStreamManager.getHttpResponse(AbstractODataStreamManager.java:125)
  at org.apache.olingo.client.core.communication.request.batch.ODataBatchRequestImpl$BatchManagerImpl.getResponseInstance(ODataBatchRequestImpl.java:88)
  at org.apache.olingo.client.core.communication.request.batch.AbstractBatchManager.getResponse(AbstractBatchManager.java:115)
  at org.apache.olingo.client.core.communication.request.batch.AbstractBatchManager.getResponse(AbstractBatchManager.java:38)
  at org.apache.olingo.client.core.communication.request.AbstractODataStreamManager$1.get(AbstractODataStreamManager.java:179)
  at org.apache.olingo.client.core.communication.request.AbstractODataStreamManager$1.get(AbstractODataStreamManager.java:154)

Full thread dump attached.