Uploaded image for project: 'ActiveMQ Apollo (Retired)'
  1. ActiveMQ Apollo (Retired)
  2. APLO-160

Reduce memory overhead of many connections.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.3
    • None
    • None
    • apollo-1.1-20120209.032648-24

    Description

      While running a stress test against apollo-1.1-20120209.032648-24 (many concurrent TCP connections), the broker became unresponsive.

      It logged several times: java.lang.OutOfMemoryError: GC overhead limit exceeded

      It also logged other warnings, probably related:

      2012-02-14 14:14:49,273 | WARN | handle failed | org.eclipse.jetty.io.nio | Apollo Task
      2012-02-14 14:18:39,073 | WARN | Problem scavenging sessions | org.eclipse.jetty.server.session | HashSessionScavenger-0

      It could not be stopped either, I had to kill -9 it.

      What can be done to avoid these problems?

      FWIW, java has been started with -server -Xmx8192m -Xms4096m

      Attachments

        1. apollo.dump
          88 kB
          Lionel Cons

        Activity

          People

            chirino Hiram R. Chirino
            lionel.cons Lionel Cons
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: