After fixing the JMS problem, I'm now seeing a hang in JBoss Cache:
"main" prio=1 tid=0x80b31a18 nid=0x40a4 in Object.wait()
[0x80453000..0x80455fb0]
at java.lang.Object.wait(Native Method)
- waiting on <0xb0ba95f0> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.cache.CacheImpl
$MessageListenerAdaptor.waitForState(CacheImpl.java:3379)
- locked <0xb0ba95f0> (a java.lang.Object)
at
org.jboss.cache.CacheImpl.fetchStateOnStartup(CacheImpl.java:1273)
at org.jboss.cache.CacheImpl.internalStart(CacheImpl.java:767)
at org.jboss.cache.CacheImpl.start(CacheImpl.java:708)
at
org.jboss.cache.jmx.CacheJmxWrapper.start(CacheJmxWrapper.java:614)
Brian? :-)
On Fri, 2007-10-19 at 16:37 +0200, Adrian wrote:
On Fri, 2007-10-19 at 16:17 +0200, Adrian wrote:
> I checked out the Beta4 tag and built the assembly.
>
> I've added it to the repository, so we're just waiting
> for the mirroring to catch up so we can test it.
The TM problem is fixed, I'm seeing a different problem
now relating to jgroups or jboss messaging?
(the default configuration boots fine).
16:33:06,342 ERROR [ExceptionUtil]
org.jboss.messaging.core.jmx.MessagingPostOfficeService@9198a2 startService
java.lang.NullPointerException: the specifed protocol stack
configuration was null
at
org.jgroups.conf.ConfiguratorFactory.checkForNullConfiguration(ConfiguratorFactory.java:482)
at
org.jgroups.conf.ConfiguratorFactory.getStackConfigurator(ConfiguratorFactory.java:150)
at org.jgroups.JChannel.<init>(JChannel.java:195)
at
org.jboss.messaging.core.impl.jchannelfactory.XMLChannelFactory.createControlChannel(XMLChannelFactory.java:80)
at
org.jboss.messaging.core.impl.postoffice.GroupMember.start(GroupMember.java:124)
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx