[sle]

Hi,

I have a probleme running JBOSS 3.2.6 in debug mode when Eclipse is running JAVA 1.5 that I don’t have if Eclipse is running java 1.4.

The fact is that JBOSS 3.2.6 can not run in java 1.5, so when Eclipse is running in java 1.5, I set up a jdk1.4 in JBOSS connector.

That setup works fine in run mode, but in debug mode I can not start JBOSS and get the following error : Transport dt_socket failed to initialize, rc = 509.

I tried running Eclipse in java 1.4 and without changing the connector setup, starting jboss in debug mode: no problem !

I certainly can use Eclipse in java 1.4, so this is not a blocking problem. But I have no idea what is missing in the setup (eclipse running 1.5, jboss running 1.4) to make it work. I tried different version of 1.4, no change.

Do you have any idea/suggestion ?

I am using Eclipse 3.1.2 with MyEclipse 4.1 on Windows XP SP2.

thanks,

Seb’-

[Riyad Kalla]

Seb,
I can’t reproduce this locally. I used JDK 1.5.0_06 to run MyEclipse 4.1.1 and then used JDK 1.4.2_09 to run JBoss 3.2.6 in debug mode, it started up fine:

05:55:58,566 INFO [Server] Starting JBoss (MX MicroKernel)…
05:55:58,566 INFO [Server] Release ID: JBoss [WonderLand] 3.2.6 (build: CVSTag=JBoss_3_2_6 date=200410140106)
05:55:58,566 INFO [Server] Home Dir: C:\Java\jboss-3.2.6
05:55:58,566 INFO [Server] Home URL: file:/C:/Java/jboss-3.2.6/
05:55:58,566 INFO [Server] Library URL: file:/C:/Java/jboss-3.2.6/lib/
05:55:58,566 INFO [Server] Patch URL: null
05:55:58,566 INFO [Server] Server Name: default
05:55:58,566 INFO [Server] Server Home Dir: C:\Java\jboss-3.2.6\server\default
05:55:58,566 INFO [Server] Server Home URL: file:/C:/Java/jboss-3.2.6/server/default/
05:55:58,566 INFO [Server] Server Data Dir: C:\Java\jboss-3.2.6\server\default\data
05:55:58,566 INFO [Server] Server Temp Dir: C:\Java\jboss-3.2.6\server\default\tmp
05:55:58,566 INFO [Server] Server Config URL: file:/C:/Java/jboss-3.2.6/server/default/conf/
05:55:58,566 INFO [Server] Server Library URL: file:/C:/Java/jboss-3.2.6/server/default/lib/
05:55:58,566 INFO [Server] Root Deployment Filename: jboss-service.xml
05:55:58,566 INFO [Server] Starting General Purpose Architecture (GPA)…
05:55:58,909 INFO [ServerInfo] Java version: 1.4.2_09,Sun Microsystems Inc.
05:55:58,909 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.2_09-b05,Sun Microsystems Inc.
05:55:58,909 INFO [ServerInfo] OS-System: Windows 2003 5.2,x86
05:55:59,066 INFO [Server] Core system initialized
05:56:00,925 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
05:56:01,034 INFO [WebService] Using RMI server codebase: http://rsk:8083/
05:56:01,238 INFO [NamingService] Started jndi bootstrap jnpPort=1099, rmiPort=1098, backlog=50, bindAddress=/0.0.0.0, Client SocketFactory=null, Server SocketFactory=org.jboss.net.sockets.DefaultSocketFactory@ad093076
05:56:03,253 INFO [RARMetaData] Loading JBoss Resource Adapter for JDBC 2 XA drivers
05:56:03,253 INFO [RARMetaData] Required license terms present. See deployment descriptor.
05:56:05,488 INFO [MailService] Mail Service bound to java:/Mail
05:56:05,941 INFO [Embedded] Catalina naming disabled
05:56:06,534 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
05:56:06,722 INFO [Catalina] Initialization processed in 719 ms
05:56:06,722 INFO [StandardService] Starting service jboss.web
05:56:06,738 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.0.28
05:56:06,769 INFO [StandardHost] XML validation disabled
05:56:06,784 INFO [Catalina] Server startup in 62 ms
05:56:06,878 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=file:/C:/Java/jboss-3.2.6/server/default/deploy/http-invoker.sar/invoker.war/
05:56:07,784 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=file:/C:/Java/jboss-3.2.6/server/default/deploy/jbossweb-tomcat50.sar/ROOT.war/
05:56:07,941 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=file:/C:/Java/jboss-3.2.6/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
05:56:08,081 INFO [DefaultDS] Bound connection factory for resource adapter for ConnectionManager ‘jboss.jca:service=LocalTxCM,name=DefaultDS to JNDI name ‘java:/DefaultDS’
05:56:08,331 INFO [A] Bound to JNDI name: queue/A
05:56:08,331 INFO [B] Bound to JNDI name: queue/B
05:56:08,331 INFO [C] Bound to JNDI name: queue/C
05:56:08,331 INFO [D] Bound to JNDI name: queue/D
05:56:08,331 INFO [ex] Bound to JNDI name: queue/ex
05:56:08,363 INFO [testTopic] Bound to JNDI name: topic/testTopic
05:56:08,363 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
05:56:08,363 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
05:56:08,378 INFO [testQueue] Bound to JNDI name: queue/testQueue
05:56:08,456 INFO [UILServerILService] JBossMQ UIL service available at : /0.0.0.0:8093
05:56:08,503 INFO [DLQ] Bound to JNDI name: queue/DLQ
05:56:08,519 INFO [JmsXA] Bound connection factory for resource adapter for ConnectionManager ‘jboss.jca:service=TxCM,name=JmsXA to JNDI name ‘java:/JmsXA’
05:56:08,566 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=file:/C:/Java/jboss-3.2.6/server/default/deploy/jmx-console.war/
05:56:08,738 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=file:/C:/Java/jboss-3.2.6/server/default/deploy/management/web-console.war/
05:56:09,456 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
05:56:09,581 INFO [ChannelSocket] JK2: ajp13 listening on /0.0.0.0:8009
05:56:09,597 INFO [JkMain] Jk running ID=0 time=0/31 config=null
05:56:09,613 INFO [Server] JBoss (MX MicroKernel) [3.2.6 (build: CVSTag=JBoss_3_2_6 date=200410140106)] Started in 10s:843ms

Any ideas what I missed?

[sle]

Hi,

First, I made a mistake in my first post. I’m running JBOSS 3.2.3 , not 3.3.6, but I don’t think this makes any difference.

Maybe there is something connected to the path required to reproduce the bug.

The bug occurs on my desktop when there is no mention of JRE 1.4 at all, just JRE 1.5. It is the case on your end ?

I had to replace the path to JRE 1.5 by the path to JRE 1.4 to make the thing work.

By the way, I tried to start Eclipse with a specific JRE that is different from the one in the path. The only command line option I found is -vm, but it doesn’t do what I need. If you have any knowledge about that, would be great. Otherwise I can keep JRE 1.4 in the path for the moment.

Seb’

[Riyad Kalla]

Maybe there is something connected to the path required to reproduce the bug.

I’m not sure, what does your path look like?

The bug occurs on my desktop when there is no mention of JRE 1.4 at all, just JRE 1.5. It is the case on your end ?

I think, I only have the 1.5 JRE installed for personal use, then I have 1.3, 1.4 and 1.6 all installed as JDK-only for testing (no JRE).

By the way, I tried to start Eclipse with a specific JRE that is different from the one in the path. The only command line option I found is -vm, but it doesn’t do what I need. If you have any knowledge about that, would be great. Otherwise I can keep JRE 1.4 in the path for the moment.

Yes you are right, -vm is the way to do it, you have to point at the actual executable, like:
eclipse.exe -vm c:\jdk1.5.0_06\bin\javaw.exe

[Author]

Posts