免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
查看: 4248 | 回复: 1
打印 上一主题 下一主题

[Mail] 求助邮件服务James232无法启动 [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2009-12-31 12:02 |只看该作者 |倒序浏览
10可用积分
启动时信息如下:

[root@dooynn logs]# cat /root/log.txt
Using PHOENIX_HOME:   /usr/local/james232
Using PHOENIX_TMPDIR: /usr/local/james232/temp
Using JAVA_HOME:      /usr/java/jdk1.5.0_06
Running Phoenix:

Phoenix 4.2

James Mail Server 2.3.2
Remote Manager Service started plain:4555
POP3 Service started plain:110
SMTP Service started plain:25
NNTP Service Disabled
FetchMail Disabled

log显示:

INFO    2009-12-31 11:30:28.933 [Phoenix ] (): Logger started
WARN    2009-12-31 11:30:28.954 [Phoenix ] (): Phoenix was not started by the daemon thus it will not be possible to restart the JVM via the Management

interface.
INFO    2009-12-31 11:30:29.037 [Phoenix.] (): Installing Sar located at file:/usr/local/james232/apps/james.sar.
WARN    2009-12-31 11:30:29.160 [Phoenix.] (): The file conf/sqlResources.xml can not be extracted from the Sar "file:/usr/local/james232/apps/james.sar"

into directory /usr/local/james232/apps/james/conf/sqlResources.xml because there is a file in the way.
WARN    2009-12-31 11:30:29.161 [Phoenix.] (): The file conf/james-fetchmail.xml can not be extracted from the Sar "file:/usr/local/james232/apps/james.sar"

into directory /usr/local/james232/apps/james/conf/james-fetchmail.xml because there is a file in the way.
WARN    2009-12-31 11:30:29.161 [Phoenix.] (): The file conf/james-smtphandlerchain.xml can not be extracted from the Sar

"file:/usr/local/james232/apps/james.sar" into directory /usr/local/james232/apps/james/conf/james-smtphandlerchain.xml because there is a file in the way.
WARN    2009-12-31 11:30:29.161 [Phoenix.] (): The file conf/miResources.xml can not be extracted from the Sar "file:/usr/local/james232/apps/james.sar" into

directory /usr/local/james232/apps/james/conf/miResources.xml because there is a file in the way.
WARN    2009-12-31 11:30:29.162 [Phoenix.] (): The file conf/james-listmanager.xml can not be extracted from the Sar

"file:/usr/local/james232/apps/james.sar" into directory /usr/local/james232/apps/james/conf/james-listmanager.xml because there is a file in the way.
WARN    2009-12-31 11:30:29.162 [Phoenix.] (): The file conf/james-liststores.xml can not be extracted from the Sar "file:/usr/local/james232/apps/james.sar"

into directory /usr/local/james232/apps/james/conf/james-liststores.xml because there is a file in the way.
WARN    2009-12-31 11:30:29.162 [Phoenix.] (): The file conf/samples/fetchmail/maxMessageSize.xml can not be extracted from the Sar

"file:/usr/local/james232/apps/james.sar" into directory /usr/local/james232/apps/james/conf/samples/fetchmail/maxMessageSize.xml because there is a file in

the way.
WARN    2009-12-31 11:30:29.163 [Phoenix.] (): The file conf/samples/fetchmail/oneAccountManyUsers.xml can not be extracted from the Sar

"file:/usr/local/james232/apps/james.sar" into directory /usr/local/james232/apps/james/conf/samples/fetchmail/oneAccountManyUsers.xml because there is a

file in the way.
WARN    2009-12-31 11:30:29.163 [Phoenix.] (): The file conf/samples/fetchmail/oneAccountManyUsersDynamic.xml can not be extracted from the Sar

"file:/usr/local/james232/apps/james.sar" into directory /usr/local/james232/apps/james/conf/samples/fetchmail/oneAccountManyUsersDynamic.xml because there

is a file in the way.
WARN    2009-12-31 11:30:29.163 [Phoenix.] (): The file conf/samples/fetchmail/oneAccountPerUser.xml can not be extracted from the Sar

"file:/usr/local/james232/apps/james.sar" into directory /usr/local/james232/apps/james/conf/samples/fetchmail/oneAccountPerUser.xml because there is a file

in the way.
WARN    2009-12-31 11:30:29.164 [Phoenix.] (): The file conf/samples/fetchmail/oneAccountPerUserDynamic.xml can not be extracted from the Sar

"file:/usr/local/james232/apps/james.sar" into directory /usr/local/james232/apps/james/conf/samples/fetchmail/oneAccountPerUserDynamic.xml because there is

a file in the way.
WARN    2009-12-31 11:30:29.164 [Phoenix.] (): The file conf/samples/fetchmail/remoteReceivedHeader.xml can not be extracted from the Sar

"file:/usr/local/james232/apps/james.sar" into directory /usr/local/james232/apps/james/conf/samples/fetchmail/remoteReceivedHeader.xml because there is a

file in the way.
WARN    2009-12-31 11:30:29.164 [Phoenix.] (): The file SAR-INF/config.xml can not be extracted from the Sar "file:/usr/local/james232/apps/james.sar" into

directory /usr/local/james232/apps/james/SAR-INF/config.xml because there is a file in the way.
WARN    2009-12-31 11:30:29.164 [Phoenix.] (): The file SAR-INF/assembly.xml can not be extracted from the Sar "file:/usr/local/james232/apps/james.sar" into

directory /usr/local/james232/apps/james/SAR-INF/assembly.xml because there is a file in the way.
WARN    2009-12-31 11:30:29.165 [Phoenix.] (): The file SAR-INF/environment.xml can not be extracted from the Sar "file:/usr/local/james232/apps/james.sar"

into directory /usr/local/james232/apps/james/SAR-INF/environment.xml because there is a file in the way.
INFO    2009-12-31 11:30:29.414 [Phoenix.] (): Verifying that all key-stores have valid names.
INFO    2009-12-31 11:30:29.414 [Phoenix.] (): Verify that any keystore names used by grant or permission reference actual keystores
INFO    2009-12-31 11:30:29.414 [Phoenix.] (): Verify that if target is null then actions is null.
INFO    2009-12-31 11:30:29.628 [Phoenix.] (): Verifying that the name specified for Blocks and BlockListeners are valid.
INFO    2009-12-31 11:30:29.629 [Phoenix.] (): Verifying that the names specified for Component are valid.
INFO    2009-12-31 11:30:29.630 [Phoenix.] (): Verifying that the names specified for the Components are unique.
INFO    2009-12-31 11:30:29.630 [Phoenix.] (): Verifying that the dependency mapping is valid according to ComponentInfos.
INFO    2009-12-31 11:30:29.630 [Phoenix.] (): Verifying that the dependency mapping for every Component is valid with respect to other components.
INFO    2009-12-31 11:30:29.630 [Phoenix.] (): Verifying that there are no circular dependencies between Components.
INFO    2009-12-31 11:30:29.632 [Phoenix.] (): Verifying that the name specified for Blocks and BlockListeners are unique.
INFO    2009-12-31 11:30:29.632 [Phoenix.] (): Verifying that the specified Blocks have valid types.
INFO    2009-12-31 11:30:29.672 [Phoenix.] (): Verifying that the specified BlockListeners have valid types.
INFO    2009-12-31 11:30:29.727 [Phoenix.] (): 20 Blocks to process for phase "startup". Order of processing = [dnsserver, database-connections, mailstore,

users-store, localusersrepository, spoolrepository, sockets, thread-manager, scheduler, James, mailetpackages, matcherpackages, spoolmanager, connections,

remotemanager, pop3server, smtpserver, nntp-repository, nntpserver, fetchmail].
INFO    2009-12-31 11:30:43.839 [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].
ERROR   2009-12-31 11:30:44.934 [Phoenix.] (): Component named "thread-manager" failed to pass through the Destruction stage. (Reason:

java.lang.IllegalThreadStateException).
ERROR   2009-12-31 11:30:44.935 [Phoenix.] (): Component named "thread-manager" failed to pass through the Destruction stage. (Reason:

java.lang.IllegalThreadStateException).
ERROR   2009-12-31 11:30:44.935 [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).).
org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleException: Component named "thread-manager" failed to pass through the Destruction stage. (Reason:

java.lang.IllegalThreadStateException).
        at org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleHelper.fail(LifecycleHelper.java:354)
        at org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleHelper.shutdown(LifecycleHelper.java:28
        at org.apache.avalon.phoenix.components.application.DefaultApplication.shutdown(DefaultApplication.java:566)
        at org.apache.avalon.phoenix.components.application.DefaultApplication.doRunPhase(DefaultApplication.java:482)
        at org.apache.avalon.phoenix.components.application.DefaultApplication.runPhase(DefaultApplication.java:409)
        at org.apache.avalon.phoenix.components.application.DefaultApplication.stop(DefaultApplication.java:233)
        at org.apache.avalon.framework.container.ContainerUtil.stop(ContainerUtil.java:292)
rethrown from
java.lang.IllegalThreadStateException
        at java.lang.ThreadGroup.destroy(ThreadGroup.java:750)
        at org.apache.avalon.excalibur.thread.impl.DefaultThreadPool.dispose(DefaultThreadPool.java:76)
        at org.apache.avalon.framework.container.ContainerUtil.dispose(ContainerUtil.java:306)
        at org.apache.avalon.cornerstone.blocks.threads.AbstractThreadManager.dispose(AbstractThreadManager.java:69)
        at org.apache.avalon.framework.container.ContainerUtil.dispose(ContainerUtil.java:306)
        at org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleHelper.shutdown(LifecycleHelper.java:274)
        at org.apache.avalon.phoenix.components.application.DefaultApplication.shutdown(DefaultApplication.java:566)
INFO    2009-12-31 11:30:44.939 [Phoenix.] (): exception while stopping:Component named "thread-manager" failed to pass through the Destruction stage.

(Reason: java.lang.IllegalThreadStateException).

您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP