4 Replies Latest reply on Jan 19, 2005 11:41 PM by niccolas

a strange startup problem

niccolas Jan 18, 2005 3:14 AM

it's due to the network card, it seems that the jboss service can be started only when the network card was disabled. that's why?and how to resolve it.
here's the error output when starting service:

16:08:30,359 INFO [Server] Core system initialized
16:08:35,921 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour
ce:log4j.xml
16:08:36,312 INFO [WebService] Using RMI server codebase: http://blackhole.auto
 bytel.ca:8083/16:08:36,625 ERROR [NamingService] Starting failed jboss:service=Naming
java.rmi.server.ExportException: Port already in use: 1098; nested exception is:

 java.net.BindException: Address already in use: JVM_Bind
 at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:243)
 at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:178
)
 at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
 at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
 at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:14
5)
 at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:12
9)
 at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.
java:275)
 at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.
java:206)
 at org.jnp.server.Main.initJnpInvoker(Main.java:301)
 at org.jnp.server.Main.start(Main.java:264)
 at org.jboss.naming.NamingService.startService(NamingService.java:221)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:272)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:222)
 at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:144)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
 at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:122)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
 at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:131)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:249)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
 at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:891)
 at $Proxy0.start(Unknown Source)
 at org.jboss.system.ServiceController.start(ServiceController.java:416)
 at org.jboss.system.ServiceController.start(ServiceController.java:438)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:144)
 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:249)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
 at $Proxy4.start(Unknown Source)
 at org.jboss.deployment.SARDeployer.start(SARDeployer.java:261)
 at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:722)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:144)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
 at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:122)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
 at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:131)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:249)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
 at $Proxy5.deploy(Unknown Source)
 at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:413)
 at org.jboss.system.server.ServerImpl.start(ServerImpl.java:310)
 at org.jboss.Main.boot(Main.java:162)
 at org.jboss.Main$1.run(Main.java:423)
 at java.lang.Thread.run(Thread.java:534)
Caused by: java.net.BindException: Address already in use: JVM_Bind
 at java.net.PlainSocketImpl.socketBind(Native Method)
 at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
 at java.net.ServerSocket.bind(ServerSocket.java:318)
 at java.net.ServerSocket.<init>(ServerSocket.java:185)
 at org.jboss.net.sockets.DefaultSocketFactory.createServerSocket(Default
SocketFactory.java:79)
 at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:61
5)
 at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:231)
 ... 62 more
16:08:36,781 WARN [ServiceController] Problem starting service jboss:service=Na
ming
java.rmi.server.ExportException: Port already in use: 1098; nested exception is:

 java.net.BindException: Address already in use: JVM_Bind
 at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:243)
 at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:178
)
 at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
 at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
 at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:14
5)
 at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:12
9)
 at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.
java:275)
 at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.
java:206)
 at org.jnp.server.Main.initJnpInvoker(Main.java:301)
 at org.jnp.server.Main.start(Main.java:264)
 at org.jboss.naming.NamingService.startService(NamingService.java:221)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:272)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:222)
 at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:144)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
 at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:122)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
 at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:131)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:249)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
 at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:891)
 at $Proxy0.start(Unknown Source)
 at org.jboss.system.ServiceController.start(ServiceController.java:416)
 at org.jboss.system.ServiceController.start(ServiceController.java:438)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:144)
 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:249)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
 at $Proxy4.start(Unknown Source)
 at org.jboss.deployment.SARDeployer.start(SARDeployer.java:261)
 at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:722)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)

see the content with red color, the proper RMI service codebase should be http://myComputerName:8083/, why it changes?
by the way, my computer is in a domain of company, does it matter?

1. Re: a strange startup problem

frito Jan 18, 2005 4:49 AM (in response to niccolas)

The server you started is configured with its conf/jboss-service.xml (e.g. the ports used for JNDI). But the port 1098 is in use when you are going to start your server.
Try netstat before you start the server and watch who is using this port on your machine. If this port isn't used at all, it is possible that it is blocked (firewall)...
Actions
2. Re: a strange startup problem

niccolas Jan 18, 2005 9:12 PM (in response to niccolas)
right, the domain server which my computer belong to has block the port, so i must disable the network i can startup.
and now, i modified the jboss-service.xml, as followed:
<mbean code="org.jboss.web.WebService" name="jboss:service=WebService"> <attribute name="Port">8083</attribute>  <attribute name="DownloadServerClasses">true</attribute> <attribute name="Host">${jboss.bind.address}</attribute> <attribute name="BindAddress">127.0.0.1</attribute> </mbean>

it can be started normally without disabling the network. will it cause any other hidden problems?
Actions
3. Re: a strange startup problem

fruehbeck Jan 19, 2005 7:54 AM (in response to niccolas)

I think, the Naming service will only be accessible from localhost (127.0.0.1).

Thomas
Actions
4. Re: a strange startup problem

niccolas Jan 19, 2005 11:41 PM (in response to niccolas)

"fruehbeck" wrote:
I think, the Naming service will only be accessible from localhost (127.0.0.1).

that's right.
I tested another jboss server without logining the domain of company,
there was no error when starting up service, so i think that's due to the computer which is in a domain, that cant be the jboss server on network
Actions

Go to original post