Hi Jeff, could make a test with the 2.0m7? It helpes to automatically release connection once the entity has been handled.
Best regards, Thierry Boileau > Yes, we made sure to update and we did notice that there were recent > changes to the latch code. > -jeff > > "Thierry Boileau" <[email protected] > <mailto:[email protected]>> wrote in message > news:[email protected]... > Hello Jeff, > > did you try the latest snapshot (the internal connectors have been > updated a few days ago)? > > Best regards, > Thierry Boileau > >> We're seeing the vm blocking forever on a call to Client.put that >> worked fine on an earlier release of 2.0-SNAPSHOT: >> >> Thread [main] (Suspended) >> Unsafe.park(boolean, long) line: not available [native >> method] >> LockSupport.park(Object) line: 158 >> >> CountDownLatch$Sync(AbstractQueuedSynchronizer).parkAndCheckInterrupt() >> line: 747 [local variables unavailable] >> >> CountDownLatch$Sync(AbstractQueuedSynchronizer).doAcquireSharedInterruptibly(int) >> line: 905 >> >> CountDownLatch$Sync(AbstractQueuedSynchronizer).acquireSharedInterruptibly(int) >> line: 1217 >> CountDownLatch.await() line: 207 [local variables >> unavailable] >> HttpClientHelper(BaseClientHelper).handle(Request, >> Response) line: 490 >> Client.handle(Request, Response) line: 268 >> Client.handle(Request) line: 259 >> Client.put(Reference, Representation) line: 508 >> >> Any ideas? Has anyone else seen this behavior? >> >> -jeff >> >> ------------------------------------------------------ >> >> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2442913 >> >> > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2443767
