[joerg.vollmer]

Hello,

I could install MyEclipse successfully, but when I try to start JBoss out of Eclipse a message window pops up with the message:

“A configuration occured during startup. Please verify: JBoss JDK name”

Can someone help me?

Jörg Vollmer

[support-michael]

This problem is most likely that your JBoss connector is not configured to launch JBoss using a JDK. A JRE will not work due to requirements for dynamic compilation of JSP and EJB proxy generation. You configure the JDK for JBoss under the JBoss JDK preference page, i.e., Windows->Preferences->MyEclipse->Application Servers->JBoss->JDK. If you don’t explicitly initialize the JVM, MyEclipse will try to use the default JVM environment for which Eclipse is configured. Many times this will be j2rexxx, which is not a JDK. When you visit this page and set or verify the JDK value correctly make sure that you select the “Apply” button followed by “OK” to ensure the preference values are properly persisted.

Michael
MyEclipse Support

[gronnz]

Michael,

I also encountered the same problem and I tried doing your suggestion. I now encountered a new error. It says :

A configuration error occurred during startup. Please verify: Unrecognized option: -Xdebug
Could not create virtual machine.

Please help. Thanks.

[Scott Anderson]

Gronnz,

-Xdebug is the flag that Eclipse passes to the launched JVM to enable remote debugging. If your JDK doesn’t recognize it you’re running a JDK version prior to 1.3, which is not supported by Eclipse. You’ll need to upgrade to at least JDK 1.3.1, although I would HIGHLY recommend you install JDK 1.4.1 so that you’ll be able to use the hotswap debugging features for your J2EE code that MyEclipse provides. A link to the 1.4.1 JDK is available on our download page for your convenience.

Once JDK 1.4.1 is installed, you’ll have to start Eclipse and configure it as the JDK for JBoss by navigating to Preferences->MyEclipse->AppServers->JBoss->JDK and clicking ‘Add’. When specifying the JDK root directory, be sure to use the top level directory, NOT its internal ‘jre’ subdirectory. Click OK.

You should then be off and running.

–Scott
MyEclipse Support

[takai]

Hi!
How config MyEclipse to work with jboss-4.0.0DR1_tomcat-4.1.24?
When run the server, result follow error:
Failed to boot JBoss:
org.jboss.deployment.DeploymentException: url file:/C:/jboss-4.0.0DR1_tomcat-4.1.24/server/JBOSS/conf/jboss-service.xml could not be opened, does it exist?
Please help. Thanks.

[Scott Anderson]

Takai,

We haven’t tested with the JBoss 4.0 / Tomcat bundle yet. However, we have verified full functionality on JBoss 4.0 / Jetty (JBoss Web), with the exception of a minor issue on shutdown that will be addressed in the EA2 release. Without more context, such as the way you’ve configured the server, it’s hard to determine the issue. Does the jboss-service.xml file exist at the path specified? One thing I do notice is that the URL is malformed. It should begin with file:///C: since file:// is the full protocol.

Let us know if you determine the issue or have any more details. We’ll be testing this configuration in the next day or so and that also may shed some light on this problem.

–Scott

MyEclipse Support

[Scott Anderson]

Well, I downloaded and tested against JBoss 4.0 / Tomcat this morning. I configured the JBoss connector just as is shown in the FAQ (http://www.myeclipseide.com/modules.php?op=modload&name=FAQ&file=index&myfaq=yes&id_cat=19&categories=JBoss&parent_id=14#4), but naturally pointed it at the JBoss 4.0 installation.

Upon startup, an error occured and jboss-net did not deploy cleanly. However, this same error occurs when starting JBoss with their run.bat script from the command line so it has nothing to do with MyEclipse. Since the JBoss 4.0 bundle is only a couple of days old as of this posting, I’m surmising that it has a few kinks that need to be worked out.

If you’d like to use JBoss 4.0, I’d suggest you use the JBoss / JBoss Web (Jetty) bundle as this version operates perfectly from both the command line and from within MyEclipse.

–Scott

MyEclipse Support

[takai]

Hello Scott.
Ok, I will going to use JBoss 4.0 / JBoss Web (Jetty).
Thank you very much.

[takai]

Hello Scott.
I instaled JBoss 4.0 and configured the JBoss connector. But, when I start JBoss server, the same error occur:
=============================================
13:51:48,105 INFO [Server] Core system initialized
Failed to boot JBoss:
org.jboss.deployment.DeploymentException: url file:/C:/jboss-4.0.0DR1/server/JBOSS/conf/jboss-service.xml could not be opened, does it exist?
at org.jboss.deployment.DeploymentInfo.<init>(DeploymentInfo.java:191)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:557)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:542)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)13:51:48,185 ERROR [Server] Failed to start
=============================================

