[mattcuthbert]

Hi there,

Our team is experiencing very slow startup when running JBoss 4.0.4GA from MyEclipse in debug mode. ‘Run’ mode is fine, and we’ve worked round the problem by switching to run mode, and setting debug on in the optional Java VM arguments (and then remote debugging using a socket).

Any idea why this might be happening? Seems to slow down when trying to read the Log4J settings and the starting the EJB3 invoker locator.

<snip>
10:32:28,682 INFO [ServiceBindingManager] Using StoreURL: file:/C:/java/servers/jbossAS/jboss-4.0.4.GA/server/rlg-bindings.xml
10:32:28,963 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
10:34:14,265 INFO [SocketServerInvoker] Invoker started for locator: InvokerLocator [socket://10.250.10.89:3873/]
10:42:23,161 INFO [AspectDeployer] Deployed AOP: file:/C:/java/servers/jbossAS/jboss-4.0.4.GA/server/default/deploy/ejb3-interceptors-aop.xml
10:43:07,209 INFO [WebService] Using RMI server codebase: http://S1B00934:8083/
10:43:12,580 INFO [MailService] Mail Service bound to java:/Mail

…..

10:32:13,474 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
10:32:24,669 INFO [Server] Core system initialized
10:32:28,682 INFO [ServiceBindingManager] Initializing store
10:32:28,682 INFO [ServiceBindingManager] Using StoreURL: file:/C:/java/servers/jbossAS/jboss-4.0.4.GA/server/rlg-bindings.xml
10:32:28,963 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
10:34:14,265 INFO [SocketServerInvoker] Invoker started for locator: InvokerLocator [socket://10.250.10.89:3873/]
10:42:23,161 INFO [AspectDeployer] Deployed AOP: file:/C:/java/servers/jbossAS/jboss-4.0.4.GA/server/default/deploy/ejb3-interceptors-aop.xml
10:43:07,209 INFO [WebService] Using RMI server codebase: http://S1B00934:8083/
10:43:12,580 INFO [MailService] Mail Service bound to java:/Mail
10:43:13,689 INFO [NamingService] JNDI bootstrap JNP=/0.0.0.0:1099, RMI=/0.0.0.0:1098, backlog=50, no client SocketFactory, Server SocketFactory=class org.jboss.net.sockets.DefaultSocketFactory
10:43:13,814 INFO [SubscriptionManager] Bound event dispatcher to java:/EventDispatcher
10:43:15,875 INFO [Embedded] Catalina naming disabled

</snip>

[mattcuthbert]

Sorry should have added thats using Eclipse 3.1.2 and MyEclipse 4.1.1 on Windows XP Prof.

[Scott Anderson]

Matt,

The thing that comes to mind is that when starting JBoss internally it’s not being configured with the same RAM configuration you’re getting with the external config and this is likely the cause of the slow startup. On the JDK preference sub-page for the JBoss connector you can provide JVM arguments to be used during server startup. Could you please try setting:

-Xms128m 
-Xmx512m

I believe that should help quite a bit.

[mattcuthbert]

Hi Scott,

Thanks for the feedback – I already had some similar settings (xms=256, xmx=512) and didn’t seem to help. I’ve also tried playing with various other VM tuning options.

I think it must be something to do with how MyEclipse sets up it’s debugging connection. If I disable debug mode and instead set the following JVM settings it all starts up with no delays. I can then remote debug in Eclipse with no problems.

-Xdebug -Xrunjdwp:transport=dt_socket,address=9999,server=y,suspend=n

I assume the MyEclipse ‘debug mode’ is doing something similar (only starting the debugger with the server=n flag and differnt port)?

Thanks
Matt

[Scott Anderson]

Matt,

I assume the MyEclipse ‘debug mode’ is doing something similar (only starting the debugger with the server=n flag and differnt port)?

Yes, it does exactly the same thing but with a dynamic port. At the point the connection is made, it’s all handled by the Eclipse debugger so there’s nothing we’re injecting into the process. Part of the issue might be that Log4J behaves differently (somehow) between the two startup modes and when it detects the debug mode takes much longer. I did a quick search and noticed a similar problem was reported with JBoss 4 startups here.

[Author]

Posts