subscribe to WebLogic Topic

[narasigr]

Did anybody tried to subscribe to a remote weblogic topic?
We are trying to deploy a MDB on JBoss 4.0 , which subscribed to a remote weblogic topic. We have included wlclient.jar in the ejb classpath. While deploying MDB, it throws an error "Invalid NameSpace" from the orb invalidName exception?

Any suggestion on how to resolve this would be appreciated.

[cookserr]

Additional Information - error at startup

09:08:56,027 ERROR [DLQHandler] Initialization failed DLQHandler
javax.naming.InvalidNameException: Couldn't resolve initial reference: NameServic
e [Root exception is org.omg.CORBA.ORBPackage.InvalidName]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:50)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelpe
r.java:499)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:46
5)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext
(InitialContextFactoryImpl.java:97)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext
(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialConte
xtFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:66
2)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)

at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.(InitialContext.java:195)
at org.jboss.jms.jndi.JNDIProviderAdapter.getInitialContext(JNDIProviderA
dapter.java:40)
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:142
)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanS
upport.java:237)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:1
64)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainer
Invoker.java:545)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContaine
rInvoker.java:767)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSu
pport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBe
anSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)

[narasigr]

please find entries from the jboss-ds.xml and standardjboss.xml files

--
Jms-ds.xml


CPRWebLogicJMSProvider
org.jboss.jms.jndi.JNDIProviderAdapter
java:/XAConnectionFactory
java:/XAConnectionFactory

java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.factory.url.pkgs=weblogi.jndi
java.naming.provider.url=t3://10.45.150.69:7001



--

standardjboss.xml

<invoker-proxy-binding>
my-mdb-invoker
<invoker-mbean>default</invoker-mbean>
<proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
<proxy-factory-config>
CPRWebLogicJMSProvider
StdJMSPool
1
1
30000
1

10

</proxy-factory-config>
</invoker-proxy-binding>


We have tried to deploy the above code in JBoss 4.0.1 SP1, and we get a different error message. "Class Cast Exception."

17:36:21,609 ERROR [JMSContainerInvoker] Starting failed jboss.j2ee:binding=my-md
b-invoker,jndiName=local/CprOrderListenerMDBean,plugin=invoker,service=EJB
java.lang.ClassCastException
at org.jboss.mq.SpyConnectionConsumer.(SpyConnectionConsumer.java:9
1)
at org.jboss.mq.SpyConnection.createConnectionConsumer(SpyConnection.java
:136)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainer
Invoker.java:703)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContaine
rInvoker.java:813)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSu
pport.java:272)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBe
anSupport.java:222)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
orImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatche
r.java:144)
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.j
ava:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControll
er.java:891)
at $Proxy50.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
orImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatche
r.java:144)
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.j
ava:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:17

[txie2000]

Did you get it solved? I'm also running into this problem. Acturally the client deployed on Jboss even not able to lookup Topic Factory on WLS 8.1

[narasigr]

Nope.. We decided not to use JBoss for now.