JBoss directory struct don’t have the directory C:/jboss-4.0.0DR1/server/JBOSS!!!! Consequently, JBoss don’t find file jboss-service.xml.

How I correct this problem?
Thanks.

[Scott Anderson]

Takai,

I think you have the JBoss Home Directory on the JBoss connector preference page set incorrectly. I downloaded and installed the JBoss/Jetty version and set my JBoss Home Directory in the preference page to be:
C:\dev\appservers\jboss\jboss-4.0.0DR1
The directory C:\dev\appservers\jboss already existed and was the target directory I specified when I unzipped the distribution. The jboss-4.0.0DR1 directory is the top level directory from the zip file and should be selected as the home directory. For the server name I used ‘default’.

–Scott
MyEclipse Support

[takai]

Hello Scott.
I used server name JBOSS. It was wrong. I rename to ‘dafault’ and bingo! It’s work!
Again, thank you very much.
Takai.

[takai]

Hi Scott.
Sorry. But I have one more problem. Jboss started, but follow error happened:
=============================================
21:06:18,727 INFO [jbossweb] Started SocketListener on 0.0.0.0:8080
21:06:18,768 WARN [jbossweb] WARNING: Failed to start: AJP13Listener@0.0.0.0:8009
21:06:18,768 ERROR [JettyService] multiple exceptions…
21:06:18,768 ERROR [JettyService] exception
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:309)
at java.net.ServerSocket.<init>(ServerSocket.java:183)
at org.mortbay.util.ThreadedServer.newServerSocket(ThreadedServer.java:317)
at org.mortbay.util.ThreadedServer.start(ThreadedServer.java:389)
at org.mortbay.http.ajp.AJP13Listener.start(AJP13Listener.java:128)
at org.mortbay.http.HttpServer.start(HttpServer.java:653)
at org.jboss.jetty.JettyService.startService(JettyService.java:176)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:233)
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:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:72)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:45)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:70)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:155)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:544)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:1036)
at $Proxy13.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:401)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:72)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:45)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:70)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:155)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:544)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:172)
at $Proxy6.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:224)
at org.jboss.deployment.DeploymentInfo.start(DeploymentInfo.java:254)
at sun.reflect.GeneratedMethodAccessor38.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:72)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:45)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:70)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:155)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:544)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:1036)
at $Proxy13.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:401)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:72)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:45)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:70)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:155)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:544)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:798)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:594)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:558)
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:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:72)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:45)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:70)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:155)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:544)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:172)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:405)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:529)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:200)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:273)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:233)
at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:72)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:45)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:70)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:155)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:544)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:1036)
at $Proxy1.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:401)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:72)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:45)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:70)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:155)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:544)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:172)
at $Proxy6.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:224)
at org.jboss.deployment.DeploymentInfo.start(DeploymentInfo.java:254)
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:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:72)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:45)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:70)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:155)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:544)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:1036)
at $Proxy1.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:401)
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:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:72)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:45)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:70)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:155)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:544)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:798)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:594)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:558)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:542)
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:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:72)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:45)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:70)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:155)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:544)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:172)
at $Proxy7.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:330)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:238)
at org.jboss.Main.boot(Main.java:165)
at org.jboss.Main$1.run(Main.java:403)
at java.lang.Thread.run(Thread.java:536)
21:06:18,808 INFO [JettyService] Started
=============================================

Please, any sugestions?
Thanks

Takai.

[Scott Anderson]

Takai,

java.net.BindException: Address already in use: JVM_Bind

This means that you’ve already got something running on port 8080. Perhaps a partially started verion of the JBoss/Tomcat bundle? In any case, the easiest solution is to exit Eclipse and kill all Java processes on your computer just to be sure you clear it out. In any case, the problem is easy to resolve, just be sure you’re not already running Tomcat somwhere.

–Scott
MyEclipse Support

[takai]

Hello Scott.
It’s work!
Again: THANK YOU VERY VERY MUCH.
Takai.

[Scott Anderson]

Takai,

You are most certainly welcome.

–Scott
MyEclipse Support

[Author]

Posts