Skip to main content

Java com.sun.net.httpserver. HttpServer OutOfMemory Issue

We had to extract text out of documents that people were uploading to the site so we can index them. As this was going to be just a text extraction services I didnt wanted to go for some full blown tomcat server so wrote a quick http server using java

        this.httpServer = HttpServer.create(addr, 0);
        HttpContext context = this.httpServer.createContext("/", new DocumentProcessHandler());
        this.httpThreadPool = Executors.newFixedThreadPool(this.noOfThreads);
        this.httpServer.setExecutor(this.httpThreadPool);
        context.getFilters().add(new HttpParameterFilter());
        this.httpServer.start();
Not adding all code for brevity. 

After being live for 2-3 days the process started crashing and it was a regular pattern. I added -verbose:gc -XX:+HeapDumpOnOutOfMemoryError to the startup script and had a crash dump after 3 days. Using eclipse Memory Analyzer and using Histogram to look at the heap dump revealed that we had 90K HttpConnection objects. wow that looks for sure like a leak.



I tried everything from closing the exchange, responseBody as shown below but the connections would remain.

    class DocumentProcessHandler implements HttpHandler {
        @SuppressWarnings("unchecked")
        public void handle(HttpExchange exchange) throws IOException {
                PrintWriter responseBody = new PrintWriter(exchange.getResponseBody());

                try {
..........code removed for brevity of post....................
                } catch (Throwable t) {
                    logger.error(t);
                    throw new IOException(t);
                } finally {
                    responseBody.flush();
                    responseBody.close();
                    exchange.close();
                }
        }
    }

To prove my theory I send few http requests and did jmap -histo:live 16315 |grep http and keep on seeing the http connections would increase after every requests.
This is definitely a bug in the HttpServer code so use it only for demos and not for production use. I saw that lots of other people are also facing same issues and sun wont agree that its a bug so I am again moving back to tomcat :).


 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6563368
http://forums.sun.com/thread.jspa?threadID=5380631
http://www.experts-exchange.com/Programming/Languages/Java/Q_24416845.html

Comments

  1. I find out if the HTTP GET request has some extra bytes after the last 0xd 0xa in the HTTP header, it could lead to this leak as the HttpConnection is not added to "idleConnections" in sun.net.httpserver.ServerImpl

    ReplyDelete
  2. Another relevant bug report: http://bugs.sun.com/view_bug.do;?bug_id=6946825

    ReplyDelete

Post a Comment

Popular posts from this blog

RabbitMQ java clients for beginners

Here is a sample of a consumer and producer example for RabbitMQ. The steps are
Download ErlangDownload Rabbit MQ ServerDownload Rabbit MQ Java client jarsCompile and run the below two class and you are done.
This sample create a Durable Exchange, Queue and a Message. You will have to start the consumer first before you start the for the first time.

For more information on AMQP, Exchanges, Queues, read this excellent tutorial
http://blogs.digitar.com/jjww/2009/01/rabbits-and-warrens/

+++++++++++++++++RabbitMQProducer.java+++++++++++++++++++++++++++
import com.rabbitmq.client.Connection; import com.rabbitmq.client.Channel; import com.rabbitmq.client.*; public class RabbitMQProducer { public static void main(String []args) throws Exception { ConnectionFactory factory = new ConnectionFactory(); factory.setUsername("guest"); factory.setPassword("guest"); factory.setVirtualHost("/"); factory.setHost("127.0.0.1"); factory.setPort(5672); Conne…

Logging to Graphite monitoring tool from java

We use Graphite as a tool for monitoring some stats and watch trends. A requirement is to monitor impact of new releases as build is deployed to app nodes to see if things like
1) Has the memcache usage increased.
2) Has the no of Java exceptions went up.
3) Is the app using more tomcat threads.
Here is a screenshot

We changed the installer to log a deploy event when a new build is deployed. I wrote a simple spring bean to log graphite events using java. Logging to graphite is easy, all you need to do is open a socket and send lines of events.
import org.slf4j.Logger;import org.slf4j.LoggerFactory; import java.io.OutputStreamWriter; import java.io.Writer; import java.net.Socket; import java.util.HashMap; import java.util.Map; public class GraphiteLogger { private static final Logger logger = LoggerFactory.getLogger(GraphiteLogger.class); private String graphiteHost; private int graphitePort; public String getGraphiteHost() { return graphiteHost; } public void setGraphite…

Jersey posting multipart data

This took me sometime to figure out mostly it was because I was only including jersey-multipart-1.6.jar but I was not including mimepull-1.3.jar.

So the intent is to upload a file using REST api and we need pass meta attributes in addition to uploading the file. Also the intent is to stream the file instead of first storing it on the local disk. Here is some sample code.
@Path("/upload-service") public class UploadService { @Context protected HttpServletResponse response; @Context protected HttpServletRequest request; @POST @Consumes(MediaType.MULTIPART_FORM_DATA) @Produces(MediaType.APPLICATION_JSON) public String uploadFile(@PathParam("fileName") final String fileName, @FormDataParam("workgroupId") String workgroupId, @FormDataParam("userId") final int userId, @FormDataParam("content") final InputStream content) throws JSONException { //.......Upload the file to S3 or netapp or any storage service } }
Now to tes…