I am trying to setup Messaging Bridge (weblogic 6.1 with service packs) to MQ Series in a solaris system. MQ Series setup tested successfully as a standalone. But when I tried to target a server in the Messaging Bridge, Weblogic crashes without any error log. The JMSMQ log doesn't provide much information. Has anybody encountered a problem similar to this. There is not much help in bea e-docs. Thanks for your help
A few comments/questions... 1) What Service Pack are you using? There was a bug in the Messaging Bridge with regards to MQSeries in SP3. This was addressed by the CR081511 patch for SP3, and the patch has also been rolled into SP4. 2) Have you tried turning on debugging for the Messaging Bridge? Add the following system properties to your server startup script:
3) Have you read this document: Using Foreign JMS Providers with WebLogic Server? 4) What QOS mode are you running the bridge in? I do not think 6.1 supports Exactly-Once mode with external providers.
sriram Vaidhya
Greenhorn
Joined: Dec 24, 2002
Posts: 4
posted
0
After Setting up all the debug options, I finally got some exceptions. I am trying to connect an MQ queue to a Weblogic JMS queue using the JMS bridge, We have Weblogic with service pack 4 running under solaris box.
I have jms-xa-adp.rar deployed in /applications folder. Am I missing something or running wrong versions.Thanks for the help.Here are the log messages when server is started. ####<Jan 3, 2003 10:57:21 AM CST> <Warning> <J2EE> <scritturadev> <scritturadev> <main> <system> <> <160007> <You are running WebLogic Server with J2EE 1.3 features enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP 1.2, Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server 6.1 is of a non-final version of the appropriate specification. It is subject to change in future releases once the specification becomes finalized. This may cause application code developed for BEA WebLogic Server 6.1 that uses the new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform supported in future releases of BEA WebLogic Server.> ####<Jan 3, 2003 10:57:21 AM CST> <Info> <Dispatcher> <scritturadev> <scritturadev> <main> <system> <> <000000> <Exception thrown by rmi server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 - jvmid: '3553414848833889764S:10.4.132.104:[7001,7001,7002,7002,7001,7002,-1]:ipicorp:scritturadev', oid: '9', implementation: 'weblogic.jndi.internal.RootNamingNode@209e41''> javax.naming.NameNotFoundException: Unable to resolve 'eis.jms/' Resolved: '' Unresolved:'eis' ; remaining name 'eis.jms/WLSConnectionFactoryJNDIXA' at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:890)
... ... ####<Jan 3, 2003 10:57:21 AM CST> <Info> <Connector> <scritturadev> <scritturadev> <main> <system> <> <190014> <Initializing connection pool for resource adapter Weblogic Messaging Bridge Adapter (XA).> ####<Jan 3, 2003 10:57:21 AM CST> <Warning> <Connector> <scritturadev> <scritturadev> <main> <system> <> <190025> << Weblogic Messaging Bridge Adapter (XA) > Connection Pool has been initialized with no connections.> ####<Jan 3, 2003 10:57:21 AM CST> <Info> <Connector> <scritturadev> <scritturadev> <main> <system> <> <190026> << Weblogic Messaging Bridge Adapter (XA) > Connection Pool initialization has completed successfully.> ####<Jan 3, 2003 10:57:21 AM CST> <Info> <J2EE> <scritturadev> <scritturadev> <main> <system> <> <160003> <Deployed : jms-xa-adp> ####<Jan 3, 2003 10:57:21 AM CST> <Warning> <J2EE> <scritturadev> <scritturadev> <main> <system> <> <160007> <You are running WebLogic Server with J2EE 1.3 features enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP 1.2, Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server 6.1 is of a non-final version of the appropriate specification. It is subject to change in future releases once the specification becomes finalized. This may cause application code developed for BEA WebLogic Server 6.1 that uses the new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform supported in future releases of BEA WebLogic Server.> ####<Jan 3, 2003 10:57:21 AM CST> <Info> <Dispatcher> <scritturadev> <scritturadev> <main> <system> <> <000000> <Exception thrown by rmi server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 - jvmid: '3553414848833889764S:10.4.132.104:[7001,7001,7002,7002,7001,7002,-1]:ipicorp:scritturadev', oid: '9', implementation: 'weblogic.jndi.internal.RootNamingNode@209e41''> javax.naming.NameNotFoundException: Unable to resolve 'eis.jms.WLSConnectionFactoryJNDILocal' Resolved: 'eis.jms' Unresolved:'WLSConnectionFactoryJNDILocal' ; remaining name 'WLSConnectionFactoryJNDILocal' at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:890)
0
