Hi all- We've updated to the restlet trunk last night, but not successfully- some or all (hard to tell yet) of our Client requests are hanging with the thread getting suspended during the latch.await() call in BaseClientHelper.handle().
(Our project is a web-app that uses openid for federated sign-in, so on sign-in the user's browser is eventually redirected back to us with a token, and we make a POST call to the openid provider using a ClientResource, in order to verify the sign-in etc. Since our client POST call never returns, we're not able to sign in to our web app, which is why we haven't yet concluded whether all the other places we're using the client connector are also broken or not.) The only thing we're doing that's even slightly unusual is that we're calling clientResource.post(null), since we don't need to post an entity body (all the params are in the URI). We haven't tried changing this- figured it was important to send this issue in asap, but we'll be trying different things this afternoon. So, is it the case that the built-in Client connector is broken in RC1? Or does it work for some requests and not others? Incidentally, this was a bit of a pain in the butt to track down, since all we could tell was that somewhere our thread was just hanging. debugging restlet apps is not too fun to begin with, due to the deep stacks filled with filter handle/doHandle calls and in general all the layers of Helpers and deep inheritance trees of all the restlet classes etc. I'm sure much of that is unavoidable, so this isn't really a complaint, but we'd be interested in hearing how other people typically debug their restlet apps- maybe there should be some docs about that too :-) ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2464496
