2012-12-11 78 views
0

我們已經在生產中使用了AMQ 5.5.1幾個月。偶爾,我們觀察到經紀人決定不用外部觸發來刷新自己。發生這種情況時,我們的隊列發件人會失敗,直到經紀人大約10分鐘後重新聯機。我無法找到任何會導致此行爲的信息或設置,並讓我控制它。爲什麼ActiveMQ會自動重啓,我該如何防止它?

這對經紀人來說是否正常自行回收?如果是這樣,會導致什麼事情呢?

2012-12-11 11:02:11,603 | INFO | Refreshing [email protected]: startup date [Tue Dec 11 11:02:11 EST 2012]; root of context hierarchy | org.apache.activemq.xbean.XBeanBrokerFactory$1 | WrapperSimpleAppMain 
2012-12-11 11:02:13,806 | WARN | destroyApplicationContextOnStop parameter is deprecated, please use shutdown hooks instead | org.apache.activemq.xbean.XBeanBrokerService | WrapperSimpleAppMain 
2012-12-11 11:02:13,821 | INFO | PListStore:D:\Tools\ActiveMQ\apache-activemq-5.5.1\bin\win32\..\..\data\localhost\tmp_storage started | org.apache.activemq.store.kahadb.plist.PListStore | WrapperSimpleAppMain 
2012-12-11 11:02:13,868 | INFO | Using Persistence Adapter: KahaDBPersistenceAdapter[D:\Tools\ActiveMQ\apache-activemq-5.5.1\bin\win32\..\..\data\kahadb] | org.apache.activemq.broker.BrokerService | WrapperSimpleAppMain 
2012-12-11 11:02:16,618 | INFO | KahaDB is version 3 | org.apache.activemq.store.kahadb.MessageDatabase | WrapperSimpleAppMain 
2012-12-11 11:02:16,697 | INFO | Recovering from the journal ... | org.apache.activemq.store.kahadb.MessageDatabase | WrapperSimpleAppMain 

回答

0

我發現wrapper exe進程正在強制重啓。

我能夠在wrapper.log(windows服務)中看到進程正在重新啓動,因爲JVM沒有響應。所以這對於代理自動重啓本身並不是問題..這是代理JVM掛起的問題(單獨的問題)。

下面是對於那些有興趣的包裝日誌條目:

ERROR | wrapper | 2012/12/11 11:01:58 | JVM appears hung: Timed out waiting for signal from JVM. 
ERROR | wrapper | 2012/12/11 11:01:58 | JVM did not exit on request, terminated 
STATUS | wrapper | 2012/12/11 11:02:04 | Launching a JVM... 
相關問題