[jboss-jira] [JBoss JIRA] Commented: (JBAS-4441) Jboss hangs at startup with 100% CPU utilization
Adrian Brock (JIRA)
jira-events at lists.jboss.org
Fri May 25 08:52:08 EDT 2007
[ http://jira.jboss.com/jira/browse/JBAS-4441?page=comments#action_12363187 ]
Adrian Brock commented on JBAS-4441:
------------------------------------
This issue is caused by JBAS-4066.
The classloader in 4.2.x now catches java.lang.LinkageError and assumes it is a spurious ClassCircularityError
caused by the JDK bug.
The problem is that with this broken configuration, the LinkageError is real.
There should be a maximum number of retries and then it should give up, e.g. 10 attempts?
There is a numCCE in the ClassLoadingTask but this is not currently maintained or used.
The suggested patch in LoadMgr3 would be something like:
catch(Throwable e)
{
boolean retry = e instanceof ClassCircularityError
|| e.getClass().equals(LinkageError.class);
- if( retry)
+ if( retry && loadTask.numCCE < 10)
{
+ ++loadTask.numCEE;
/* Reschedule this task after all existing tasks to allow the
current load tasks which are conflicting to complete.
*/
etc.
> Jboss hangs at startup with 100% CPU utilization
> ------------------------------------------------
>
> Key: JBAS-4441
> URL: http://jira.jboss.com/jira/browse/JBAS-4441
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ClassLoading
> Affects Versions: JBossAS-4.2.0.GA
> Environment: all
> Reporter: Mikhail Grushinskiy
> Assigned To: Scott M Stark
>
> Reproducable this way
> When seam application application.xml includes
> <module>
> <java>jboss-el-api.jar</java>
> </module>
> See these threads for details:
> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=108938&start=10&postdays=postDays&postorder=postOrder&highlight=highlight
> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=109212&start=0&postdays=postDays&postorder=postOrder&highlight=highlight
> At least 4 people independently confirmed it (on windows and linux). It seems looping is hapenning in classloading code which migth indicate
> more serious issue than just with seam applications.
--
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
More information about the jboss-jira
mailing list