[
http://jira.jboss.com/jira/browse/JBAS-1941?page=all ]
Dimitris Andreadis resolved JBAS-1941.
--------------------------------------
Fix Version/s: (was: JBossAS-4.0.5.GA)
Resolution: Cannot Reproduce Bug
I've closing this, if it cannot be reproduced by Alexey.
JBoss-4.0.1Sp1 startup slow (server hangs in SQLUtil.tableExists()
method)
--------------------------------------------------------------------------
Key: JBAS-1941
URL:
http://jira.jboss.com/jira/browse/JBAS-1941
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: CMP service
Affects Versions: JBossAS-4.0.1 SP1
Environment: Effect takes place on the Solaris (SunOS Release 5.8) as well as the
Windows (XP) Platform. The System uses a DB2 Database (UDB Runtime Client V8.1 connects
via DB2Connect to DB2 Server V7.0 running on OS390)
I observed the same Effect on other JBoss releases (JBoss-3.2.5, JBoss-4.0.2)
Reporter: helly15
Assigned To: Alexey Loubyansky
Attachments: JBoss4_Startup 2005-06-21 17-59-35.profile
I am moving from JBoss-3.2.1 to JBoss-4.0.1Sp1. The problem I am facing is that it takes
JBoss-4.0.1 over 10 minutes to start, while JBoss-3.2.1 started up in under 3 minutes.
I did a profiling of the startup process using the Eclipse Profiler. The profiling
revealed that the server spends nearly 10 seconds in the method SQLUtil.tableExists()
every time the method is called during the startup process. This method is called once for
every table that exists in the application (32 tables). This leads to the lengthy startup
time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira