ApacheJames2.3.2のインストールで奇妙なエラーが発生しました。
i Jamesソースコードを使用して、電子メールサーバーの動作を電子メールプロキシのパススルーに変更しました。すべてが数時間はかなりうまく機能します。その後、Jamesは明白な理由もなくシャットダウンします。
まず、phoenix.logにいくつかのエラーが表示されます。
INFO 2012-01-30 18:49:55.215 [Phoenix.] (): Unknown resource. Bundle: 'org.apache.avalon.phoenix.components.monitor.Resources' Key: 'scanner.skipping-file.notice' Args: '/phoenix/apps/smtp-proxy' Reason: java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key scanner.skipping-file.notice
INFO 2012-01-30 18:49:55.232 [Phoenix.] (): Unknown resource. Bundle: 'org.apache.avalon.phoenix.components.monitor.Resources' Key: 'scanner.undeploy.notice' Args: 'smtp-proxy' Reason: java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key scanner.undeploy.notice
INFO 2012-01-30 18:49:55.233 [Phoenix.] (): 20 Blocks to process for phase "shutdown". Order of processing = [spoolmanager, matcherpackages, mailetpackages, remotemanager, pop3server, smtpserver, fetchmail, James, dnsserver, nntpserver, nntp-repository, spoolrepository, localusersrepository, users-store, mailstore, connections, sockets, scheduler, database-connections, thread-manager].
**INFO 2012-01-30 18:49:55.562 [Phoenix ] (): Shutting down because there are not any applications running.**
ERROR 2012-01-30 18:50:00.350 [Phoenix.] (): Component named "thread-manager" failed to pass through the Destruction stage. (Reason: java.lang.IllegalThreadStateException).
ERROR 2012-01-30 18:50:00.350 [Phoenix.] (): Component named "thread-manager" failed to pass through the Destruction stage. (Reason: java.lang.IllegalThreadStateException).
ERROR 2012-01-30 18:50:00.350 [Phoenix.] (): There was an error running phase "shutdown" for Block named "thread-manager". (Reason: Component named "thread-manager" failed to pass through the Destruction stage. (Reason: java.lang.IllegalThreadStateException).).
エラーが発生した直後に、smtp-server.logに2つの例外が表示されます。
30/01/12 18:42:57 ERROR smtpserver: Exception opening socket: Unable to access thread pool due to java.lang.InterruptedException
java.lang.IllegalStateException: Unable to access thread pool due to java.lang.InterruptedException
at org.apache.avalon.excalibur.thread.impl.BasicThreadPool.getWorker(BasicThreadPool.java:164)
at org.apache.excalibur.thread.impl.AbstractThreadPool.execute(AbstractThreadPool.java:131)
at org.apache.excalibur.thread.impl.AbstractThreadPool.execute(AbstractThreadPool.java:120)
at org.apache.avalon.excalibur.thread.impl.DefaultThreadPool.execute(DefaultThreadPool.java:115)
at org.apache.james.util.watchdog.InaccurateTimeoutWatchdog.start(InaccurateTimeoutWatchdog.java:106)
at proxy.james.smtpserver.SMTPHandler.handleConnection(SMTPHandler.java:374)
at org.apache.james.util.connection.ServerConnection$ClientConnectionRunner.run(ServerConnection.java:432)
at org.apache.excalibur.thread.impl.ExecutableRunnable.execute(ExecutableRunnable.java:55)
at org.apache.excalibur.thread.impl.WorkerThread.run(WorkerThread.java:116)
30/01/12 18:42:57 ERROR smtpserver: Exception opening socket: Unable to access thread pool due to java.lang.InterruptedException
java.lang.IllegalStateException: Unable to access thread pool due to java.lang.InterruptedException
at org.apache.avalon.excalibur.thread.impl.BasicThreadPool.getWorker(BasicThreadPool.java:164)
at org.apache.excalibur.thread.impl.AbstractThreadPool.execute(AbstractThreadPool.java:131)
at org.apache.excalibur.thread.impl.AbstractThreadPool.execute(AbstractThreadPool.java:120)
at org.apache.avalon.excalibur.thread.impl.DefaultThreadPool.execute(DefaultThreadPool.java:115)
at org.apache.james.util.watchdog.InaccurateTimeoutWatchdog.start(InaccurateTimeoutWatchdog.java:106)
at proxy.james.smtpserver.SMTPHandler.handleConnection(SMTPHandler.java:374)
at org.apache.james.util.connection.ServerConnection$ClientConnectionRunner.run(ServerConnection.java:432)
at org.apache.excalibur.thread.impl.ExecutableRunnable.execute(ExecutableRunnable.java:55)
at org.apache.excalibur.thread.impl.WorkerThread.run(WorkerThread.java:116)
smtp-server.logの例外は、フェニックスコンテナのシャットダウンによる、ある種のフォローアップ例外だと思います。
何時間もすべてが正常に機能していて、突然フェニックスがシャットダウンする理由を私は本当に説明できないので、誰かがこの動作を見ましたか？
前もって感謝します！