[JBoss Messaging] - DefaultJMSProvider not bound
by beve
Hi,
we received this error message after starting a JBossAS 4.2 server:
15:01:01,480 ERROR [MessagingXAResourceWrapper] ********************************Failed to connect to server
| javax.naming.NameNotFoundException: DefaultJMSProvider not bound
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
| at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
| at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
| at javax.naming.InitialContext.lookup(InitialContext.java:351)
| at org.jboss.jms.server.recovery.MessagingXAResourceWrapper.getConnectionFactory(MessagingXAResourceWrapper.java:355)
| at org.jboss.jms.server.recovery.MessagingXAResourceWrapper.connect(MessagingXAResourceWrapper.java:302)
| at org.jboss.jms.server.recovery.MessagingXAResourceWrapper.getDelegate(MessagingXAResourceWrapper.java:261)
| at org.jboss.jms.server.recovery.MessagingXAResourceWrapper.recover(MessagingXAResourceWrapper.java:109)
| at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecovery(XARecoveryModule.java:746)
| at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecovery(XARecoveryModule.java:685)
| at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:179)
| at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWork(PeriodicRecovery.java:237)
| at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:163)
|
|
This was "solved" by modifying conf/jbossjta-properties.xml:
<property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING1" value="org.jboss.jms.server.recovery.MessagingXAResourceRecovery;DefaultJMSProvider"/>
|
to:
<property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING1" value="org.jboss.jms.server.recovery.MessagingXAResourceRecovery;java:/DefaultJMSProvider"/>
|
Just posting here in case other are getting the same error.
Regards,
Daniel
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079845#4079845
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079845
18Â years, 7Â months
[JBossWS] - Dreaded Multiple context root
by nickarls
Hi,
I'm using Seam 2.0.0b1 and JBoss 4.2.1GA and have tried to follow the wiki on encrypted web services and the Seam manual and have come up with
| @Remote
| public interface FooBeanI {
| ...
|
| @Stateless
| @WebService(name="fooService", serviceName="fooService")
| @WebContext(contextRoot="/foo") //added this after suggestion after reading the forum
| @Name("fooService")
| public class FooBean implements FooBeanI {
| ...
|
and put the
| jboss-wsse-client.xml
| jboss-wsse-server.xml
| wsse.keystore
| wsse.truststore
|
under WEB-INF
and
standard-jaxws-endpoint-config.xml
under the jar META-INF
But I still get the
| 09:12:52,498 ERROR [ServiceEndpointPublisher] Cannot obtain waURL for: OSTi.ear/
| OSTi.jar
| 09:12:52,498 ERROR [MainDeployer] Could not create deployment: file:/C:/Java/jbo
| ss-4.2.1.GA/server/default/deploy/OSTi.ear/OSTi.jar/
| org.jboss.deployment.DeploymentException: Cannot create service endpoint; - nest
| ed throwable: (org.jboss.ws.WSException: Multiple context root not supported)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079833#4079833
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079833
18Â years, 7Â months