Eclipse + JBoss Debug Mode issue

[nameghino]

Hello all,
I'm having an issue regarding a debug deployment using Eclipse + JBoss 4.2.2.
Whenever I deploy my application in debug mode, it takes a big load of time to deploy it (around 20-30 minutes). However, sometimes it deploys in 2 minutes (in debug mode) and it just takes 1.5 minutes in run mode.
This behavior is mostly random, but after the first occurrence of the long-time debug deployment, it's mostly sure that it will happen again.

Note that I've already posted this in the eclipse.newcomers group and Wayne Beaton suggested that I should post this issue here and in a JBoss forum.

I have a "virgin environment" (all I did to it was configure it to work and then never touched it again) so that I can spawn the same installation in several computers and have the same contents everywhere in another PC with Eclipse 3.3.2 (Build M20080221-1800) and JBoss 4.2.2GA which I compared against my installation of the bundle.

It turned out that two files were changed between those two installations:

* org.eclipse.jdt.core_3.3.1.v_780_R33x.jar
* org.eclipse.jdt.core_3.3.3.v_793_R33x.jar

I tried overwriting those two files with the virgin copies, but without result. I then deleted my whole eclipse folder and downloaded the virgin environment. Still no good.

Some time later, I proceeded to undeploy the application from the server, delete the temp files from it, do a full clean build of the app. and then redeployed. It worked for a couple of debug deployments but now the problem is back. I repeated those steps, hoping it would work, but unfortunately it didn't.

Finally, I also noted that, if given the 20-30 minutes' time it requires to deploy the application in debug mode, the application is a lot slower than the usual debug deployments that take 2 minutes.

Any help appreciated, and thanks!
Nicolas Ameghino

[jaikiran]

Try taking thread dumps at regular intervals when JBoss is starting to see where exactly its taking time. See this for details about how to take thread dumps http://wiki.jboss.org/wiki/StackTrace

[nameghino]

Thanks for the tip.
I'm taking those thread dumps right now, both from Eclipse and from JBoss and will analyze them later. However, it's taking extra-time for everything, it's not that it gets stuck at some specific point every time.

[jaikiran]

"nameghino" wrote:
However, it's taking extra-time for everything, it's not that it gets stuck at some specific point every time.

I do expect the server startup to slow down when debugging is enabled. How much time does it take to start the server in debug mode without your application being deployed? What exactly does your application contain?

[jaikiran]

Also post the params that you are passing through the startup script to enabled "debug" mode for JBoss.

[nameghino]

JBoss starts in 1m15s average in run mode, and 2m30s average in debug mode (when this issue is not present), deploying the application. Without deploying the application, it takes about 25 seconds to start in run mode and about 40 secs. in debug mode.

Program arguments for JBoss are:
--configuration=default

VM arguments are:
-Xms256m -Xmx512m -XX:MaxPermSize=256m

Taken from the server properties in the Eclipse JBoss Servers view, although it wasn't specified that those parameters were used for debug mode or if there were extra debug mode parameters.

What do you mean by "what exactly does your application contain?"? I'm using the Seam framework by the way.

[nameghino]

Bump

[jaikiran]

"nameghino" wrote:

What do you mean by "what exactly does your application contain?"? I'm using the Seam framework by the way.

The application deployment time heavily depends on the components packaged in the application. For example if the application contains EJB3 beans, then the deployment phase will consist of parsing the annotations and other metadata.

The parameters that you posted does not contain anything specific to the debugger. Usually, the run.bat would contain

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

[jaikiran]

I assume that you are not trying to debug anything *during* your application deployment. In that case, you can attach the Eclipse debugger after your application has been deployed.

[nameghino]

Yes, the application contains several EJB3 beans, and I'm aware of the usual deployment time.

I also checked run.bat for a line like the one you posted, but there's only one, and it's commented.

rem JPDA options. Uncomment and modify as appropriate to enable remote debugging.
rem set JAVA_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y %JAVA_OPTS%

And no, what I'm trying to debug is the application running on the server, after it's been deployed.

[nameghino]

Bump

[jaikiran]

"nameghino" wrote:

I also checked run.bat for a line like the one you posted, but there's only one, and it's commented.

rem JPDA options. Uncomment and modify as appropriate to enable remote debugging.
rem set JAVA_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y %JAVA_OPTS%

In that case, i am not sure how the server is started in debug mode. Probably the IDE picks up some other configuration file for starting JBoss?

"nameghino" wrote:

And no, what I'm trying to debug is the application running on the server, after it's been deployed.

So, as mentioned in one of my earlier replies, you can attach the debugger to the server "after" the application has been deployed. This way you don't run into this issue (which you mention happens "during" application deployment).

[praveenas]

Hi,

I am trying to cluster my Jboss deployed a war file written using ECHO2 and Hibernate. There are some issues to be solved in the source of EC?HO2. For that I need to run the war in Jboss in Debug mode. My m/c is running on LINUX. Please let me know where I can find proper documentation for configuring JbossIDE plugin in my current eclipse which already has Tomcat. I did nt find complete documentation in http://docs.jboss.com/jbosside/install/build/en/pdf/JBossIDE-Install.pdf


Thank you in advance.

Praveena.

[jaikiran]

"praveenas" wrote:
Hi,

I am trying to cluster my Jboss deployed a war file written using ECHO2 and Hibernate. There are some issues to be solved in the source of EC?HO2. For that I need to run the war in Jboss in Debug mode. My m/c is running on LINUX. Please let me know where I can find proper documentation for configuring JbossIDE plugin in my current eclipse which already has Tomcat. I did nt find complete documentation in http://docs.jboss.com/jbosside/install/build/en/pdf/JBossIDE-Install.pdf


Thank you in advance.

Praveena.

Praveena,

Your question is not related to what is being discussed in this thread. Please open a separate topic in this forum.

[praveenas]

Hi,

I am trying to run Jboss in Debug mode on eclipse to find the bugs.
I am looking for good documentation steps to install Jboss IDE. (I am on Linux m/c), on my eclipse which already has tomcat configured in it.

Hope I have posted at the right location for my requirement. Please let me know the available docs for updating jbosside plugin on eclipse sdk.
http://docs.jboss.com/jbosside/install/build/en/pdf/JBossIDE-Install.pdf . This document did not give me complete details of configuration.


Thanks in advance for your help in providing required documentaion.