Win a copy of Mesos in Action this week in the Cloud/Virtualizaton forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

problem while starting jboss5.0

 
uttam kumar
Ranch Hand
Posts: 128
Eclipse IDE Java Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi,
I am getting the following problem while starting up the JBoss5.0 server......i couldnt understand the problem.
following is the error log generated in server.log file.

2009-01-28 12:25:19.488,DEBUG,org.jboss.system.ServiceCreator,JBoss,main,Created mbean: jboss:service=Naming,
2009-01-28 12:25:19.488,DEBUG,org.jboss.system.ServiceConfigurator,JBoss,main,CallByValue set to false in jboss:service=Naming,
2009-01-28 12:25:19.488,DEBUG,org.jboss.system.ServiceConfigurator,JBoss,main,Port set to 2099 in jboss:service=Naming,
2009-01-28 12:25:19.504,DEBUG,org.jboss.system.ServiceConfigurator,JBoss,main,BindAddress set to 127.0.0.1 in jboss:service=Naming,
2009-01-28 12:25:19.504,DEBUG,org.jboss.system.ServiceConfigurator,JBoss,main,RmiPort set to 1098 in jboss:service=Naming,
2009-01-28 12:25:19.504,DEBUG,org.jboss.system.ServiceConfigurator,JBoss,main,RmiBindAddress set to 127.0.0.1 in jboss:service=Naming,
2009-01-28 12:25:19.504,DEBUG,org.jboss.system.ServiceConfigurator,JBoss,main,LookupPool set to MBeanProxyExt[jboss.system:service=ThreadPool] in jboss:service=Naming,
2009-01-28 12:25:19.519,DEBUG,org.jboss.system.ServiceConfigurator,JBoss,main,Naming set to MBeanProxyExt[jboss:service=NamingBeanImpl] in jboss:service=Naming,
2009-01-28 12:25:19.535,ERROR,org.jboss.kernel.plugins.dependency.AbstractKernelController,JBoss,main,Error installing to Configured: name=jboss:service=Naming state=Instantiated mode=Manual requiredState=Configured,
java.lang.RuntimeException: Exception setting attribute Naming on mbean jboss:service=Naming
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:170)
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:114)
at org.jboss.system.microcontainer.ConfigureAction.installAction(ConfigureAction.java:58)
at org.jboss.system.microcontainer.ConfigureAction.installAction(ConfigureAction.java:42)
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
at org.jboss.system.ServiceController.install(ServiceController.java:274)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:95)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:45)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:274)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
at org.jboss.Main.boot(Main.java:209)
at org.jboss.Main$1.run(Main.java:547)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.IllegalArgumentException: Unable to find operation setNaming(org.jnp.server.NamingBean)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:231)
at org.jboss.mx.interceptor.AttributeDispatcher.invoke(AttributeDispatcher.java:128)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanAttributeInterceptor.invoke(ModelMBeanAttributeInterceptor.java:103)
at org.jboss.mx.interceptor.PersistenceInterceptor.invoke(PersistenceInterceptor.java:76)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at org.jboss.mx.server.AbstractMBeanInvoker.setAttribute(AbstractMBeanInvoker.java:461)
at org.jboss.mx.server.MBeanServerImpl.setAttribute(MBeanServerImpl.java:617)
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:166)
... 40 more

*** CONTEXTS IN ERROR: Name -> Error

vfsfile:/D:/OTPServer/common/3rdparty/jboss/server/default/conf/jboss-service.xml -> java.lang.IllegalArgumentException: Unable to find operation setNaming(org.jnp.server.NamingBean)


Thanks in advance..
 
Jaikiran Pai
Marshal
Pie
Posts: 10447
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Which exact version of JBoss 5.0 are you using? And which version of Java? Did you do any changes to the downloaded JBoss? How do you start the server? And do you see any other errors on the console?
 
uttam kumar
Ranch Hand
Posts: 128
Eclipse IDE Java Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi ,
I have downloaded jboss-5.0.0.GA-jdk6.zip and using jdk1.6 update 11
i dont see any other error on the console......
i start jboss using a batch file which simply first set some paths and then run the run.bat file of jboss.
 
Jaikiran Pai
Marshal
Pie
Posts: 10447
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
uttam kumar wrote:hi ,

i start jboss using a batch file which simply first set some paths and then run the run.bat file of jboss.


Can you post the contents of the additional bat file you have written? And what's that bat file meant for?

While posting logs or xml content or code, please remember to wrap it in a code block by using the Code button in the message editor window. Please use the Preview button to ensure that your post is correctly formatted.
 
Javid Jamae
Author
Ranch Hand
Posts: 198
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Also, please provide the output of the following command from the prompt where you tried to start JBoss:

java -version
 
Peter Johnson
author
Bartender
Posts: 5852
7
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This root error:

Caused by: java.lang.IllegalArgumentException: Unable to find operation setNaming(org.jnp.server.NamingBean)


suggests to me that you have a stray JAR file somewhere in your classpath. If you have the CLASSPATH env var set, unset it (setting CLASSPATH is is sure-fire way top get in trouble). If that doesn't help, added "-verbose:class" to JAVA_OPTS in run.bat (or you can set JAVA_OPTS before running run.bat). This JVM option prints out the name of each class file loaded and the JAR it came from. You will have to redirect stdout/stderr to a file to get all of the result. Scan the output for org.jnp.server.NamingBean and see where it was loaded from. Or look to see if there are any JAR files other that the rt.jar or one fo the JBoss JARs being loaded.
 
uttam kumar
Ranch Hand
Posts: 128
Eclipse IDE Java Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi,
i am not able to attach the log file created on the command prompt. So I am pasteing few lines of the log file...Please see it and provide the solution.








 
Peter Johnson
author
Bartender
Posts: 5852
7
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Please post the server/xxx/conf/jboss-service.xml file.

Also, post the console output, starting with the command you entered and ending with the first line of the exception. This output should provide use with some clues as to you environment.
 
uttam kumar
Ranch Hand
Posts: 128
Eclipse IDE Java Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi,
this is the Jboss-service.xml file that I am using
 
uttam kumar
Ranch Hand
Posts: 128
Eclipse IDE Java Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
and this is the console output.....
 
Javid Jamae
Author
Ranch Hand
Posts: 198
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It looks like your hard-coding the Port for the NamingService in your jboss-service.xml file. You'll probably want to restore your jboss-service.xml file and use the server/xxx/conf/bindings.xml file instead. Then start your application with the jboss.service.binding.set property pointing to the appropriate port configuration.
 
Peter Johnson
author
Bartender
Posts: 5852
7
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It looks like you made several changes in jboss-service.xml. You also wrote another bat file to run run.bat. I suggest that you go back to a very basic JBoss AS installation without any changes and try that first, using run.bat to start the app server. If that works, then one of the changes you made caused the problems you are seeing.

The other thing I would do is get the JDK out of program files - spaces in paths tend to confuse various Java libraries. You do not have to re-install - simply move (or copy) the C:\Program Files\Java\jdk1.6.0_11 directory elsewhere (mine is at c:/apps/Java/jdk1.6.0_11) and set JAVA_HOME to reference it.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic