起步软件技术论坛-X3

 找回密码
 立即注册
搜索
查看: 650|回复: 12

【结】IMServer启动报错

[复制链接]
发表于 2010-9-14 20:38:11 | 显示全部楼层 |阅读模式
IMServer启动的时候报告如下错误:
Exception in thread "main" java.lang.NoClassDefFoundError: org.jivesoftware.wildfire.component.InternalComponentManager
   at java.lang.Class.initializeClass(libgcj.so.7rh)
   at org.jivesoftware.wildfire.XMPPServer.initialize(XMPPServer.java:343)
   at org.jivesoftware.wildfire.XMPPServer.start(XMPPServer.java:409)
   at org.jivesoftware.wildfire.XMPPServer.<init>(XMPPServer.java:177)
   at java.lang.Class.newInstance(libgcj.so.7rh)
   at org.jivesoftware.wildfire.starter.ServerStarter.start(ServerStarter.java:88)
   at org.jivesoftware.wildfire.starter.ServerStarter.main(ServerStarter.java:49)
Caused by: java.lang.ClassNotFoundException: java.util.concurrent.ConcurrentHashMap not found in org.jivesoftware.wildfire.starter.JiveClassLoader{urls=[file:/usr/oracle/X3Server/IMServer/lib/,file:/usr/oracle/X3Server/IMServer/lib/wildfire.jar,file:/usr/oracle/X3Server/IMServer/lib/activation.jar,file:/usr/oracle/X3Server/IMServer/lib/resin.jar,file:/usr/oracle/X3Server/IMServer/lib/commons-el.jar,file:/usr/oracle/X3Server/IMServer/lib/jasper-runtime.jar,file:/usr/oracle/X3Server/IMServer/lib/jdic.jar,file:/usr/oracle/X3Server/IMServer/lib/ojdbc14.jar,file:/usr/oracle/X3Server/IMServer/lib/jasper-compiler.jar,file:/usr/oracle/X3Server/IMServer/lib/bouncycastle.jar,file:/usr/oracle/X3Server/IMServer/lib/hession.jar,file:/usr/oracle/X3Server/IMServer/lib/ojdbc14_g.jar,file:/usr/oracle/X3Server/IMServer/lib/hsqldb.jar,file:/usr/oracle/X3Server/IMServer/lib/hsqldbutil.jar,file:/usr/oracle/X3Server/IMServer/lib/mysql.jar,file:/usr/oracle/X3Server/IMServer/lib/servlet.jar,file:/usr/oracle/X3Server/IMServer/lib/startup.jar,file:/usr/oracle/X3Server/IMServer/lib/mail.jar,file:/usr/oracle/X3Server/IMServer/lib/postgres.jar,file:/usr/oracle/X3Server/IMServer/lib/jtds.jar], parent=gnu.gcj.runtime.SystemClassLoader{urls=[file:/usr/oracle/X3Server/IMServer/lib/startup.jar], parent=gnu.gcj.runtime.ExtensionClassLoader{urls=[], parent=null}}}
   at java.net.URLClassLoader.findClass(libgcj.so.7rh)
   at java.lang.ClassLoader.loadClass(libgcj.so.7rh)
   at java.lang.ClassLoader.loadClass(libgcj.so.7rh)
   at java.lang.Class.forName(libgcj.so.7rh)
   at java.lang.Class.initializeClass(libgcj.so.7rh)
   ...6 more



请问如何解决?
回复

使用道具 举报

 楼主| 发表于 2010-9-14 20:56:05 | 显示全部楼层
wildfire.xml的内容如下:
<?xml version="1.0" encoding="UTF-8"?>

<!--

    This file stores bootstrap properties needed by Wildfire.

    Property names must be in the format: "prop.name.is.blah=value"

    That will be stored as:

        <prop>

            <name>

                <is>

                    <blah>value</blah>

                </is>

            </name>

        </prop>



    Most properties are stored in the Wildfire database. A

        property viewer and editor is included in the admin console.

-->

<!-- root element, all properties must be under this element -->

<jive>

    <adminConsole>

        <!-- Disable either port by setting the value to -1 -->

        <port>9090</port>

        <securePort>9091</securePort>

    </adminConsole>



    <admin>

        <!-- Use this section to define users that will have admin privileges. Below,

          you will find two ways to specify which users are admins. Admins will

          have access to the admin console (only local users) and may have also access

          to other functionalities like ad-hoc commands. -->



        <!-- By default, only the user with the username "admin" can login

         to the admin console. Alternatively, you can specify a comma-delimitted

         list usernames that should be authorized to login to the admin console

         by setting the <authorizedUsernames> field below. -->

        <!-- <authorizedUsernames></authorizedUsernames> -->



        <!-- Comma-delimitted list of bare JIDs. The JIDs may belong to local

         or remote users. -->

        <!-- <authorizedJIDs></authorizedJIDs> -->

    </admin>



    <locale>en</locale>



    <!-- Network settings. By default, Wildfire will bind to all network interfaces.

      Alternatively, you can specify a specific network interfaces that the server

      will listen on. For example, 127.0.0.1. This setting is generally only useful

       on multi-homed servers. -->

    <!--

    <network>

        <interface></interface>

    </network>

    -->



    <!-- Example LDAP settings -->

    <!--

    <ldap>

        <host></host>

        <port>389</port>

        <usernameField>uid</usernameField>

        <nameField>cn</nameField>

        <emailField>mail</emailField>

        <baseDN></baseDN>

        <adminDN></adminDN>

        <adminPassword></adminPassword>

    </ldap>

    <provider>

        <user>

            <className>org.jivesoftware.wildfire.ldap.LdapUserProvider</className>

        </user>

        <auth>

            <className>org.jivesoftware.wildfire.ldap.LdapAuthProvider</className>

        </auth>

    </provider>

    -->

    <!-- End example LDAP settings -->       

        <provider>                       

                <user>

                        <className>com.justep.wildfire.JustepUserProvider</className>

                </user>

                <auth>

                        <className>com.justep.wildfire.JustepAuthProvider</className>

                </auth>

        </provider>
   

</jive>
回复 支持 反对

使用道具 举报

 楼主| 发表于 2010-9-14 21:26:20 | 显示全部楼层
还有就是我的IMServer下面没有log目录

我将wildfire.xml改为如下,仍然报错,错误同1楼:
<?xml version="1.0" encoding="UTF-8"?>

<!--

    This file stores bootstrap properties needed by Wildfire.

    Property names must be in the format: "prop.name.is.blah=value"

    That will be stored as:

        <prop>

            <name>

                <is>

                    <blah>value</blah>

                </is>

            </name>

        </prop>



    Most properties are stored in the Wildfire database. A

        property viewer and editor is included in the admin console.

-->

<!-- root element, all properties must be under this element -->

<jive>

    <adminConsole>

        <!-- Disable either port by setting the value to -1 -->

        <port>9090</port>

        <securePort>9091</securePort>

    </adminConsole>



    <admin>

        <!-- Use this section to define users that will have admin privileges. Below,

          you will find two ways to specify which users are admins. Admins will

          have access to the admin console (only local users) and may have also access

          to other functionalities like ad-hoc commands. -->



        <!-- By default, only the user with the username "admin" can login

         to the admin console. Alternatively, you can specify a comma-delimitted

         list usernames that should be authorized to login to the admin console

         by setting the <authorizedUsernames> field below. -->

        <!-- <authorizedUsernames></authorizedUsernames> -->



        <!-- Comma-delimitted list of bare JIDs. The JIDs may belong to local

         or remote users. -->

        <!-- <authorizedJIDs></authorizedJIDs> -->

    </admin>



    <locale>en</locale>



    <!-- Network settings. By default, Wildfire will bind to all network interfaces.

      Alternatively, you can specify a specific network interfaces that the server

      will listen on. For example, 127.0.0.1. This setting is generally only useful

       on multi-homed servers. -->

    <!--

    <network>

        <interface></interface>

    </network>

    -->



    <!-- Example LDAP settings -->

    <!--

    <ldap>

        <host></host>

        <port>389</port>

        <usernameField>uid</usernameField>

        <nameField>cn</nameField>

        <emailField>mail</emailField>

        <baseDN></baseDN>

        <adminDN></adminDN>

        <adminPassword></adminPassword>

    </ldap>

    <provider>

        <user>

            <className>org.jivesoftware.wildfire.ldap.LdapUserProvider</className>

        </user>

        <auth>

            <className>org.jivesoftware.wildfire.ldap.LdapAuthProvider</className>

        </auth>

    </provider>

    -->

    <!-- End example LDAP settings -->       

        <provider>                       

                <user>

                        <className>com.justep.wildfire.JustepUserProvider</className>

                </user>

                <auth>

                        <className>com.justep.wildfire.JustepAuthProvider</className>

                </auth>

        </provider>

   <database>
      <defaultProvider>
        <driver>oracle.jdbc.driver.OracleDriver</driver>
        <serverURL>jdbcracle:thin127.0.0.1:1521:ykwl</serverURL>
        <username>sysykwl</username>
        <password>ykwl</password>
        <minConnections>5</minConnections>
        <maxConnections>15</maxConnections>
        <connectionTimeout>1.0</connectionTimeout>
      </defaultProvider>
   </database>
   <setup>true</setup>
   <connectionProvider>
      <className>org.jivesoftware.database.DefaultConnectionProvider</className>
   </connectionProvider>
</jive>
回复 支持 反对

使用道具 举报

 楼主| 发表于 2010-9-15 09:14:55 | 显示全部楼层
这是什么问题啊?
回复 支持 反对

使用道具 举报

 楼主| 发表于 2010-9-15 09:37:39 | 显示全部楼层
操作系统是   rh linux
什么原因啊?
回复 支持 反对

使用道具 举报

发表于 2010-9-15 13:11:39 | 显示全部楼层
从错误信息上看是没有找到org.jivesoftware.wildfire.starter.JiveClassLoader这个类,有没有人删除过服务端的文件?
回复 支持 反对

使用道具 举报

 楼主| 发表于 2010-9-15 13:58:08 | 显示全部楼层
没有
服务器装好以后没有做个任何删除操作
回复 支持 反对

使用道具 举报

 楼主| 发表于 2010-9-15 15:03:44 | 显示全部楼层
这个怎么解决?
给提供些思路吧
回复 支持 反对

使用道具 举报

 楼主| 发表于 2010-9-15 15:42:40 | 显示全部楼层
??
该如何解决?
回复 支持 反对

使用道具 举报

发表于 2010-9-16 09:16:59 | 显示全部楼层
这个问题是org.jivesoftware.wildfire.component.InternalComponentManager没有到。
这个应该是在IMServer\lib\wildfire.jar里面。

IMServer的目录结构是否有改变过?查找看看该目录结构下有没有这个Class文件。
如果存在检查整个目录结构是否有变化,调整回原来的结构。
回复 支持 反对

使用道具 举报

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

本版积分规则

小黑屋|手机版|Justep Inc.

GMT+8, 2025-7-6 17:55 , Processed in 0.039662 second(s), 15 queries .

Powered by Discuz! X3.4

© 2001-2017 Comsenz Inc.

快速回复 返回顶部 返回列表