[jboss-dev-forums] [Design of Clustering on JBoss (Clusters/JBoss)] - Re: JBAS-4717 - Problem with @JMX for clustering
adrian@jboss.org
do-not-reply at jboss.com
Tue Sep 18 08:25:48 EDT 2007
Thanks. I committed the change, but I'm seeing other errors in the clustering
with and without the new ServiceController based jmx lifecycle.
First I'm seeing messages like the following:
| 13:56:06,511 WARN [JChannelFactory] Flush failed at 10.11.14.86:32776 DefaultPartition-HAPartitionCache
|
Before that it hangs at the following stacktrace
| "main" prio=1 tid=0x80cbdfa0 nid=0x2847 in Object.wait() [0x804d2000..0x804d5130]
| at java.lang.Object.wait(Native Method)
| - waiting on <0xaf1e6838> (a org.jgroups.util.Promise)
| at org.jgroups.util.Promise.doWait(Promise.java:104)
| at org.jgroups.util.Promise._getResultWithTimeout(Promise.java:60)
| at org.jgroups.util.Promise.getResultWithTimeout(Promise.java:28)
| - locked <0xaf1e6838> (a org.jgroups.util.Promise)
| at org.jgroups.protocols.pbcast.FLUSH.startFlush(FLUSH.java:207)
| at org.jgroups.protocols.pbcast.FLUSH.startFlush(FLUSH.java:229)
| at org.jgroups.protocols.pbcast.FLUSH.startFlush(FLUSH.java:229)
| at org.jgroups.protocols.pbcast.FLUSH.down(FLUSH.java:263)
| at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:339)
| at org.jgroups.JChannel.downcall(JChannel.java:1240)
| at org.jgroups.JChannel.startFlush(JChannel.java:1504)
| at org.jgroups.JChannelFactory.connect(JChannelFactory.java:364)
| - locked <0xade09c70> (a org.jgroups.JChannelFactory$Entry)
|
I then see NPEs in the DEBUG logging at shutdown:
| 2007-09-18 13:58:35,888 DEBUG [org.jboss.system.ServiceController] destroying service: jboss.jgroups:service=MultiplexerChannelFactory
| 2007-09-18 13:58:35,890 DEBUG [org.jboss.system.microcontainer.StartStopLifecycleAction] Error during stop for jboss.jgroups:service=MultiplexerChannelFactory
| java.lang.NullPointerException
| at org.jgroups.jmx.JChannelFactory.stop(JChannelFactory.java:74)
| at AOPContainerProxy$17.stop(AOPContainerProxy$17.java)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
| at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184)
| at $Proxy4.stop(Unknown Source)
| at org.jboss.system.microcontainer.StartStopLifecycleAction.uninstallAction(StartStopLifecycleAction.java:56)
|
I'm guessing that the start() is really failing and that it shouldn't be a WARN?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085457#4085457
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4085457
More information about the jboss-dev-forums
mailing list