JBossDeveloper

Are this error bound to JB 3.2 ? Poinsarx, if so, are you using RC1 or the latest CVS build ?

I am using 3.0.6, but if you insist I will consider moving to 3.2.X

No, please stay were you like. IDE's are for the people and not vice versa (-:

I'd like to ask you for a favor.

If you change to the debug view there is a child node of the launch which represent the started java process. If you right click this process it's displayed how the java process was called.

Could you post here the output of this for the not working launch of the JBoss-IDE and for the working one you are doing directly via the Eclipse build-in launch.

For (non-working) JBoss-IDE :
/usr/lib/j2se/1.4/bin/java -Djboss.home=/var/jboss -classpath /var/jboss/bin/run.jar:/usr/lib/j2se/1.4/lib/tools.jar:/var/jboss/bin/run.jar:/usr/lib/j2se/1.4/lib/tools.jar:/var/jboss/bin/run.jar:/usr/lib/j2se/1.4/lib/tools.jar -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,suspend=y,address=localhost:6450 org.jboss.Main -cop

For working manual launch :
/usr/lib/j2se/1.4/bin/java -Xbootclasspath:/usr/lib/j2se/1.4/jre/lib/rt.jar:/usr/lib/j2se/1.4/jre/lib/sunrsasign.jar:/usr/lib/j2se/1.4/jre/lib/jsse.jar:/usr/lib/j2se/1.4/jre/lib/jce.jar:/usr/lib/j2se/1.4/jre/lib/charsets.jar:/usr/lib/j2se/1.4/jre/lib/ext/sunjce_provider.jar:/usr/lib/j2se/1.4/jre/lib/ext/dnsns.jar:/usr/lib/j2se/1.4/jre/lib/ext/localedata.jar:/usr/lib/j2se/1.4/jre/lib/ext/ldapsec.jar -classpath /var/jboss/bin/run.jar:/usr/lib/j2se/1.4/lib/tools.jar org.jboss.Main -cop

The working manual launch is not in debugging mode. It would be great if you could post the debugging launch info as well.

I am not sure if you want full launch info. Don't hesitate to ask for it. I will give you the beginning.

Non working launch info :

Message : "couldn't connect to VM"
Console : Exception in thread "main" java.lang.NoClassDefFoundError:
metadata/.log :

!ENTRY org.jboss.ide.eclipse.launcher 4 0 févr. 18, 2003 12:46:21.629
!MESSAGE Internal Error
!STACK 1
org.eclipse.core.runtime.CoreException[120]: java.net.SocketException: Socket closed
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353)
at java.net.ServerSocket.implAccept(ServerSocket.java:439)
at java.net.ServerSocket.accept(ServerSocket.java:410)
at org.eclipse.jdi.internal.connect.SocketTransportImpl.accept(SocketTransportImpl.java:78)
at org.eclipse.jdi.internal.connect.SocketListeningConnectorImpl.accept(SocketListeningConnectorImpl.java:117)
at org.eclipse.jdt.internal.launching.StandardVMDebugger$ConnectRunnable.run(StandardVMDebugger.java:71)
at java.lang.Thread.run(Thread.java:536)
!ENTRY org.eclipse.jdt.launching 4 120 févr. 18, 2003 12:46:21.630
!MESSAGE Could not connect to VM
!STACK 0
java.net.SocketException: Socket closed
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353)
at java.net.ServerSocket.implAccept(ServerSocket.java:439)
at java.net.ServerSocket.accept(ServerSocket.java:410)
at org.eclipse.jdi.internal.connect.SocketTransportImpl.accept(SocketTransportImpl.java:78)
at org.eclipse.jdi.internal.connect.SocketListeningConnectorImpl.accept(SocketListeningConnectorImpl.java:117)
at org.eclipse.jdt.internal.launching.StandardVMDebugger$ConnectRunnable.run(StandardVMDebugger.java:71)
at java.lang.Thread.run(Thread.java:536)



Working manual launch info :

