You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2017/10/15 08:04:00 UTC

[jira] [Resolved] (AMQ-6842) activemq-5.14.4 die java.lang.OutOfMemoryError: Java heap space

     [ https://issues.apache.org/jira/browse/AMQ-6842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved AMQ-6842.
------------------------------
    Resolution: Invalid

Use the mailing list to get help with this sort of things

> activemq-5.14.4 die java.lang.OutOfMemoryError: Java heap space
> ---------------------------------------------------------------
>
>                 Key: AMQ-6842
>                 URL: https://issues.apache.org/jira/browse/AMQ-6842
>             Project: ActiveMQ
>          Issue Type: Improvement
>         Environment: CentOS 6.9 kernel 2.6.32-696.6.3.el6.x86_64   8G memory  sun jdk 1.8.0_121
>            Reporter: hyn
>
> # tail apache-activemq-5.14.4/data/activemq.log
> 2017-10-15 11:31:08,420 | WARN  | Commit failed | org.eclipse.jetty.server.HttpChannel | qtp2134271532-57
> java.lang.OutOfMemoryError: Java heap space
> 2017-10-15 11:31:08,420 | ERROR | Error in thread 'ActiveMQ BrokerService[localhost] Task-25663' | org.apache.activemq.thread.TaskRunnerFactory | ActiveMQ BrokerService[localhost] Task-25663
> java.lang.OutOfMemoryError: Java heap space
> 2017-10-15 11:56:54,515 | WARN  | /images/black-footer-bottom.png | org.eclipse.jetty.server.HttpChannel | qtp2134271532-57
> java.lang.OutOfMemoryError: Java heap space
> 2017-10-15 11:56:19,071 | WARN  | Unexpected thread death: org.eclipse.jetty.util.thread.QueuedThreadPool$3@1cf6cecd in qtp2134271532{STARTED,8<=11<=200,i=1,q=0} | org.eclipse.jetty.util.thread.QueuedThreadPool | qtp2134271532-30431
> 2017-10-15 11:55:07,550 | WARN  | Unexpected thread death: org.eclipse.jetty.util.thread.QueuedThreadPool$3@1cf6cecd in [FAILED toString()] | org.eclipse.jetty.util.thread.QueuedThreadPool | qtp2134271532-55
> 2017-10-15 11:51:56,327 | WARN  | Unexpected thread death: org.eclipse.jetty.util.thread.QueuedThreadPool$3@1cf6cecd in qtp2134271532{STARTED,8<=11<=200,i=1,q=0} | org.eclipse.jetty.util.thread.QueuedThreadPool | qtp2134271532-30434
> 2017-10-15 11:49:26,257 | WARN  | Unexpected thread death: org.eclipse.jetty.util.thread.QueuedThreadPool$3@1cf6cecd in qtp2134271532{STARTED,8<=12<=200,i=2,q=0} | org.eclipse.jetty.util.thread.QueuedThreadPool | qtp2134271532-52
> # # /etc/init.d/activemq status
> INFO: Loading '/etc/default/activemq'
> INFO: Using java '/usr/bin/java'
> ActiveMQ is running (pid '8649')
> # netstat -alpn | grep 8649
> tcp        0      0 :::8161                     :::*                        LISTEN      8649/java
> tcp        0      0 :::27841                    :::*                        LISTEN      8649/java
> tcp        0      0 :::5672                     :::*                        LISTEN      8649/java
> tcp        0      0 :::61613                    :::*                        LISTEN      8649/java
> tcp        0      0 :::61614                    :::*                        LISTEN      8649/java
> tcp        0      0 :::61616                    :::*                        LISTEN      8649/java
> tcp        0      0 :::1883                     :::*                        LISTEN      8649/java
> # curl -i http://localhost:8161/ > /dev/null 
>   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
>                                  Dload  Upload   Total   Spent    Left  Speed
>   0     0    0     0    0     0      0      0 --:--:--  0:28:21 --:--:--     0
> # /etc/init.d/activemq restart
> INFO: Loading '/etc/default/activemq'
> INFO: Using java '/usr/bin/java'
> INFO: Loading '/etc/default/activemq'
> INFO: Using java '/usr/bin/java'
> INFO: Waiting at least 30 seconds for regular process termination of pid '8649' : 
> Java Runtime: Oracle Corporation 1.8.0_121 /usr/java/jdk1.8.0_121/jre
>   Heap sizes: current=62976k  free=61992k  max=1864192k
>     JVM args: -Xms64M -Xmx2G -Djava.util.logging.config.file=logging.properties -Djava.security.auth.login.config=/data/activemq-conf/login.config -Dactivemq.classpath=/data/activemq-conf:/data/apache-activemq-5.14.4//../lib/: -Dactivemq.home=/data/apache-activemq-5.14.4/ -Dactivemq.base=/data/apache-activemq-5.14.4/ -Dactivemq.conf=/data/activemq-conf -Dactivemq.data=/data/activemq-data
> Extensions classpath:
>   [/data/apache-activemq-5.14.4/lib,/data/apache-activemq-5.14.4/lib/camel,/data/apache-activemq-5.14.4/lib/optional,/data/apache-activemq-5.14.4/lib/web,/data/apache-activemq-5.14.4/lib/extra]
> ACTIVEMQ_HOME: /data/apache-activemq-5.14.4
> ACTIVEMQ_BASE: /data/apache-activemq-5.14.4
> ACTIVEMQ_CONF: /data/activemq-conf
> ACTIVEMQ_DATA: /data/activemq-data
> ...Connecting to pid: 8649
> ..............INFO: failed to resolve jmxUrl for pid:8649, using default JMX url
> Connecting to JMX URL: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
> .INFO: Broker not available at: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
> .............
> INFO: Regular shutdown not successful,  sending SIGKILL to process
> INFO: sending SIGKILL to pid '8649'
> INFO: Loading '/etc/default/activemq'
> INFO: Using java '/usr/bin/java'
> INFO: Starting - inspect logfiles specified in logging.properties and log4j.properties to get details
> INFO: pidfile created : '/data/apache-activemq-5.14.4//data/activemq.pid' (pid '13776')
> INFO: Loading '/etc/default/activemq'
> INFO: Using java '/usr/bin/java'
> ActiveMQ is running (pid '13776')
> [link activemq-log.tar.gz|https://pan.baidu.com/s/1c28h6U0 ]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)