`
黑白配
  • 浏览: 879 次
最近访客 更多访客>>
社区版块
存档分类
最新评论

James 常见错误的解决办法

阅读更多

INFO 2014-03-28 21:38:23.689 [Phoenix ] (): Logger started WARN 2014-03-28 21:38:23.714 [Phoenix ] (): Phoenix was not started by the daemon thus it will not be possible to restart the JVM via the Management interface. INFO 2014-03-28 21:38:23.795 [Phoenix.] (): Installing Sar located at file:/F:/james/james-2.3.2/apps/james.sar. WARN 2014-03-28 21:38:23.858 [Phoenix.] (): The file conf/sqlResources.xml can not be extracted from the Sar "file:/F:/james/james-2.3.2/apps/james.sar" into directory F:\james\james-2.3.2\apps\james\conf\sqlResources.xml because there is a file in the way. WARN 2014-03-28 21:38:23.858 [Phoenix.] (): The file conf/james-fetchmail.xml can not be extracted from the Sar "file:/F:/james/james-2.3.2/apps/james.sar" into directory F:\james\james-2.3.2\apps\james\conf\james-fetchmail.xml because there is a file in the way. WARN 2014-03-28 21:38:23.858 [Phoenix.] (): The file conf/james-smtphandlerchain.xml can not be extracted from the Sar "file:/F:/james/james-2.3.2/apps/james.sar" into directory F:\james\james-2.3.2\apps\james\conf\james-smtphandlerchain.xml because there is a file in the way. WARN 2014-03-28 21:38:23.859 [Phoenix.] (): The file conf/miResources.xml can not be extracted from the Sar "file:/F:/james/james-2.3.2/apps/james.sar" into directory F:\james\james-2.3.2\apps\james\conf\miResources.xml because there is a file in the way. WARN 2014-03-28 21:38:23.859 [Phoenix.] (): The file conf/james-listmanager.xml can not be extracted from the Sar "file:/F:/james/james-2.3.2/apps/james.sar" into directory F:\james\james-2.3.2\apps\james\conf\james-listmanager.xml because there is a file in the way. WARN 2014-03-28 21:38:23.859 [Phoenix.] (): The file conf/james-liststores.xml can not be extracted from the Sar "file:/F:/james/james-2.3.2/apps/james.sar" into directory F:\james\james-2.3.2\apps\james\conf\james-liststores.xml because there is a file in the way. WARN 2014-03-28 21:38:23.860 [Phoenix.] (): The file conf/samples/fetchmail/maxMessageSize.xml can not be extracted from the Sar "file:/F:/james/james-2.3.2/apps/james.sar" into directory F:\james\james-2.3.2\apps\james\conf\samples\fetchmail\maxMessageSize.xml because there is a file in the way. WARN 2014-03-28 21:38:23.860 [Phoenix.] (): The file conf/samples/fetchmail/oneAccountManyUsers.xml can not be extracted from the Sar "file:/F:/james/james-2.3.2/apps/james.sar" into directory F:\james\james-2.3.2\apps\james\conf\samples\fetchmail\oneAccountManyUsers.xml because there is a file in the way. WARN 2014-03-28 21:38:23.861 [Phoenix.] (): The file conf/samples/fetchmail/oneAccountManyUsersDynamic.xml can not be extracted from the Sar "file:/F:/james/james-2.3.2/apps/james.sar" into directory F:\james\james-2.3.2\apps\james\conf\samples\fetchmail\oneAccountManyUsersDynamic.xml because there is a file in the way. WARN 2014-03-28 21:38:23.861 [Phoenix.] (): The file conf/samples/fetchmail/oneAccountPerUser.xml can not be extracted from the Sar "file:/F:/james/james-2.3.2/apps/james.sar" into directory F:\james\james-2.3.2\apps\james\conf\samples\fetchmail\oneAccountPerUser.xml because there is a file in the way. WARN 2014-03-28 21:38:23.861 [Phoenix.] (): The file conf/samples/fetchmail/oneAccountPerUserDynamic.xml can not be extracted from the Sar "file:/F:/james/james-2.3.2/apps/james.sar" into directory F:\james\james-2.3.2\apps\james\conf\samples\fetchmail\oneAccountPerUserDynamic.xml because there is a file in the way. WARN 2014-03-28 21:38:23.861 [Phoenix.] (): The file conf/samples/fetchmail/remoteReceivedHeader.xml can not be extracted from the Sar "file:/F:/james/james-2.3.2/apps/james.sar" into directory F:\james\james-2.3.2\apps\james\conf\samples\fetchmail\remoteReceivedHeader.xml because there is a file in the way. WARN 2014-03-28 21:38:23.862 [Phoenix.] (): The file SAR-INF/config.xml can not be extracted from the Sar "file:/F:/james/james-2.3.2/apps/james.sar" into directory F:\james\james-2.3.2\apps\james\SAR-INF\config.xml because there is a file in the way. WARN 2014-03-28 21:38:23.862 [Phoenix.] (): The file SAR-INF/assembly.xml can not be extracted from the Sar "file:/F:/james/james-2.3.2/apps/james.sar" into directory F:\james\james-2.3.2\apps\james\SAR-INF\assembly.xml because there is a file in the way. WARN 2014-03-28 21:38:23.862 [Phoenix.] (): The file SAR-INF/environment.xml can not be extracted from the Sar "file:/F:/james/james-2.3.2/apps/james.sar" into directory F:\james\james-2.3.2\apps\james\SAR-INF\environment.xml because there is a file in the way. INFO 2014-03-28 21:38:24.200 [Phoenix.] (): Verifying that all key-stores have valid names. INFO 2014-03-28 21:38:24.200 [Phoenix.] (): Verify that any keystore names used by grant or permission reference actual keystores INFO 2014-03-28 21:38:24.200 [Phoenix.] (): Verify that if target is null then actions is null. INFO 2014-03-28 21:38:24.370 [Phoenix.] (): Verifying that the name specified for Blocks and BlockListeners are valid. INFO 2014-03-28 21:38:24.372 [Phoenix.] (): Verifying that the names specified for Component are valid. INFO 2014-03-28 21:38:24.372 [Phoenix.] (): Verifying that the names specified for the Components are unique. INFO 2014-03-28 21:38:24.372 [Phoenix.] (): Verifying that the dependency mapping is valid according to ComponentInfos. INFO 2014-03-28 21:38:24.372 [Phoenix.] (): Verifying that the dependency mapping for every Component is valid with respect to other components. INFO 2014-03-28 21:38:24.372 [Phoenix.] (): Verifying that there are no circular dependencies between Components. INFO 2014-03-28 21:38:24.375 [Phoenix.] (): Verifying that the name specified for Blocks and BlockListeners are unique. INFO 2014-03-28 21:38:24.375 [Phoenix.] (): Verifying that the specified Blocks have valid types. INFO 2014-03-28 21:38:24.406 [Phoenix.] (): Verifying that the specified BlockListeners have valid types. INFO 2014-03-28 21:38:24.485 [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]. 出现了这样的错误,我知道是端口被占用了,但是却不知道是哪个端口,首先我查看了IIS 没有被占用,然后我有看了SMTP简单传输协议也没有被占用,最后发现,最后占用的是自己无意下载的h-mail,占用了端口,实在是让人很伤心。

 

我想为什么win7上边不显示端口号呢?郁闷,然后就启动成功过来 哈哈

分享到:
评论

相关推荐

    james详细配置及问题解决

    在配置过程中可能会遇到一些常见的问题,下面列出了一些常见问题及其解决方法。 ##### 1. 启动失败 如果在启动James时遇到问题,可以尝试检查以下几点: - **环境变量**:确保`JAVA_HOME`等环境变量已正确设置。 - ...

    James邮件服务配置

    #### 四、常见问题及解决方法 **4.1 无法接收邮件** - **原因分析**:可能是DNS配置错误或邮件服务器未正确配置。 - **解决方案**:检查DNS MX记录是否正确设置,并确保邮件服务器的各项配置均符合要求。 **4.2 ...

    James+Foxall+ViaualC# 2008源代码

    设计模式是解决常见软件设计问题的最佳实践。源代码可能包含一些常见的设计模式实现,如工厂模式、单例模式、观察者模式等,有助于提升我们的代码质量和可维护性。 10. **单元测试** 良好的测试实践对于软件质量...

    Linux系统故障诊断与排除--James Kirkland

    常见的解决方案包括: - **从第二个硬盘引导**:如果系统中有多个硬盘,可以从另一个硬盘启动。 - **从救援CD引导**:使用Linux发行版提供的救援CD/DVD进行引导,然后修复问题。 - **使用Knoppix CD重置丢失的root...

    Kingdee.BOS.WebApi.Client.dll反编译项目,用于解决Newtonsoft.Json冲突

    此外,解决依赖冲突的另一种常见方法是使用NuGet包管理器(如果项目是使用Visual Studio或其他支持NuGet的IDE开发的),通过控制台命令来约束或“约束”所有依赖项到同一个版本。这种方法可以确保所有引用的库都使用...

    编程之道(三册)

    3. **设计模式**:书中介绍了常见的设计模式,如工厂模式、单例模式和观察者模式,这些都是解决软件开发中反复出现问题的通用解决方案。 4. **软件工程**:James讨论了软件开发的生命周期,包括需求分析、系统设计...

    一些常见的Java面试题.docx

    9. 设计模式:设计模式是解决常见编程问题的标准化解决方案,如工厂模式、单例模式和观察者模式,它们有助于提高代码的可读性和可维护性。 10. 流式API:Java 8引入的Stream API允许以声明式方式处理数据,简化大量...

    Calculus-Graphical-Numerical-Algebraic-4th-edition

    - **目的**:提供历史背景、案例分析、常见错误警示等额外信息,帮助学生避免常见的学习陷阱。 - **示例**:在讨论极限的概念时,可能会有边注解释该概念的历史发展过程,或者提醒学生注意某些特殊情况下的计算...

    开源项目-JamesMilnerUK-pip-go.zip

    这个项目由James Milner开发,旨在提供高效且可扩展的解决方案,用于解决地理空间分析中的常见问题:判断一个点是否位于特定多边形内。 在地理信息系统(GIS)中,点在多边形内的测试是一个基础任务,广泛应用于...

    计算机网络——自顶向下方法与Internet特色(第三版)习题答案.rar

    《计算机网络——自顶向下方法与Internet特色(第三版)》是计算机网络领域一本非常经典的教材,由James F. Kurose和Keith W. Ross撰写。这本书深入浅出地介绍了计算机网络的基础理论、协议和互联网的工作原理。习题...

    Apress.dot.NET.Test.Automation.Recipes.A.Problem.Solution.Approach.May.2006.pdf

    根据提供的文件信息,我们可以推断出这是一本关于 .NET 测试自动化技术的书籍,书名为《.NET Test Automation Recipes: A Problem-Solution Approach》,作者是 James D. McCaffrey,出版于2006年5月。此书旨在通过...

    Enterprise.Application.Essentials

    - **常见问题解决**: 分析了一些常见的编程问题及其解决方案,帮助开发者避免潜在错误。 7. **Google Script 应用案例** - **实际应用**: 通过多个实际案例展示如何使用Google Script解决企业级应用开发中的具体...

    计算机常见资料书记汇总

    - **简介**: 分析了C语言中常见的错误和陷阱,并提供了解决方案。 - **适合人群**: 需要避免C语言编程中常见问题的学习者。 ### Visual Basic #### 1. Visual Basic.NET教程 - **作者**: Francesco Balena - **简介...

    Keeping Found Things Found. The Study and Practice of Personal Information Management.pdf

    Jeff Johnson的《Web Bloopers: 60 Common Web Design Mistakes, and How to Avoid Them》列举了网页设计中的常见错误,并提供了避免这些错误的策略,对于提高网页的可用性和吸引力具有重要意义。 #### 21. 用户...

    NET软件测试自动化之道.pd

    为了解决常见的测试问题,本书提供了一系列的“食谱”(recipes),每一个“食谱”都针对一个特定的测试问题,提供了清晰的解决方案。这些“食谱”涵盖了从简单的单元测试到复杂的集成测试、从测试数据的管理到测试...

    计算机网络-自顶向下方法 中文版+英文版+slides

    《计算机网络:自顶向下方法》是一本广受赞誉的教材,由James F. Kurose和Keith W. Ross合著,第六版包含了英文原版和中文译版,旨在为学习计算机网络的学生和专业人士提供全面深入的理解。这本书采用了一种独特的...

    Apress.Apache.Tomcat.7.Sep.2011.pdf

    - **常见错误**:列举了一些常见的错误消息及其可能的原因和解决方案。 #### 安全设置 - **身份验证**:介绍如何实现基于表单的身份验证、基本认证等机制。 - **加密通信**:讲解如何启用HTTPS协议,确保数据传输的...

Global site tag (gtag.js) - Google Analytics