-
1. Re: Failure getting messages from a remote queue
abhiejit Apr 7, 2006 9:30 AM (in response to germonday)Few days back I was looking for the same :)
Actually you have to define customized JMS Provider in addition to the default one. You also need to define your own invoker and container configuration either in jboss.xml or standardjboss.xml
answer to your question is already posted in the forum see this link http://www.jboss.org/index.html?module=bb&op=viewtopic&t=43817 -
2. Re: Failure getting messages from a remote queue
germonday Apr 10, 2006 7:25 AM (in response to germonday)Thanks for that. I followed the HowDoIConfigureAnMDBToTalkToARemoteQueue article but I'm now getting this error in JBoss:
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.mq:name=RemoteMQProvider,server=cslnt20,service=JMSProviderLoa
der
State: FAILED
Reason: org.jboss.deployment.DeploymentException: No Attribute found with name
: ProviderUrl
Does anyone know how to fix this?
Thanking you,
Ger -
3. Re: Failure getting messages from a remote queue
abhiejit Apr 27, 2006 10:48 AM (in response to germonday)The attribute ProviderURL supported by lower version of jboss. Since jboss 4.x we need to use
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
java.naming.provider.url=<remoteip1>:1100,<remoteip2>:1100 -
4. Re: Failure getting messages from a remote queue
abhiejit Apr 27, 2006 10:57 AM (in response to germonday)
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
java.naming.provider.url=<remoteip1>:1100,<remoteip2>:1100