12:38:47,440 DEBUG [Server] server type: class org.jboss.system.server.ServerImpl
12:38:47,442 INFO [Server] JBoss Release: JBoss-3.0.6 CVSTag=JBoss_3_0_6
12:38:47,472 DEBUG [Server] Using config: org.jboss.system.server.ServerConfigImpl@1662dc8
12:38:47,472 INFO [Server] Home Dir: /var/jboss-3.0.6
12:38:47,473 INFO [Server] Home URL: file:/var/jboss-3.0.6/
12:38:47,474 INFO [Server] Library URL: file:/var/jboss-3.0.6/lib/
12:38:47,482 INFO [Server] Patch URL: null
12:38:47,483 INFO [Server] Server Name: op
12:38:47,483 INFO [Server] Server Home Dir: /var/jboss-3.0.6/server/op
12:38:47,484 INFO [Server] Server Home URL: file:/var/jboss-3.0.6/server/op/
12:38:47,484 INFO [Server] Server Data Dir: /var/jboss-3.0.6/server/op/db
12:38:47,485 INFO [Server] Server Temp Dir: /var/jboss-3.0.6/server/op/tmp
12:38:47,486 INFO [Server] Server Config URL: file:/var/jboss-3.0.6/server/op/conf/
12:38:47,486 INFO [Server] Server Library URL: file:/var/jboss-3.0.6/server/op/lib/
12:38:47,487 INFO [Server] Root Deployemnt Filename: jboss-service.xml
12:38:47,504 INFO [Server] Starting General Purpose Architecture (GPA)...
12:38:47,872 DEBUG [Server] Created MBeanServer: org.jboss.mx.server.MBeanServerImpl@1e04cbf
12:38:47,892 DEBUG [Server] Boot url list: [file:/var/jboss-3.0.6/server/op/conf/]
12:38:47,893 DEBUG [Server] Creating loader for URL: file:/var/jboss-3.0.6/server/op/conf/
12:38:47,911 DEBUG [UnifiedClassLoader] New jmx UCL with url file:/var/jboss-3.0.6/server/op/conf/
12:38:47,917 DEBUG [UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3@18fb1f7{ url=file:/var/jboss-3.0.6/server/op/conf/ ,addedOrder=0}
12:38:47,984 INFO [ServerInfo] Java version: 1.4.1,Blackdown Java-Linux Team
12:38:47,987 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM Blackdown-1.4.1-beta,Blackdown Java-Linux Team
12:38:47,987 INFO [ServerInfo] OS-System: Linux 2.4.20-xp,i386
12:38:47,988 DEBUG [ServerInfo] Full System Properties Dump
12:38:47,989 DEBUG [ServerInfo] java.runtime.name: Java(TM) 2 Runtime Environment, Standard Edition
12:38:47,990 DEBUG [ServerInfo] jboss.server.base.dir: /var/jboss-3.0.6/server
12:38:47,990 DEBUG [ServerInfo] java.protocol.handler.pkgs: org.jboss.net.protocol
12:38:47,990 DEBUG [ServerInfo] sun.boot.library.path: /usr/lib/j2se/1.4/jre/lib/i386
12:38:47,990 DEBUG [ServerInfo] jboss.server.lib.url: file:/var/jboss-3.0.6/server/op/lib/
12:38:47,990 DEBUG [ServerInfo] java.vm.version: Blackdown-1.4.1-beta
12:38:47,990 DEBUG [ServerInfo] java.vm.vendor: Blackdown Java-Linux Team
12:38:47,990 DEBUG [ServerInfo] java.vendor.url: http://www.blackdown.org/
12:38:47,990 DEBUG [ServerInfo] path.separator: :
12:38:47,991 DEBUG [ServerInfo] java.vm.name: Java HotSpot(TM) Client VM
12:38:47,991 DEBUG [ServerInfo] file.encoding.pkg: sun.io
12:38:47,991 DEBUG [ServerInfo] user.country: FR
12:38:47,991 DEBUG [ServerInfo] sun.os.patch.level: unknown
12:38:47,991 DEBUG [ServerInfo] java.vm.specification.name: Java Virtual Machine Specification
12:38:47,991 DEBUG [ServerInfo] user.dir: /usr/local/eclipse
12:38:47,991 DEBUG [ServerInfo] jboss.server.base.url: file:/var/jboss-3.0.6/server/
12:38:47,991 DEBUG [ServerInfo] java.runtime.version: Blackdown-1.4.1-beta
12:38:47,991 DEBUG [ServerInfo] java.awt.graphicsenv: sun.awt.X11GraphicsEnvironment
12:38:47,992 DEBUG [ServerInfo] java.endorsed.dirs: /usr/lib/j2se/1.4/jre/lib/endorsed
12:38:47,993 DEBUG [ServerInfo] os.arch: i386
12:38:47,993 DEBUG [ServerInfo] java.io.tmpdir: /tmp
12:38:47,993 DEBUG [ServerInfo] line.separator:

12:38:47,993 DEBUG [ServerInfo] jbossmx.loader.repository.class: org.jboss.mx.loading.UnifiedLoaderRepository3
12:38:47,993 DEBUG [ServerInfo] java.vm.specification.vendor: Sun Microsystems Inc.
12:38:47,993 DEBUG [ServerInfo] os.name: Linux
12:38:47,993 DEBUG [ServerInfo] sun.java2d.fontpath:
12:38:47,994 DEBUG [ServerInfo] jboss.server.temp.dir: /var/jboss-3.0.6/server/op/tmp
12:38:47,994 DEBUG [ServerInfo] jboss.home.dir: /var/jboss-3.0.6
12:38:47,994 DEBUG [ServerInfo] java.library.path: /usr/lib/j2se/1.4/jre/lib/i386/client:/usr/lib/j2se/1.4/jre/lib/i386:/usr/lib/j2se/1.4/jre/../lib/i386:/usr/lib:/lib:/usr/lib/j2se/i386
12:38:47,994 DEBUG [ServerInfo] jboss.server.home.dir: /var/jboss-3.0.6/server/op
12:38:47,994 DEBUG [ServerInfo] java.specification.name: Java Platform API Specification
12:38:47,994 DEBUG [ServerInfo] java.class.version: 48.0
12:38:47,994 DEBUG [ServerInfo] jboss.server.config.url: file:/var/jboss-3.0.6/server/op/conf/
12:38:47,994 DEBUG [ServerInfo] java.util.prefs.PreferencesFactory: java.util.prefs.FileSystemPreferencesFactory
12:38:47,994 DEBUG [ServerInfo] os.version: 2.4.20-xp
12:38:47,995 DEBUG [ServerInfo] jboss.home.url: file:/var/jboss-3.0.6/
12:38:47,995 DEBUG [ServerInfo] user.home: /home/xpoinsar
12:38:47,995 DEBUG [ServerInfo] user.timezone: Europe/Paris
12:38:47,995 DEBUG [ServerInfo] java.awt.printerjob: sun.print.PSPrinterJob
12:38:47,995 DEBUG [ServerInfo] java.specification.version: 1.4
12:38:47,995 DEBUG [ServerInfo] file.encoding: ISO-8859-1
12:38:47,995 DEBUG [ServerInfo] jboss.server.home.url: file:/var/jboss-3.0.6/server/op/
12:38:47,995 DEBUG [ServerInfo] user.name: xpoinsar
12:38:47,996 DEBUG [ServerInfo] java.class.path: /var/jboss/bin/run.jar:/usr/lib/j2se/1.4/lib/tools.jar
12:38:47,996 DEBUG [ServerInfo] jboss.lib.url: file:/var/jboss-3.0.6/lib/
12:38:47,996 DEBUG [ServerInfo] jboss.server.name: op
12:38:47,996 DEBUG [ServerInfo] java.vm.specification.version: 1.0
12:38:47,996 DEBUG [ServerInfo] sun.arch.data.model: 32
12:38:47,996 DEBUG [ServerInfo] java.home: /usr/lib/j2se/1.4/jre
12:38:47,996 DEBUG [ServerInfo] java.specification.vendor: Sun Microsystems Inc.
12:38:47,996 DEBUG [ServerInfo] user.language: fr
12:38:47,996 DEBUG [ServerInfo] java.vm.info: mixed mode
12:38:47,997 DEBUG [ServerInfo] java.version: 1.4.1
12:38:47,997 DEBUG [ServerInfo] java.ext.dirs: /usr/lib/j2se/1.4/jre/lib/ext:/usr/lib/j2se/ext
12:38:47,997 DEBUG [ServerInfo] jboss.server.data.dir: /var/jboss-3.0.6/server/op/db
12:38:47,997 DEBUG [ServerInfo] sun.boot.class.path: /usr/lib/j2se/1.4/jre/lib/rt.jar:/usr/lib/j2se/1.4/jre/lib/sunrsasign.jar:/usr/lib/j2se/1.4/jre/lib/jsse.jar:/usr/lib/j2se/1.4/jre/lib/jce.jar:/usr/lib/j2se/1.4/jre/lib/charsets.jar:/usr/lib/j2se/1.4/jre/lib/ext/sunjce_provider.jar:/usr/lib/j2se/1.4/jre/lib/ext/dnsns.jar:/usr/lib/j2se/1.4/jre/lib/ext/localedata.jar:/usr/lib/j2se/1.4/jre/lib/ext/ldapsec.jar
12:38:47,997 DEBUG [ServerInfo] java.vendor: Blackdown Java-Linux Team
12:38:47,997 DEBUG [ServerInfo] file.separator: /
12:38:47,997 DEBUG [ServerInfo] java.vendor.url.bug: http://www.blackdown.org/cgi-bin/jdk
12:38:47,997 DEBUG [ServerInfo] sun.cpu.endian: little
12:38:47,997 DEBUG [ServerInfo] sun.io.unicode.encoding: UnicodeLittle
12:38:47,998 DEBUG [ServerInfo] sun.cpu.isalist:
12:38:48,069 INFO [ServiceController] Controller MBean online
12:38:48,088 DEBUG [Server] Registered service controller: jboss.system:service=ServiceController
12:38:48,253 INFO [MainDeployer] Creating
12:38:48,317 INFO [MainDeployer] Created
12:38:48,319 INFO [MainDeployer] Starting
12:38:48,320 INFO [MainDeployer] Started
12:38:48,321 DEBUG [Server] Shutdown hook added
12:38:48,348 INFO [JARDeployer] Creating
12:38:48,349 INFO [JARDeployer] Created
12:38:48,350 INFO [JARDeployer] Starting
12:38:48,351 INFO [MainDeployer] Adding deployer: org.jboss.deployment.JARDeployer@1b9240e
12:38:48,352 INFO [JARDeployer] Started
12:38:48,368 DEBUG [SARDeployer] ServiceDeployer preregistered with mbean server
12:38:48,383 INFO [SARDeployer] Creating
12:38:48,384 INFO [SARDeployer] Created
12:38:48,385 INFO [SARDeployer] Starting
12:38:48,385 INFO [MainDeployer] Adding deployer: org.jboss.deployment.SARDeployer@184ec44
12:38:48,425 INFO [SARDeployer] Started
12:38:48,425 INFO [Server] Core system initialized
12:38:48,433 INFO [MainDeployer] Starting deployment of package: file:/var/jboss-3.0.6/server/op/conf/jboss-service.xml
12:38:48,433 DEBUG [MainDeployer] Starting deployment (init step) of package at: file:/var/jboss-3.0.6/server/op/conf/jboss-service.xml
12:38:48,463 DEBUG [UnifiedClassLoader] New jmx UCL with url file:/var/jboss-3.0.6/server/op/tmp/deploy/server/op/conf/jboss-service.xml/1.jboss-service.xml
12:38:48,464 DEBUG [UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3@1808199{ url=file:/var/jboss-3.0.6/server/op/tmp/deploy/server/op/conf/jboss-service.xml/1.jboss-service.xml ,addedOrder=0}
12:38:48,467 DEBUG [MainDeployer] using deployer org.jboss.deployment.SARDeployer@184ec44
12:38:48,623 DEBUG [SARDeployer] Found classpath element:
12:38:48,624 DEBUG [SARDeployer] Setting up classpath from raw codebase: lib
12:38:48,624 DEBUG [SARDeployer] codebase is file:/var/jboss-3.0.6/server/op/lib/
12:38:48,624 DEBUG [SARDeployer] archives are *

I was not exact, though what you've send me might be of interest as well. What I would like to see is what you've sent me before (properties of the java process node) but this time for the process manually started in debug mode.

Well to launch it manually in debug I just added -Xdebug and so its :
/usr/lib/j2se/1.4/bin/java -Xdebug -Xbootclasspath:/usr/lib/j2se/1.4/jre/lib/rt.jar:/usr/lib/j2se/1.4/jre/lib/sunrsasign.jar:/usr/lib/j2se/1.4/jre/lib/jsse.jar:/usr/lib/j2se/1.4/jre/lib/jce.jar:/usr/lib/j2se/1.4/jre/lib/charsets.jar:/usr/lib/j2se/1.4/jre/lib/ext/sunjce_provider.jar:/usr/lib/j2se/1.4/jre/lib/ext/dnsns.jar:/usr/lib/j2se/1.4/jre/lib/ext/localedata.jar:/usr/lib/j2se/1.4/jre/lib/ext/ldapsec.jar -classpath /var/jboss/bin/run.jar:/usr/lib/j2se/1.4/lib/tools.jar org.jboss.Main -cop

But I don't see the interest. I surely missed something.

Hi,

I think there is a little misunderstanding. Hans, you think that poinsarx starts jboss from eclipse, but I think he starts it totally by hand on a command line.

I tried to start JBoss with a run configuration in debug mode from Eclipse M5. With the following properties line:

/opt/j2sdk1.4.1_01/bin/java -DJBOSS_HOME=<absolute path to my JBoss area>/jboss-src/jboss-3.2/build/output/jboss-3.2.0RC3 -Dprogram.name=run.sh -Xbootclasspath:/opt/j2sdk1.4.1_01/jre/lib/rt.jar:/opt/j2sdk1.4.1_01/jre/lib/sunrsasign.jar:/opt/j2sdk1.4.1_01/jre/lib/jsse.jar:/opt/j2sdk1.4.1_01/jre/lib/jce.jar:/opt/j2sdk1.4.1_01/jre/lib/charsets.jar:/opt/j2sdk1.4.1_01/jre/lib/ext/sunjce_provider.jar:/opt/j2sdk1.4.1_01/jre/lib/ext/dnsns.jar:/opt/j2sdk1.4.1_01/jre/lib/ext/localedata.jar:/opt/j2sdk1.4.1_01/jre/lib/ext/ldapsec.jar -classpath <path to my JBoss area>/jboss-src/jboss-3.2/build/output/jboss-3.2.0RC3/bin/run.jar:/opt/j2sdk1.4.1_01/lib/tools.jar -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,suspend=y,address=localhost:7301 org.jboss.Main

With a run configuration which generates this startup line, JBoss starts up and runs the 'default' config in debug mode and i requested the jmx-console successfully.

I hope this helps.

Bernd

redhat 8.0
eclipse-m5-gtk
jboss-3.2.0rc2_tomcat-4.1.18

when i tried to start jboss, i get "java.lang.NullPointerException null" in a Error message box, "Exception in thread "main" java.lang.NoClassDefFoundError: " in the console, and the following stack trace at the bottom of the log (Help->About Eclipse Platform->Configuration Details):

!ENTRY org.jboss.ide.eclipse.launcher 4 0 Feb 19, 2003 01:53:13.406
!MESSAGE Internal Error
!STACK 0
java.lang.NullPointerException
at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.(JDIDebugTarget.java:231)
at org.eclipse.jdt.debug.core.JDIDebugModel$1.run(JDIDebugModel.java:134)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1588)
at org.eclipse.jdt.debug.core.JDIDebugModel.newDebugTarget(JDIDebugModel.java:138)
at org.eclipse.jdt.debug.core.JDIDebugModel.newDebugTarget(JDIDebugModel.java:98)
at org.eclipse.jdt.internal.launching.StandardVMDebugger.run(StandardVMDebugger.java:251)
at org.jboss.ide.eclipse.launcher.configuration.ServerLaunchConfigurationDelegate.launchInternal(ServerLaunchConfigurationDelegate.java:229)
at org.jboss.ide.eclipse.launcher.configuration.ServerLaunchConfigurationDelegate.launch(ServerLaunchConfigurationDelegate.java:100)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:151)
at org.jboss.ide.eclipse.launcher.ServerLaunchManager.start(ServerLaunchManager.java:197)
at org.jboss.ide.eclipse.launcher.ui.ServerNavigator.doStart(ServerNavigator.java:286)
at org.jboss.ide.eclipse.launcher.ui.ServerNavigator$2.run(ServerNavigator.java:192)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:804)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:450)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:398)
at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:392)
at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:897)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1502)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1319)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1289)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1272)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:845)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
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.eclipse.core.launcher.Main.basicRun(Main.java:247)
at org.eclipse.core.launcher.Main.run(Main.java:703)
at org.eclipse.core.launcher.Main.main(Main.java:539)

