For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 4 replies, 2 voices, and was last updated 18 years, 10 months ago by
.
-
Posts
-
When I startup JBOSS in Eclipse I get a significant delay versus starting up from the command line. Here is the example that shows a 1 minute 47 second delay between the log4j & WebService
12:01:14,129 INFO [Server] Core system initialized
12:01:17,208 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
12:02:54,770 INFO [WebService] Using RMI server codebase: http://YOURGENIE:8083/
Command line delay is about 10 seconds…
Any ideas?
Are you behind a proxy or don’t have net access? I wonder if an XML parser is trying to validate an XML file by pulling down the DTD or Schema and timing out or something.
I recently upgraded to MyEclipse 5.0 and the delay between log4j & WebService reduced significantly…
However JBOSS startup is still very slow in general – are there any guidelines for speeding it up? –
An complete startup took 20 seconds with Tomcat – with JBOSS it takes about 90 seconds…
jbruen,
JBoss is a *much* bigger beast than Tomcat which is just a servlet container (JBoss is a full JEE container). So startup between the two is going to be vastly different no matter what.A tip that helps all servers on startup though is to remove breakpoints you aren’t using and close projects you aren’t debugging because when you fire up a app server, all during startup all break points need to be considered in all projects during run time, that evaluation in 90% of the cases is very fast and not noticable. But with some huge projects opens (enterprise apps or the like) it’s possible to really bog down the run/debug time of the app server.
