-
1. Re: JBOSS subscribe Weblogic JMS Topic
adrian.brock Apr 8, 2004 11:37 AM (in response to ftftft)I've seen lots of posts like this.
People say they can't get it work but never post what the error message is
or what is not working.
The jndi view problem is probably due to some sort of recursion
in your jndi tree. Due to one part of the tree including another part and vice versa.
Adding the following property to the external context mbean might help fix it:<attribute name="RemoteAccess">false</attribute>
Regards,
Adrian -
2. Re: JBOSS subscribe Weblogic JMS Topic
ftftft Apr 8, 2004 1:57 PM (in response to ftftft)Thanks adrian. I believe there is no error message in the console. That is the reason no one post the error message.
I find the follow link that provide a sample to link websphere and jboss.
http://sourceforge.net/tracker/index.php?func=detail&aid=753022&group_id=22866&atid=376687
but I cannot download the sample code. Where can I find the file?"adrian@jboss.org" wrote:
I've seen lots of posts like this.
People say they can't get it work but never post what the error message is
or what is not working.
The jndi view problem is probably due to some sort of recursion
in your jndi tree. Due to one part of the tree including another part and vice versa.
Adding the following property to the external context mbean might help fix it:<attribute name="RemoteAccess">false</attribute>
Regards,
Adrian -
3. Re: JBOSS subscribe Weblogic JMS Topic
ftftft Apr 8, 2004 3:19 PM (in response to ftftft)Finally, I move forward a little bit and get the follow exception. Would you help me figure it out? Thanks a lot.
2004-04-08 16:00:51,204 DEBUG [WeblogicMQProvider] connecting to remote JNDI with props: {java.naming.provider.url=t3://192.168.1.152:80, java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory}
2004-04-08 16:00:51,205 DEBUG [WeblogicMQProvider] props information javax.naming.InitialContext@a6997
2004-04-08 16:00:51,205 DEBUG [WeblogicMQProvider] created context: javax.naming.InitialContext@a6997
2004-04-08 16:00:51,209 ERROR [org.jboss.ejb.plugins.jms.DLQHandler] Initialization failed
javax.jms.JMSException: Error creating the dlq connection: Unhandled exception in lookup
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:169)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:158)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:458)"adrian@jboss.org" wrote:
I've seen lots of posts like this.
People say they can't get it work but never post what the error message is
or what is not working.
The jndi view problem is probably due to some sort of recursion
in your jndi tree. Due to one part of the tree including another part and vice versa.
Adding the following property to the external context mbean might help fix it:<attribute name="RemoteAccess">false</attribute>
Regards,
Adrian