- This topic has 2 replies, 2 voices, and was last updated 10 years, 3 months ago by support-swapna.
-
AuthorPosts
-
eugenejsnParticipantMyEclipse Blue 2014 on SUSE Linux.
First start the JBoss Server (7.1.1). Then from the IDE’s server panel, click on the red STOP button. Error comae up:
WARNING: -logmodule is deprecated. Please use the system property ‘java.util.logging.manager’ or the ‘java.util.logging.LogManager’ service loader.
14:21:33,860 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
WARN: can’t load the config file because JBOSS_HOME environment variable is not set.
14:21:34,063 INFO [org.xnio] XNIO Version 3.0.3.GA
14:21:34,071 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
14:21:34,077 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
org.jboss.as.cli.CliInitializationException: Failed to connect to the controller
at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:229)
at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:195)
at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.modules.Module.run(Module.java:260)
at org.jboss.modules.Main.main(Main.java:291)
Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9999
at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:639)
at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:613)
at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:227)
… 8 moreWhat are wrong? Also, where and how to set the JBOSS_HOME environment variable?
Thanks
Eugene
support-swapnaModeratorEugene,
The warning can be ignored as per this thread : http://docs.jboss.org/jbossas/7/plugins/maven/latest/faq.html
You can ensure that the JBOSS_HOME is set in your environment possibly either in the .profile file in your home directory or you can edit the JBoss connector preferences, under JDK and VM Arguments, set: -DJBOSS_HOME=D:/JBoss
Let us know how it works for you.
support-swapnaModeratorEugene,
Sorry for incorrectly stating that the JBOSS_HOME environment variable could be set via the VM arguments in the JBoss connector. If you want to get rid of the warning then the environment variable needs to be set before MyEclipse is launched.
Hope this helps.
-
AuthorPosts