- This topic has 19 replies, 4 voices, and was last updated 17 years, 3 months ago by
.
-
Posts
-
Hello,
This is a continuation of a previous post that got closed because I thought I had the problem solved.Basically, I have a Seam application that I been developing just fine under Eclipse 3.3 and MyEclipse 6.0GA. I added some more functionality to the app, and suddenly JBoss took 40 minutes to start up! I modifed the JVM memory settings and thought I had fixed the problem. Turns out, I had switched it to run in Normal mode rather than Debug mode. So, the new problem is that everything starts up and runs fine in Normal mode, but when I switch to Debug mode I’m back to waiting 40+ minutes! My environment is Mac OSX, Java 5.0, Seam 2.0, JBoss 4.2.1GA. This problem also occurs with JBoss 5.0Beta2.
Oh wow that’s a long startup.
How debug mode works is it starts up the application server and connects to the MyEclipse debugger.
When the debugger is running *every* source file you have in *every* open project is a *potential* target for a breakpoint to get hit. So either have a lot of breakpoints set or unchecked or having a ton of source code in all the open projects in your workspace, can bog the runtime of the app server in general down.
You will want to close all the projects you aren’t using, and make sure if you have the Package View to display “Workspaces” that there aren’t other projects open in other workspaces that could be hit.
This should help a lot.
Unfortunately not. Here’s what triggered this problem: I added one additional source file for Seam, and one additional XHTML file. If I remove the @Name annotation from the Seam file, everything starts up in debug mode normally. If I add the @Name annotation back, I get the long start time. In normal mode, there’s no change.
That… is officially the strangest thing I’ve ever heard.
Out of curiosity, put the annotation in, deploy the project, make sure it takes forever to start up, then try and run JBoss from the command line (make sure it’s in debug mode as well)
The problem may lie with JBoss, not MyEclipse.
Okay, while I’m waiting for it to start up under Eclipse 3.3 and MyEclipse 6.0GA, I deployed the project and started JBoss 4.2.1GA up from the command line in debug mode. Everything started and ran just fine in 45 seconds. When I do the same thing under Eclipse, it looks like it’s starting to deploy correctly, but it begins to slow down when it reaches the installation of the MBeans. Here’s a sample output:
14:50:05,478 INFO [EJBContainer] STARTED EJB: com.mdesignz.topaz.fdb.loader.FdbLoaderBean ejbName: FdbLoaderBean
14:50:08,153 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer
14:50:08,174 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=topaz.ear,jar=topazEJB.jar,name=MibLookupBean,service=EJB3 with dependencies:
14:50:08,189 INFO [JmxKernelAbstraction] persistence.units:ear=topaz.ear,jar=topazEJB.jar,unitName=topazEmIf you note the times, when run from the command line, deploying all the MBeans requires less than a second.
Things come to a screaching halt when it deploys the WAR file. This is the last message in my Eclipse console:14:50:13,454 INFO [TomcatDeployer] deploy, ctxPath=/topazWeb, warUrl=…/deploy/topaz.ear/topazWeb.war/
which was displayed about 7 minutes ago. It will be a while longer before it comes up. When it does, I’ll do the test as you suggested.
Since I can launch the project in debug mode from the command line, is there any way I can do that and still trap the break points in Eclipse? At least that would be a work around. Thanks!Okay, it finally finished starting up, so I started an instance from the command line. It threw exceptions about the address already being in use, but otherwise finished in about 30 seconds. From my point of view, it looks like JBoss is behaving correctly.
There is sometihng fishy going on here, but as an immediate workaround to the problem please use the remote debugging capabilities in MyEclipse (tutorial here: http://www.myeclipseide.com/documentation/quickstarts/remotedebugging/)
that will atleast get you workaround around that issue for now.
Hello Riyad,
The above is a bad link. I’ll try to find it manually. I really appreciate your help on this.
-robert.Hello Riyad,
Remote debugging works just fine. A couple extra steps, but I can easily live with that. If you need additional information to solve the other problem, please let me know.
-robert.Robert thank you, I’m going to continue testing scenarios on my end and see if I can reproduce this reliably.
Zip… I can’t get this thing to startup crazy-slow like you are seeing… it’s almost too slow… like “how is this even possible” slow…
I’ve just been deploying a ton of projects to it and leaving them all open then setting random breakpoints and firing it up in debug mode.
Hmm… could be I suppose, I don’t have a Mac to test on unfortunately.
You *could* try changing the default platform VM and restarting MyEclipse (I guess you have to install that Java 6 preview release from Apple?)
