Jboss服务器启动异常

我在Windows 7 64位计算机上启动Jboss-4.0.3SP1时发现以下异常。我正在研究这个，看看是否有任何港口冲突等..任何想法从你将不胜感激！Jboss服务器启动异常

14:52:13,067 WARN [ServiceController] Problem starting service jboss:service=invoker,type=pooled 
java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind 
     at java.net.PlainSocketImpl.socketBind(Native Method) 
     at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359) 
     at java.net.ServerSocket.bind(ServerSocket.java:319) 
     at java.net.ServerSocket.<init>(ServerSocket.java:185) 
     at org.jboss.invocation.pooled.server.PooledInvoker.startService(PooledInvoker.java:205) 
     at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:274) 
     at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:230) 
     at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) 
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
     at java.lang.reflect.Method.invoke(Method.java:592) 
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) 
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) 
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) 
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245) 
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) 
     at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:943) 
     at $Proxy0.start(Unknown Source) 
     at org.jboss.system.ServiceController.start(ServiceController.java:428) 
     at org.jboss.system.ServiceController.start(ServiceController.java:446) 
     at org.jboss.system.ServiceController.start(ServiceController.java:446) 
     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:592) 
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) 
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) 
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) 
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245) 
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) 
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) 
     at $Proxy4.start(Unknown Source) 
     at org.jboss.deployment.SARDeployer.start(SARDeployer.java:285) 
     at org.jboss.deployment.MainDeployer.start(MainDeployer.java:989) 
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:790) 
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753) 
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:737) 
     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:592) 
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) 
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) 
     at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118) 
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) 
     at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127) 
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) 
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245) 
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) 
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) 
     at $Proxy5.deploy(Unknown Source) 
     at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:453) 
     at org.jboss.system.server.ServerImpl.start(ServerImpl.java:330) 
     at org.jboss.Main.boot(Main.java:187) 
     at org.jboss.Main$1.run(Main.java:438) 
     at java.lang.Thread.run(Thread.java:595)

来源

2010-12-17 Java Guy

也许你可以显示你用来调用JBoss的命令呢？ – 2010-12-18 00:53:13

呀！修复了这个问题，其中一个端口正在使用中。

<attribute name="ServerBindPort">4445</attribute>

4445是在使用，所以改为4446

文件名：的jboss-4.0.3SP1 \服务器\ DEFAULT \的conf \的jboss-service.xml的

netstat的是有用的识别端口

netstat -an |find /i "4445"

TCP 0.0.0.0:4445 0.0.0.0:0 LISTENING

来源

2010-12-20 22:00:51

这就是我所说的。 – 2010-12-21 12:54:50

最有可能的港口冲突。例如，用'netstat'命令检查计算机上打开的端口列表。

来源

2010-12-17 22:12:32 maximdim

使用netstat命令检查这些端口是否已在您的机器上运行：1098,1099 4444,4445,8009,8080,8083,8093。最有可能的端口8080已在您的机器上运行，但检查他们全部。

来源

2010-12-17 22:36:03

有时候，这可能是由于防火墙服务。

它也更好地尝试改变在server.xml中的端口号，这是在\服务器\默认发现\部署\ jbossweb-tomcat55.sar

来源

2010-12-18 13:15:29

Jboss服务器启动异常

回答

相关问题