I was tracking down an out-of-memory error with my new Atomojo V2
server project where I moved to 2.1.m7 and I found the solution quite
disturbing. I have a configuration where I call out to Google's
ClientLogin and the code that did that had this code:
Client client = new
Client(context.createChildContext(),service.getSchemeProtocol());
instead of this:
Client client = context.getClientDispatcher();
The service URI was over HTTPS and the memory was being consumed by
byte arrays instantiated in the SSL handling. I found that
out-of-memory error from such a subtle change in the API usage
disturbing. Any ideas on what could cause that?
I have other issues this code as well in 2.1.m7. After awhile, the
client stops being able to connect. If I restart the server,
everything is fine.
I have been using this code for a long time without any issue.
I am using the org.restlet.ext.net.jar client connector but the SSL
client support also requires org.restlet.ext.ssl.jar. When I looked
at the memory consumption, there were class from
org.restlet.ext.ssl.jar involved.
--Alex Milowski
------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2846045
