[jboss-jira] [JBoss JIRA] Commented: (JBAS-8580) JBoss 6 uses 100% CPU after scanning

Thu Nov 4 12:32:01 EDT 2010

    [ https://jira.jboss.org/browse/JBAS-8580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561401#action_12561401 ] 

Rico Neubauer commented on JBAS-8580:
-------------------------------------

This is not really related to any port scanning (at least not for me), see JBoss Forum Reference for my 2 cents. Also an issue with today's (2010-11-04) snapshot of JBoss6.

> JBoss 6 uses 100% CPU after scanning
> ------------------------------------
>
>                 Key: JBAS-8580
>                 URL: https://jira.jboss.org/browse/JBAS-8580
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 6.0.0.M2
>         Environment: Seen in several environments, by myself and others (see the forum thread).  My two environments are:
> JBoss 6.0.0.M2:  Java version: 1.6.0_16,Sun Microsystems Inc.   OS-System: Linux 2.6.9-89.0.26.ELsmp,i386
> JBoss 6.0.0.M2:  Java version: 1.6.0_20,Sun Microsystems Inc.   OS-System: Linux 2.6.18-194.17.1.el5,i386
>            Reporter: Nick Newman
>
> These JBossAS instances are not clustered and are in environments where they are port-scanned by Nessus software looking for security problems.  After the scans each JBossAS instance is left in a state that has a thread actively consuming CPU.  A typical figure is 105% CPU on a 4-CPU box, 99.9% CPU on a single CPU virtual machine.
> The JBossAS instance continues to respond despite this, although the response (and the response of everything else) is very slow on a single CPU box.
> The JBossAS instances have to be restarted to resolve the problem.
> The forum thread contains access logs (to show what the scanner is trying) and thread dumps from myself and others, including thread dumps at consecutive intervals to help indicate the thread activity during this unusual state.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira