jboss messaging

[aioaneid]

I'm having trouble installing JBossMessaging-1.0.0alpha-pr2. The readme file says it's compatible with JBoss 5.0.0alpha. Where can I find JBoss 5.0.0alpha ?

I tried to copy jboss-messaging.sar to jboss-4.0.3/server/default/deploy but it logs some errors:

18:49:20,290 WARN [ServiceController] Problem starting service jboss.messaging:
service=ServerPeer
javax.naming.NameNotFoundException: TransactionManager not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:514)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:522)
at org.jnp.server.NamingServer.getObject(NamingServer.java:528)
at org.jnp.server.NamingServer.lookup(NamingServer.java:281)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:610)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at org.jboss.messaging.core.persistence.HSQLDBPersistenceManager.start(H
SQLDBPersistenceManager.java:522)
at org.jboss.messaging.core.persistence.HSQLDBPersistenceManager.(
HSQLDBPersistenceManager.java:63)
at org.jboss.jms.server.ServerPeer.start(ServerPeer.java:162)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:118)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:127)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:245)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:960)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:428)
at org.jboss.system.ServiceController.start(ServiceController.java:446)
at org.jboss.system.ServiceController.start(ServiceController.java:446)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:245)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:285)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:989)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:790)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)
at sun.reflect.GeneratedMethodAccessor49.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:118)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:127)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:245)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
tScanner.java:319)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
canner.java:507)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
doScan(AbstractDeploymentScanner.java:192)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
loop(AbstractDeploymentScanner.java:203)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
run(AbstractDeploymentScanner.java:182)
18:49:20,415 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- MBeans waiting for other MBeans ---
ObjectName: jboss.messaging:service=ServerPeer
State: FAILED
Reason: javax.naming.NameNotFoundException: TransactionManager not bound
I Depend On:
jboss.messaging:service=Connector,transport=socket
jboss.jca:service=DataSourceBinding,name=DefaultDS
jboss.messaging:service=AspectLoader
Depends On Me:
jboss.messaging.destination:service=Topic,name=testTopic
jboss.messaging.destination:service=Topic,name=securedTopic
jboss.messaging.destination:service=Topic,name=testDurableTopic
jboss.messaging.destination:service=Queue,name=testQueue
jboss.messaging.destination:service=Queue,name=A
jboss.messaging.destination:service=Queue,name=B
jboss.messaging.destination:service=Queue,name=C
jboss.messaging.destination:service=Queue,name=D
jboss.messaging.destination:service=Queue,name=ex

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.messaging:service=ServerPeer
State: FAILED
Reason: javax.naming.NameNotFoundException: TransactionManager not bound
I Depend On:
jboss.messaging:service=Connector,transport=socket
jboss.jca:service=DataSourceBinding,name=DefaultDS
jboss.messaging:service=AspectLoader
Depends On Me:
jboss.messaging.destination:service=Topic,name=testTopic
jboss.messaging.destination:service=Topic,name=securedTopic
jboss.messaging.destination:service=Topic,name=testDurableTopic
jboss.messaging.destination:service=Queue,name=testQueue
jboss.messaging.destination:service=Queue,name=A
jboss.messaging.destination:service=Queue,name=B
jboss.messaging.destination:service=Queue,name=C
jboss.messaging.destination:service=Queue,name=D
jboss.messaging.destination:service=Queue,name=ex

Any help would be appreciated.

Daniel

[ovidiu.feodorov]

Thanks for trying out an alpha.


JBoss 5.0.0 alpha is actually the repository head. I doubt there is a standalone JBoss 5.0.0 alpha release. In order to try it with the head, you will have to check it out from CVS and build it.

However, it should work in JBoss 4.0.x. I will take a look to see why it doesn't and get back to you.

[ovidiu.feodorov]

Moved your topic to the appropriate forum.

[cartola]

Hi!
I'm having the same problem.
I'm deploying the jboss-messaging.sar on a JBoss 4.0.2, in default configuration.
I'm trying the JBossMessaging-1.0.0alpha-pr2 version.
Does anyone has a solution for this event?

[ovidiu.feodorov]

I will upload on sourceforge a PR2 update to that fixes this problem. This will probably happen on Monday. I'll post an anouncement here as well.

Otherwise, you can build a release bundle by youself, from the CVS head, as follows: check out a fresh jboss head from the anonymous CVS (in a directory called jboss-head, for the purpose of this example) and then:

cd jboss-head
./build/build.sh
cd jms
ant release-bundle

You will find a JBoss 4.x deployable sar under jboss-head/jms/output/lib/jboss-messaging-scoped.sar.

[ovidiu.feodorov]

I've released PR2.1. It is available for download on sourceforge at http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=157261