2009-02-25 111 views
4

我在Tomcat server.xml文件的Tomcat安全领域中引用LDAP。然而,我收到了一个不寻常的错误:Tomcat没有启动,进入日志我发现它无法连接到localhost:389 - Tomcat的默认LDAP URL。配置LDAP时出现Tomcat错误

然而,Tomcat的配置来点不同的URL(不在同一台机器的外部URL;不同的一个完全),像这样:

<Realm className="org.apache.catalina.realm.JNDIRealm" debug="99" 
     connectionURL="ldap://XXX.XX.XX.XXX:389" 
     userSubtree="true" 
     userPattern="(cn={0},ou=XXXXXXXX,ou=XXXXX,o=XXX)" 
     roleBase="ou=XXXXXXXX,o=XXX" 
     roleName="cn" 
     roleSearch="member={0}" 
     connectionName="cn=XXXXXXXX,ou=XXXXXXXX,o=XXX" 
     connectionPassword="XXXXXXXX"/> 

,基本上我不知道为什么它的仍在看本地主机:389。如果有人遇到过这个,我会很感激一些帮助!我已经搜索了一段时间,但是当人们将错误粘贴到页面中时,似乎没有多少答案。如果有人有任何建议,我会很感激。

这里的日志文件:

24-Feb-2009 11:38:45 org.apache.coyote.http11.Http11Protocol init 
INFO: Initializing Coyote HTTP/1.1 on http-8443 
Starting service Tomcat-Standalone 
Apache Tomcat/4.1.31 
Catalina.start: LifecycleException: Exception opening directory server connection:  
javax.naming.CommunicationException: localhost:389 
    [Root exception is java.net.ConnectException: Connection refused: connect] 
LifecycleException: Exception opening directory server connection: 
javax.naming.CommunicationException: localhost:389 
    [Root exception is java.net.ConnectException: Connection refused: connect] 
at org.apache.catalina.realm.JNDIRealm.start(JNDIRealm.java:1558) 
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1126) 
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:316) 
at org.apache.catalina.core.StandardService.start(StandardService.java:450) 
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2143) 
at org.apache.catalina.startup.Catalina.start(Catalina.java:463) 
at org.apache.catalina.startup.Catalina.execute(Catalina.java:350) 
at org.apache.catalina.startup.Catalina.process(Catalina.java:129) 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
at java.lang.reflect.Method.invoke(Method.java:324) 
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:156) 
----- Root Cause ----- 
javax.naming.CommunicationException: localhost:389 
    [Root exception is java.net.ConnectException: Connection refused: connect] 
at com.sun.jndi.ldap.Connection.<init>(Connection.java:204) 
at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:119) 
at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1668) 
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2599) 
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:290) 
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:53) 
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662) 
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243) 
at javax.naming.InitialContext.init(InitialContext.java:219) 
at javax.naming.InitialContext.<init>(InitialContext.java:195) 
at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:80) 
at org.apache.catalina.realm.JNDIRealm.open(JNDIRealm.java:1482) 
at org.apache.catalina.realm.JNDIRealm.start(JNDIRealm.java:1556) 
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1126) 
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:316) 
at org.apache.catalina.core.StandardService.start(StandardService.java:450) 
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2143) 
at org.apache.catalina.startup.Catalina.start(Catalina.java:463) 
at org.apache.catalina.startup.Catalina.execute(Catalina.java:350) 
at org.apache.catalina.startup.Catalina.process(Catalina.java:129) 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
at java.lang.reflect.Method.invoke(Method.java:324) 
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:156) 
Caused by: java.net.ConnectException: Connection refused: connect 
at java.net.PlainSocketImpl.socketConnect(Native Method) 
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305) 
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171) 
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158) 
at java.net.Socket.connect(Socket.java:452) 
at java.net.Socket.connect(Socket.java:402) 
at java.net.Socket.<init>(Socket.java:309) 
at java.net.Socket.<init>(Socket.java:124) 
at com.sun.jndi.ldap.Connection.createSocket(Connection.java:346) 
at com.sun.jndi.ldap.Connection.<init>(Connection.java:181) 
... 24 more 
Stopping service Tomcat-Standalone 
Catalina.stop: LifecycleException: Coyote connector has not been started 
LifecycleException: Coyote connector has not been started 
at org.apache.coyote.tomcat4.CoyoteConnector.stop(CoyoteConnector.java:1296) 
at org.apache.catalina.core.StandardService.stop(StandardService.java:499) 
at org.apache.catalina.core.StandardServer.stop(StandardServer.java:2178) 
at org.apache.catalina.startup.Catalina.start(Catalina.java:494) 
at org.apache.catalina.startup.Catalina.execute(Catalina.java:350) 
at org.apache.catalina.startup.Catalina.process(Catalina.java:129) 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
at java.lang.reflect.Method.invoke(Method.java:324) 
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:156) 
+0

你确定server.xml是你配置的唯一地方吗?据我所知, – tehvan 2009-02-25 09:57:47

+0

。我正在进入已禁用的现有安装,我不认为它是其他任何地方。哪里会是好看的地方? 干杯 – 2009-03-02 10:19:29

回答

1
  • 许多雄猫配置元素的支持调试属性。尝试将debug =“99”添加到领域配置。 (见雄猫realm-howto的例子,搜索调试=“99”
  • 作出额外额外肯定它不是一个错字,例如在连接大写的URL
  • 查看conf/server.xml中是否有其他提及“localhost”(或“127.0”)的信息
  • 查看是否有任何提及的“localhost”(或“127.0”)在conf/*/*/*。xml(尽管这不应该导致tomcat不启动:它只会影响该应用程序)
  • 从最小的server.xml开始 - 如果使用tomcat 5.xa文件“server-minimal .xml“的交付方式比默认的server.xml更易读
  • 请确保您不受server.xml中各种xml注释的影响 - 我多次被它们咬伤。
2

尝试添加与alternateURL具有相同值的'alternateURL'属性。出于某种原因,当我遇到类似问题时,这对我有用。

2

我知道这是一个非常老的帖子,但是我最近遇到了这个问题,问题在于我将我的JNDIRealm嵌套在LockoutRealm中。

通过将JNDIRealm作为我的顶级领域,我不再有所描述的问题。如果你确实需要锁定领域,这个解决方案是没有用的。

相关问题