2012-02-29 36 views
4

"これはメモリリークを引き起こす可能性が非常に高い"エラーです。一度エラーが出たら、activeMQに接続できませんでした。私からのActiveMQに接続しようとしていますこれはtomcat 7.0.xでメモリリークを引き起こす可能性が非常に高い

<bean id="activemq" class="org.apache.activemq.camel.component.ActiveMQComponent">  
    <property name="brokerURL" value="${url}" /> 
</bean> 

$ {URL}が

tcp://activeMQhost.localnet/192.168.0.15:61616?keepAlive=true&trace=true 

に設定されている

27-Feb-2012 08:27:55 org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads 
SEVERE: The web application [/Webapp] appears to have started a 
thread named [Camel thread 1: ActiveMQComponent] but has failed to stop 
it. This is very likely to create a memory leak. 
27-Feb-2012 08:27:55 org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads 
SEVERE: The web application [/Webapp] appears to have started a 
thread named [Camel thread 2: ActiveMQComponent] but has failed to stop 
it. This is very likely to create a memory leak. 
27-Feb-2012 08:27:55 org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads 
SEVERE: The web application [/Webapp] appears to have started a 
thread named [ActiveMQ Scheduler] but has failed to stop it. This is very 
likely to create a memory leak. 
27-Feb-2012 08:27:55 org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads 
SEVERE: The web application [/Webapp] appears to have started a 
thread named [Camel thread 3: ProducerTemplate] but has failed to stop it. 
This is very likely to create a memory leak. 
27-Feb-2012 08:27:55 org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads 
SEVERE: The web application [/Webapp] appears to have started a 
thread named [Camel thread 4: ActiveMQComponent] but has failed to stop 
it. This is very likely to create a memory leak. 
27-Feb-2012 08:27:55 org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads 
SEVERE: The web application [/Webapp] appears to have started a 
thread named [Camel thread 5: ActiveMQComponent] but has failed to stop 
it. This is very likely to create a memory leak. 
27-Feb-2012 08:27:55 org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads 
SEVERE: The web application [/Webapp] appears to have started a 
thread named [Camel thread 6: ActiveMQComponent] but has failed to stop 
it. This is very likely to create a memory leak. 
27-Feb-2012 08:27:55 org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads 
SEVERE: The web application [/Webapp] appears to have started a 
thread named [Camel thread 7: ActiveMQComponent] but has failed to stop 
it. This is very likely to create a memory leak. 
27-Feb-2012 08:27:55 org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads 
SEVERE: The web application [/Webapp] appears to have started a 
thread named [Camel thread 8: ActiveMQComponent] but has failed to stop 
it. This is very likely to create a memory leak. 
27-Feb-2012 08:27:55 org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads 
SEVERE: The web application [/Webapp] appears to have started a 
thread named [Camel thread 9: ActiveMQComponent] but has failed to stop 
it. This is very likely to create a memory leak. 
27-Feb-2012 08:27:55 org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads 
SEVERE: The web application [/Webapp] appears to have started a 
thread named [Camel thread 10: ActiveMQComponent] but has failed to stop 
it. This is very likely to create a memory leak. 
27-Feb-2012 08:27:55 org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads 
SEVERE: The web application [/Webapp] appears to have started a 
thread named [Camel thread 11: ProducerTemplate] but has failed to stop 
it. This is very likely to create a memory leak. 
27-Feb-2012 08:27:55 org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads 
SEVERE: The web application [/Webapp] appears to have started a 
thread named [Camel thread 12: ProducerTemplate] but has failed to stop 
it. This is very likely to create a memory leak. 
27-Feb-2012 08:27:55 org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads 
SEVERE: The web application [/Webapp] appears to have started a 
thread named [Camel thread 13: ProducerTemplate] but has failed to stop 
it. This is very likely to create a memory leak. 
27-Feb-2012 08:27:55 org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads 
SEVERE: The web application [/Webapp] appears to have started a 
thread named [ActiveMQ Connection Worker: 
tcp://activeMQhost.localnet/192.168.0.15:61616] but has failed to stop it. 
This is very likely to create a memory leak. 

春豆:私たちは、recently.Hereがトレースされ、このエラーに気づきましたあるマシンから別のマシンへたとえば、machine1とactiveMQ running activeMQhostで実行されているWebアプリケーションです。いくつかの時間、スレッドは何らかの理由で閉じることができませんでした。あなたは、トレースの終わりに接続URLを見つけることができます。

tcp://activeMQhost.localnet/192.168.0.15:61616 

答えて

0

あなたの代わりにフェイルオーバー・トランスポートを使用して検討するかもしれない...その、より堅牢であっても、単一のブローカー接続

http://activemq.apache.org/failover-transport-reference.html

+0

他のブローカーURLは現在使用できません。疑問なんだけど。このエラーは3〜4時間後に発生します。何らかの理由で接続が閉鎖されていると思いますか? – ADS

+0

AMQのどのバージョン?あなたは接続プールを使用していますか?フェイルオーバー転送は、移動する方法です... –

+0

ActiveMQ-5.5.1最新バージョン。以前のバージョンを使用する前に最近は最新のものにアップグレードしました。 – ADS

1

のためにあなたをあなたの接続ファクトリBean(通常はActiveMQでは 'stop'、ラクダのバージョンについてはわからない)にdestory-methodを指定してみてください。

<bean id="..." class="..." destroy-method="stop"> 
    ... 
</bean> 
関連する問題