When I mean by manually, it was inside eclipse.
I configured a run task with the jboss run.jar and the org.jboss.Main class and specifying the configuration with -c <config name>

I think I found the bug. Could someone check it out with linux. I'm sorry that I have no running linux system at the moment. This will change.

I've attached the new version of the launcherplugin. Just unzip it in your plug-in directory.

Thanks for your help

Hans

Sorry, Hans, just the same error messages and popups as described above.
Tested with M5, jbosside 1.0.1 + launcher 1.0.2, jboss 3.0.6 and jboss 3.2RC2 on linux (debian sid), sun jdk 141_01

Hi Hans,

its realy strange. It doesn't work, I get the same 'can not connect' message. But I tried to play around with the launch config. When I try to start JBoss with JBoss-IDE and default classpaths, I get the following startup line:

/opt/j2sdk1.4.1_01/bin/java -Djboss.home=<path to jboss>/jboss-3.2/build/output/jboss-3.2.0RC3 -classpath <path to jboss>/jboss-3.2/build/output/jboss-3.2.0RC3/bin/run.jar:/opt/j2sdk1.4.1_01/lib/tools.jar -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,suspend=y,address=localhost:12892 org.jboss.Main

When I only uncheck the 'use default classpath' checkbox in the 'Classpath' tabpane, I get the following startup line:

