Jboss AS 6 boot up time increases dramatically after turning debug port on!

[stewar]

HI,

I have an application deployed in JBoss AS 6.1.0, the normal bootup time is around 7 minutes.

but when i turn the debug port on inside $JBOSS_HOME/bin/run.conf file.

the bootup time shoots to 25 minutes!!! Can anybody let me know what is the issue here?

[jaikiran]

See if this helps https://community.jboss.org/message/195040#195040

[stewar]

Hi jaikiran,

i went through the link you have provided but it is related to starting jboss from inside an IDE,

i am not doing any such thing.

i have installed JBoss AS 6.1.0 final on a unix machine, deployed my ears on it and i turn on the debug port,

so there is no chance of an debug point overhead here.?

[jaikiran]

Sumeeth Tewar wrote:

i went through the link you have provided but it is related to starting jboss from inside an IDE,

It's actually about having set breakpoints from inside an IDE and not about starting the server from IDE.

Sumeeth Tewar wrote:

i am not doing any such thing.

So you aren't using any IDE to add debug breakpoints?

Sumeeth Tewar wrote:

i have installed JBoss AS 6.1.0 final on a unix machine, deployed my ears on it and i turn on the debug port,

so there is no chance of an debug point overhead here.?

Just so that I understand better, why do you want to switch on the debug port?

[stewar]

I am doing a bootup time analysis, and i came across this issue.

i just picked my application ear's and added to the server and it got successfully deployed in 7 minutes.

then i stop the server turn the debug on. and start the server. the boot up time shot to 25 minutes?

and i successfully reproduced this on different machines.

I have not even opened the IDE or tried to establish a connection to the remote debug port?

Is this normal behaviour or there is a solution?

[jaikiran]

A difference of around 18 minutes to the startup time is not common although I have seen some users report it (like in that thread).

[stewar]

So, is there a solution or reason why this happens?

Or the server does something special in debug mode that we could configure it not to do?

[jaikiran]

JBoss AS does nothing different here. It's just the Java runtime http://stackoverflow.com/questions/2195720/why-does-java-code-slow-down-in-debugger?answertab=votes#tab-top

[kcoupland]

Just to clarify - the only change that is being made to reproduce this problem is to modify the run.conf file to uncomment the line which enables the debugger port (i.e. JAVA_OPTS="$JAVA_OPTS -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n"). No debugger is actually being attached.

[iampratik]

DO we have any update on it??
I am also facing the same issue.....

Any hint would be commendable.

Thanks in advance

[stewar]

Hi Pratik,

I have not received or found any concrete solution,

but for now i have added jboss-scanning.xml to all the ears/meta-inf and wars/web-inf

and mentioned which packages to scan for annotation classes and which packages/jars to ignore.

as far as i am concerned i have seen a considerable decrease in boot up time.

This way you can also better the normal bootup time. but then be very careful in configuring which packages to scan and which to ignore.

If you do not have any classes which are annotated in jars of an ear, or a war you can add empty jboss-scanning.xml to these artifacts. empty meaning :

<scanning xmlns="urn:jboss:scanning:1.0"> 
 </scanning>

For an example of the jboss-scanning.xml, please refer :

http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Web_Platform/5/html/JBoss_Microcontainer_User_Guide/sect-JBoss_Microcontainer_User_Guide-The_Virtual_Deployment_Framework-Scanning_Classes_for_Annotations.html

Good Luck!

[iampratik]

Thanks Sumeeth.

I found a solution, optimising JVM usage significantly improved my boot up time.

Thanks.