Yet even more information: On a whim, I switched back to creating a new Client and not using the Client returned by getContext().getClientDispatcher(). I call stop() when I am finished and now everything works fine.
So, here's the state of play: Client client = getContext().getClientDispatcher(); ...same code... results in some kind of hang where the number of available clients or sockets is somehow depleted. Client client = new Client(getContext().createChildContext(),ref.getSchemeProtocol()); ...same code.. client.stop(); client = null and everything works fine (so far). I had just moved to use getClientDispatcher() to solve an out-of-memory issue. I think calling stop() will keep that from happening again but I'll have to run some more tests. Meanwhile, I also see this in the log: INFO: Stopping the internal[HTTPS/1.1] client I have the org.restlet.ext.net.jar in the classpath (jar manifest), should I be seeing that? It doesn't seem right. --Alex Milowski ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2846654
