problem starting Naming service with jboss-4.2.2.GA

[veraz01170]

Hello,

I am using bind address 0.0.0.0, default mode. java sdk jdk1.5.0_11.

Using jboss 4.0.5.GA is not causing any problem.

When starting jboss 4.2.2.GA I get very early in the process the following NullPointerException :

2007-11-16 00:18:25,372 DEBUG [org.jboss.naming.Naming] Creating NamingServer stub, theServer=null,rmiPort=1098,clientSocketFactory=
null,serverSocketFactory=org.jboss.net.sockets.DefaultSocketFactory@fbc4815d[bindAddress=/0.0.0.0]
2007-11-16 00:18:25,372 DEBUG [org.jboss.naming.NamingService]
java.lang.NullPointerException
at org.jnp.server.Main.getNamingInstance(Main.java:301)
at org.jnp.server.Main.initJnpInvoker(Main.java:354)
at org.jnp.server.Main.start(Main.java:316)
at org.jboss.naming.NamingService.startService(NamingService.java:284)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
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:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
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:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:595)



With both versions i am keeping original jboss-service.xml and xmdesc dependencies untouched.



-> Any ideas what the problem could be would be very,very appreciated.



Thanks,

[veraz01170]

this is now solved by reinstalling jboss from source so there was a glitch somewhere.

[klein01]

veraz,

I'm a newbie to jboss and I got exact same issues when starting jboss 4.2.2.

Can you share a little more detail on how do you re-install from source? Do you mean you install it using the GUI installer.jar? I tried to download the jboss-4.2.2.src and then rebuild it but the naming services issues (NullPointerExceptions) are still there when I start my jboss 4.2.2.

thanks,
klein

[dimitris]

You don't need to build anything from source. Just grab the 4.2.2.GA binary distro, unzip, set JAVA_HOME, cd to the ./bin directory and ./run.sh

[klein01]

I also tried the binary distro first and got that same issue with fail to start Naming services (NullPointerException).

I saw veraz's comments that a workaround by re-installing from source and kindda not sure what is the workaround. If you have any clue on how should I trouble-shoot this, please share.

My application worked fine w/ jboss4.0.5 but when I upgrade to 4.2.2, the app server fails to start very early due to failures on starting naming services (NullPointerException, exactly the same exceptions Veraz posted above). I got stuck for some time on this exception and have no clue how to trouble-shoot.

Thanks for any help,
klein

[peterj]

Try this. Start JBossAS without your app deployed, see if it starts properly. Then deploy your application. What errors do you get then?