/opt/j2sdk1.4.1_01/bin/java -Djboss.home=<path to jboss>/jboss-3.2/build/output/jboss-3.2.0RC3 -Xbootclasspath:/opt/j2sdk1.4.1_01/jre/lib/rt.jar:/opt/j2sdk1.4.1_01/jre/lib/sunrsasign.jar:/opt/j2sdk1.4.1_01/jre/lib/jsse.jar:/opt/j2sdk1.4.1_01/jre/lib/jce.jar:/opt/j2sdk1.4.1_01/jre/lib/charsets.jar:/opt/j2sdk1.4.1_01/jre/lib/ext/sunjce_provider.jar:/opt/j2sdk1.4.1_01/jre/lib/ext/dnsns.jar:/opt/j2sdk1.4.1_01/jre/lib/ext/localedata.jar:/opt/j2sdk1.4.1_01/jre/lib/ext/ldapsec.jar -classpath <path to jboss>/jboss-3.2/build/output/jboss-3.2.0RC3/bin/run.jar:/opt/j2sdk1.4.1_01/lib/tools.jar -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,suspend=y,address=localhost:11787 org.jboss.Main

But if I start JBoss with a normal debug launch config with this startup line:

/opt/j2sdk1.4.1_01/bin/java -Djboss.home=<path to jboss>/jboss-3.2/build/output/jboss-3.2.0RC3 -Xbootclasspath:/opt/j2sdk1.4.1_01/jre/lib/rt.jar:/opt/j2sdk1.4.1_01/jre/lib/sunrsasign.jar:/opt/j2sdk1.4.1_01/jre/lib/jsse.jar:/opt/j2sdk1.4.1_01/jre/lib/jce.jar:/opt/j2sdk1.4.1_01/jre/lib/charsets.jar:/opt/j2sdk1.4.1_01/jre/lib/ext/sunjce_provider.jar:/opt/j2sdk1.4.1_01/jre/lib/ext/dnsns.jar:/opt/j2sdk1.4.1_01/jre/lib/ext/localedata.jar:/opt/j2sdk1.4.1_01/jre/lib/ext/ldapsec.jar -classpath <path to jboss>/jboss-3.2/build/output/jboss-3.2.0RC3/bin/run.jar:/opt/j2sdk1.4.1_01/lib/tools.jar -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,suspend=y,address=localhost:7058 org.jboss.Main

JBoss works well and I can request the jmx-console. It seems that the only difference is the number of the debug port. And when I startup JBoss on the command line in debug mode that it listens on port 11787 for a connecting debugger and use a remote Jboss config in eclipse it works. So the port is useable. It seems that the eclipse debugger and the JBoss-IDE launch config don't use the same port.

Thanks

Bernd

May be I'm wrong, but I think I got it. In my last Mail I said that I started JBoss on the commandline and connected with the eclipse debugger and it worked. I looked in the Debugger API of the JDK. When I don't give an address variable on the command line, the VM selectes a port on his own and prints it on the console. After doing this, I configured the remote jboss launch config with this port number and Jboss started up fine.

I think that after the JBoss-IDE starts up JBoss, the starting VM gives back the port number it waits for a connecting debugger. But this port isn't handed to the eclipse debugger. The debugger tries to connect to the wrong port and fails. This stops the debugger and the JBoss VM and the debugger claims that he can't connect to VM.

Is this possible?

Bernd