[Building Sakai] shutdown issue, possibly activemq
Joshua Swink
joshua.swink at gmail.com
Fri Sep 30 15:19:55 PDT 2011
We are using Sakai 2.7.1 with multiple tomcats on each server, and
they fail to shut down properly. I'm checking out the thread dumps and
such, and wonder if anyone can confirm whether this snippet might
indicate the culprit:
"ActiveMQ Transport: tcp://localhost/127.0.0.1:61616" prio=3
tid=0x0e98d400 nid=0x61 runnable [0x37237000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at org.apache.activemq.transport.tcp.TcpBufferedInputStream.fill(TcpBufferedInputStream.java:50)
at org.apache.activemq.transport.tcp.TcpTransport$2.fill(TcpTransport.java:575)
at org.apache.activemq.transport.tcp.TcpBufferedInputStream.read(TcpBufferedInputStream.java:58)
at org.apache.activemq.transport.tcp.TcpTransport$2.read(TcpTransport.java:560)
at java.io.DataInputStream.readInt(DataInputStream.java:370)
at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:269)
at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:226)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:218)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:201)
at java.lang.Thread.run(Thread.java:662)
I'm concerned with multiple processes all trying to listen on the same
port, but not sure if this could cause such a problem.
Josh
More information about the sakai-dev
mailing list