Re: [jboss-user] [Beginner's Corner] - Nessus scan makes JBoss 5.1.0.GA stop processing web requests
by Nathan Ciliberto
Nathan Ciliberto [http://community.jboss.org/people/snacker] replied to the discussion
"Nessus scan makes JBoss 5.1.0.GA stop processing web requests"
To view the discussion, visit: http://community.jboss.org/message/548382#548382
--------------------------------------------------------------
We are seeing a similar issue, but it is not caused by a scanning application.
On the web server side we see occasionally see threads with this stack:
75: [Thread[jrpp-1390,5,jrpp]]/id=49440/hc=13398717/shc=*/state=RUNNABLE/name=*
java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketInputStream.read(SocketInputStream.java:129)
java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
java.io.BufferedInputStream.read(BufferedInputStream.java:237)
java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2249)
java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2429)
java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2499)
java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2571)
java.io.ObjectInputStream.read(ObjectInputStream.java:820)
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.*readVersion*(MicroSocketClientInvoker.java:1263)
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:838)
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:165)
org.jboss.remoting.Client.invoke(Client.java:1724)
org.jboss.remoting.Client.invoke(Client.java:629)
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
org.jboss.ejb3.security.client.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
$Proxy5.invoke(Unknown Source)
org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:207)
org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164)
$Proxy1643.completeMyOrder(Unknown Source)
On the jboss server for each thread above we usually see at least 2 jboss threads with the following stack:
816: [WorkerThread#10[10.1.4.245:46454]]/id=6923/hc=1806701791/shc=*/state=RUNNABLE/name=*
java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketInputStream.read(SocketInputStream.java:129)
java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
java.io.BufferedInputStream.read(BufferedInputStream.java:237)
java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2249)
java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2429)
java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2499)
java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2571)
java.io.ObjectInputStream.read(ObjectInputStream.java:820)
org.jboss.remoting.transport.socket.ServerThread.*readVersion*(ServerThread.java:1038)
org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:673)
org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:551)
org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
I am not sure what is going on, but it looks like there is something that occasionally gets messed up with these "readVersion(...)" methods.
These threads will hang for hours and days.
The only way we can get these to stop hanging is to send a Thread.interrupt() to the threads on the web server side.
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
hanging.
We are not sure what is causing this, but it appears to be a bug in jboss.
We are using 5.1.0 GA as well.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/548382#548382]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
[JBoss Messaging] - problem with seam and mdb on jboss5.1
by Simon Cigoj
Simon Cigoj [http://community.jboss.org/people/SimonCigoj] created the discussion
"problem with seam and mdb on jboss5.1"
To view the discussion, visit: http://community.jboss.org/message/548355#548355
--------------------------------------------------------------
I have a problem when using a mdb as a seam component. In the bean I inject some other seam somponents.
The problem is that when the server restart after a crash and the mdb is deployed it starts reading the messages
but seam is not initialized yet and I got an exception(listed above). If i start the server whith the queues
empty and submit a message to queue after the server start it is working ok.
The mdb is anothated like this :
@Name("videoConverter")
@MessageDriven(name = "VideoConverter",
activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
@ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/VideoConverterQueue"),
@ActivationConfigProperty(propertyName = "maxSession", propertyValue = "1")
})
@Pool(value = PoolDefaults.POOL_IMPLEMENTATION_STRICTMAX, maxSize = 1, timeout = 10000
Is there a posibility to stop or delay the sending off messages on server startup and start sending them only when
seam is fully funcional? I tried the @Depends antotatin on the bean but withowt success from the possible solution
mentioned here https://jira.jboss.org/browse/JBSEAM-2286?focusedCommentId=12535875 https://jira.jboss.org/browse/JBSEAM-2286?focusedCommentId=12535875 but no success.
my environment : jboss5.1 GA seam 2.2.0 GA jboss messaging 1.4
Any help would be appreceated
the error on startup :
11:24:20,477 ERROR [TxPolicy] javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException:
Attempted to invoke a Seam component outside an initialized application
11:24:30,483 ERROR [TxPolicy] javax.ejb.EJBException: Failed to acquire the pool semaphore, strictTimeout=10000
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/548355#548355]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
[JBoss Messaging] - problem with seam and mdb on jboss5.1
by Simon Cigoj
Simon Cigoj [http://community.jboss.org/people/SimonCigoj] created the discussion
"problem with seam and mdb on jboss5.1"
To view the discussion, visit: http://community.jboss.org/message/548354#548354
--------------------------------------------------------------
I have a problem when using a mdb as a seam component. In the bean I inject some other seam somponents.
The problem is that when the server restart after a crash and the mdb is deployed it starts reading the messages but seam is not initialized yet and I got an exception(listed above). If i start the server whith the queues empty and submit a message to queue after the server start it is working ok.
The mdb is anothated like this :
{code}
@Name("videoConverter")
@MessageDriven(name = "VideoConverter",
activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
@ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/VideoConverterQueue"),
@ActivationConfigProperty(propertyName = "maxSession", propertyValue = "1")
})
@Pool(value = PoolDefaults.POOL_IMPLEMENTATION_STRICTMAX, maxSize = 1, timeout = 10000
{code}
Is there a posibility to stop or delay the sending off messages on server startup and start sending them only when seam is fully funcional?
I tried the @Depends antotatin on the bean but withowt success from the possible solution mentioned https://jira.jboss.org/browse/JBSEAM-2286?focusedCommentId=12535875 here but no success.
my environment : jboss5.1 GA seam 2.2.0 GA jboss messaging 1.4
Any help would be appreceated
the error on startup :
11:24:20,477 ERROR http://community.jboss.org/message/548354#548354/TxPolicy http://community.jboss.org/message/548354#548354/TxPolicy javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted to invoke a Seam component outside an initialized application11:24:30,483 ERROR http://community.jboss.org/message/548354#548354/TxPolicy http://community.jboss.org/message/548354#548354/TxPolicy javax.ejb.EJBException: Failed to acquire the pool semaphore, strictTimeout=10000code}
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/548354#548354]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years