<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<body link="#355491" alink="#4262a1" vlink="#355491" style="background: #e2e2e2; margin: 0; padding: 20px;">
<div>
<table cellpadding="0" bgcolor="#FFFFFF" border="0" cellspacing="0" style="border: 1px solid #dadada; margin-bottom: 30px; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td>
<table border="0" cellpadding="0" cellspacing="0" bgcolor="#FFFFFF" style="border: solid 2px #ccc; background: #dadada; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td bgcolor="#000000" valign="middle" height="58px" style="border-bottom: 1px solid #ccc; padding: 20px; -moz-border-radius-topleft: 3px; -moz-border-radius-topright: 3px; -webkit-border-top-right-radius: 5px; -webkit-border-top-left-radius: 5px;">
<h1 style="color: #333333; font: bold 22px Arial, Helvetica, sans-serif; margin: 0; display: block !important;">
<!-- To have a header image/logo replace the name below with your img tag -->
<!-- Email clients will render the images when the message is read so any image -->
<!-- must be made available on a public server, so that all recipients can load the image. -->
<a href="http://community.jboss.org/index.jspa" style="text-decoration: none; color: #E1E1E1">Community</a></h1>
</td>
</tr>
<tr>
<td bgcolor="#FFFFFF" style="font: normal 12px Arial, Helvetica, sans-serif; color:#333333; padding: 20px; -moz-border-radius-bottomleft: 4px; -moz-border-radius-bottomright: 4px; -webkit-border-bottom-right-radius: 5px; -webkit-border-bottom-left-radius: 5px;"><h3 style="margin: 10px 0 5px; font-size: 17px; font-weight: normal;">
Nessus scan makes JBoss 5.1.0.GA stop processing web requests
</h3>
<span style="margin-bottom: 10px;">
reply from <a href="http://community.jboss.org/people/snacker">Nathan Ciliberto</a> in <i>Beginner's Corner</i> - <a href="http://community.jboss.org/message/548382#548382">View the full discussion</a>
</span>
<hr style="margin: 20px 0; border: none; background-color: #dadada; height: 1px;">
<div class="jive-rendered-content"><p>We are seeing a similar issue, but it is not caused by a scanning application.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>On the web server side we see occasionally see threads with this stack:</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p style="padding-left: 30px;"><span style="font-size: 8pt; font-family: arial,helvetica,sans-serif; ">75: [Thread[jrpp-1390,5,jrpp]]/id=49440/hc=13398717/shc=*/state=RUNNABLE/name=*<br/>        java.net.SocketInputStream.socketRead0(Native Method)<br/>        java.net.SocketInputStream.read(SocketInputStream.java:129)<br/>        java.io.BufferedInputStream.fill(BufferedInputStream.java:218)<br/>        java.io.BufferedInputStream.read(BufferedInputStream.java:237)<br/>        java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2249)<br/>        java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2429)<br/>        java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2499)<br/>        java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2571)<br/>        java.io.ObjectInputStream.read(ObjectInputStream.java:820)<br/>        org.jboss.remoting.transport.socket.MicroSocketClientInvoker.<span style="font-size: 10pt;"><strong>readVersion</strong></span>(MicroSocketClientInvoker.java:1263)<br/>        org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:838)<br/>        org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:165)<br/>        org.jboss.remoting.Client.invoke(Client.java:1724)<br/>        org.jboss.remoting.Client.invoke(Client.java:629)<br/>        org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)<br/>        org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)<br/>        org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)<br/>        org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)<br/>        org.jboss.ejb3.security.client.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)<br/>        org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)<br/>        org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)<br/>        org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)<br/>        org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)<br/>        $Proxy5.invoke(Unknown Source)<br/>        org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:207)<br/>        org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164)<br/>        $Proxy1643.completeMyOrder(Unknown Source)</span></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p> On the jboss server for each thread above we usually see at least 2 jboss threads with the following stack:</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p style="padding-left: 30px;"><span style="font-size: 8pt;">816: [WorkerThread#10[10.1.4.245:46454]]/id=6923/hc=1806701791/shc=*/state=RUNNABLE/name=*<br/>         java.net.SocketInputStream.socketRead0(Native Method)<br/>         java.net.SocketInputStream.read(SocketInputStream.java:129)<br/>         java.io.BufferedInputStream.fill(BufferedInputStream.java:218)<br/>         java.io.BufferedInputStream.read(BufferedInputStream.java:237)<br/>         java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2249)<br/>         java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2429)<br/>         java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2499)<br/>         java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2571)<br/>         java.io.ObjectInputStream.read(ObjectInputStream.java:820)<br/>         org.jboss.remoting.transport.socket.ServerThread.<span style="font-size: 10pt;"><strong>readVersion</strong></span>(ServerThread.java:1038)<br/>         org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:673)<br/>         org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:551)<br/>         org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)</span></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>I am not sure what is going on, but it looks like there is something that occasionally gets messed up with these "readVersion(...)" methods.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>These threads will hang for hours and days.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>The only way we can get these to stop hanging is to send a Thread.interrupt() to the threads on the <span style="text-decoration: underline;">web server side</span>.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Sending the interrupt to the thread on the jboss side only moves the problem to a different thread and doesn't stop the web server threads from</p><p>hanging.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>We are not sure what is causing this, but it appears to be a bug in jboss.</p><p>We are using 5.1.0 GA as well.</p></div>
<div style="background-color: #f4f4f4; padding: 10px; margin-top: 20px;">
<p style="margin: 0;">Reply to this message by <a href="http://community.jboss.org/message/548382#548382">going to Community</a></p>
<p style="margin: 0;">Start a new discussion in Beginner's Corner at <a href="http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2075">Community</a></p>
</div></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>