12 Replies Latest reply: Nov 4, 2009 4:30 PM by 732201 RSS

    BAM cannot connect to WEBLOGIC

    MarioMesquita
      I have this setup in my EMS :

      WeblogicJMS

      View|Edit|Copy|Delete|Create|Start|Stop|Test|Refresh

      Name: WeblogicJMS
      Owner: fmwadmin
      Created: 7/29/08 3:00:57 PM
      Last modified: 7/30/08 6:34:52 PM
      Status: Stopped

      Initial Context Factory: weblogic.jni.WLInitialContextFactory.
      JNDI Service Provider URL: t3://10.20.162.16:7001.
      Topic/Queue ConnectionFactory Name: jms/confactory.
      Topic/Queue Name: jms/topic.
      JNDI Username: weblogic.
      JNDI Password: ********.
      JMS Message Type: TextMessage.
      Durable Subscriber Name (Optional): OracleBam.
      Message Selector (Optional): OracleBam.
      DataObject Name: /WeblogicJMS/TextJMS.
      Operation: Insert.
      Batching: No.
      Transaction: No.
      Start when BAM Server starts: No.
      JMS Username (Optional): .
      JMS Password (Optional): .

      XML Formatting

      Pre-Processing

      Message Specification
      Message Element Name: textdata

      Column Value
      Element Tag
      Attribute

      Source to Data Object Field Mapping

      Key Tag name Data Object Field
      . textdata. textdata. String



      When I try to start the connection I get this error:

      An error occurred while processing your request
      Details...
      Exception Message BAM-00533: Resource open for destination "jms/topic" failed.
      Stack Trace at oracle.bam.common.messaging.base.operation.MessageOperationBase.onStartFailedException(MessageOperationBase.java:1582) at oracle.bam.common.messaging.api.MessageConsumerRegistry.onStartFailedException(MessageConsumerRegistry.java:822) at oracle.bam.common.messaging.base.operation.MessageOperationBase.start(MessageOperationBase.java:1487) at oracle.bam.common.messaging.base.operation.MessageOperationBase.start(MessageOperationBase.java:1442) at oracle.bam.ems.engine.JMSListener.<init>(JMSListener.java:143) at oracle.bam.ems.engine.EMSHandler.initMessageHandler(EMSHandler.java:392) at oracle.bam.ems.engine.EMSHandler.start(EMSHandler.java:422) at oracle.bam.ems.server.EMSServer.start(EMSServer.java:103) at oracle.bam.web.architect.Sources.startEMS(Sources.java:930) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at oracle.bam.web.shared.WebPage.invokeWebMethod(WebPage.java:480) at oracle.bam.web.shared.WebPage.processRequest(WebPage.java:414) at oracle.bam.web.shared.WebPage.processRequest(WebPage.java:298) at _2609._architect._default._jspService(_default.java:46) at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:60) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:406) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:706) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:627) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65) at oracle.bam.web.cache.ClientSideCache.doFilter(ClientSideCache.java:79) at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15) at oracle.bam.web.filters.GZIPFilter.doFilter(GZIPFilter.java:86) at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17) at oracle.bam.web.redirect.Redirect.doFilter(Redirect.java:66) at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17) at oracle.bam.web.filters.ValidateBrowserSupport.doFilter(ValidateBrowserSupport.java:93) at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17) at oracle.bam.web.filters.CharsetFixupFilter.doFilter(CharsetFixupFilter.java:65) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:583) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:334) at com.evermind.server.http.HttpRequestHandler.doDispatchRequest(HttpRequestHandler.java:942) at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:843) at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:658) at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:626) at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:417) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:189) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:163) at oracle.oc4j.network.ServerSocketReadHandler$ClientRunnable.run(ServerSocketReadHandler.java:275) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) ...
      Debugging Information BAM-00553: Resources start for destination "jms/topic" failed. [ErrorSource="Messaging", ErrorID="MessageFramework.Start.Failed"] BAM-00500: Exception in messaging framework "BAM-00533: Resource open for destination "jms/topic" failed.". [ErrorSource="Messaging", ErrorID="MessageFramework.Exception"] BAM-00533: Resource open for destination "jms/topic" failed. [ErrorSource="Messaging", ErrorID="MessageFramework.Open.Failed"] BAM-00533: Resource open for destination "jms/topic" failed. [ErrorSource="Messaging", ErrorID="MessageFramework.Open.Failed"] BAM-00523: Resource recovery for destination "jms/topic" failed. [ErrorSource="Messaging", ErrorID="MessageFramework.Recovery.Failed"] BAM-00523: Resource recovery for destination "jms/topic" failed. [ErrorSource="Messaging", ErrorID="MessageFramework.Recovery.Failed"] BAM-00500: Exception in messaging framework "BAM-00500: Exception in messaging framework "Cannot instantiate class: weblogic.jni.WLInitialContextFactory".". [ErrorSource="Messaging", ErrorID="MessageFramework.Exception"] BAM-00500: Exception in messaging framework "Cannot instantiate class: weblogic.jni.WLInitialContextFactory". [ErrorSource="Messaging", ErrorID="MessageFramework.Exception"] Cannot instantiate class: weblogic.jni.WLInitialContextFactory [ErrorSource="javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jni.WLInitialContextFactory [Root exception is oracle.classloader.util.AnnotatedClassNotFoundException: Missing class: weblogic.jni.WLInitialContextFactory Dependent class: com.sun.naming.internal.VersionHelper12 Loader: jre.bootstrap:1.5.0_11 Code-Source: unknown Configuration: jre bootstrap This load was initiated at OracleBamWeb.web.oracle-bam-web:0.0.0 using the Class.forName() method. The missing class is not available from any code-source or loader in the system.]"] Missing class: weblogic.jni.WLInitialContextFactory Dependent class: com.sun.naming.internal.VersionHelper12 Loader: jre.bootstrap:1.5.0_11 Code-Source: unknown Configuration: jre bootstrap This load was initiated at OracleBamWeb.web.oracle-bam-web:0.0.0 using the Class.forName() method. The missing class is not available from any code-source or loader in the system. [ErrorSource="oracle.classloader.util.AnnotatedClassNotFoundException: Missing class: weblogic.jni.WLInitialContextFactory Dependent class: com.sun.naming.internal.VersionHelper12 Loader: jre.bootstrap:1.5.0_11 Code-Source: unknown Configuration: jre bootstrap This load was initiated at OracleBamWeb.web.oracle-bam-web:0.0.0 using the Class.forName() method. The missing class is not available from any code-source or loader in the system."] Debugging information: oracle.bam.common.messaging.api.exception.StartFailedException: BAM-00553: Resources start for destination "jms/topic" failed.oracle.bam.common.messaging.api.exception.StartFailedException: BAM-00553: Resources start for destination "jms/topic" failed. at oracle.bam.common.messaging.base.operation.MessageOperationBase.onStartFailedException(MessageOperationBase.java:1582) at oracle.bam.common.messaging.api.MessageConsumerRegistry.onStartFailedException(MessageConsumerRegistry.java:822) at oracle.bam.common.messaging.base.operation.MessageOperationBase.start(MessageOperationBase.java:1487) at oracle.bam.common.messaging.base.operation.MessageOperationBase.start(MessageOperationBase.java:1442) at oracle.bam.ems.engine.JMSListener.<init>(JMSListener.java:143) at oracle.bam.ems.engine.EMSHandler.initMessageHandler(EMSHandler.java:392) at oracle.bam.ems.engine.EMSHandler.start(EMSHandler.java:422) at oracle.bam.ems.server.EMSServer.start(EMSServer.java:103) at oracle.bam.web.architect.Sources.startEMS(Sources.java:930) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at oracle.bam.web.shared.WebPage.invokeWebMethod(WebPage.java:480) at oracle.bam.web.shared.WebPage.processRequest(WebPage.java:414) at oracle.bam.web.shared.WebPage.processRequest(WebPage.java:298) at _2609._architect._default._jspService(_default.java:46) at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:60) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:406) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:706) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:627) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65) at oracle.bam.web.cache.ClientSideCache.doFilter(ClientSideCache.java:79) at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15) at oracle.bam.web.filters.GZIPFilter.doFilter(GZIPFilter.java:86) at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17) at oracle.bam.web.redirect.Redirect.doFilter(Redirect.java:66) at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17) at oracle.bam.web.filters.ValidateBrowserSupport.doFilter(ValidateBrowserSupport.java:93) at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17) at oracle.bam.web.filters.CharsetFixupFilter.doFilter(CharsetFixupFilter.java:65) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:583) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:334) at com.evermind.server.http.HttpRequestHandler.doDispatchRequest(HttpRequestHandler.java:942) at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:843) at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:658) at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:626) at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:417) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:189) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:163) at oracle.oc4j.network.ServerSocketReadHandler$ClientRunnable.run(ServerSocketReadHandler.java:275) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Caused by: oracle.bam.common.messaging.api.MessageFrameworkException: BAM-00500: Exception in messaging framework "BAM-00533: Resource open for destination "jms/topic" failed.". at oracle.bam.common.messaging.base.operation.MessageOperationBase.onStartException(MessageOperationBase.java:1566) at oracle.bam.common.messaging.base.operation.MessageOperationBase.performStart(MessageOperationBase.java:1538) at oracle.bam.common.messaging.api.jms.JMSMessageConsumerRegistry.performStart(JMSMessageConsumerRegistry.java:444) at oracle.bam.common.messaging.base.operation.MessageOperationBase.start(MessageOperationBase.java:1478) ... 42 more Caused by: oracle.bam.common.messaging.api.exception.OpenFailedException: BAM-00533: Resource open for destination "jms/topic" failed. at oracle.bam.common.messaging.base.operation.MessageOperationBase.waitForOpen(MessageOperationBase.java:1321) at oracle.bam.common.messaging.base.operation.MessageOperationBase.waitForOpen(MessageOperationBase.java:1255) at oracle.bam.common.messaging.base.operation.MessageOperationBase.performStart(MessageOperationBase.java:1526) ... 44 more Caused by: oracle.bam.common.messaging.api.exception.OpenFailedException: BAM-00533: Resource open for destination "jms/topic" failed. at oracle.bam.common.messaging.base.operation.MessageOperationBase.onOpenFailedException(MessageOperationBase.java:1238) at oracle.bam.common.messaging.api.MessageConsumerRegistry.onOpenFailedException(MessageConsumerRegistry.java:785) at oracle.bam.common.messaging.base.operation.MessageOperationBase.open(MessageOperationBase.java:1138) at oracle.bam.common.messaging.base.operation.MessageOperationBase.access$000(MessageOperationBase.java:71) at oracle.bam.common.messaging.base.operation.MessageOperationBase$1.performOperation(MessageOperationBase.java:1118) at oracle.bam.common.messaging.base.operation.MessageOperationBase$UtilityThread.run(MessageOperationBase.java:2512) Caused by: oracle.bam.common.messaging.api.exception.RecoveryFailedException: BAM-00523: Resource recovery for destination "jms/topic" failed. at oracle.bam.common.messaging.base.operation.MessageOperationBase.onRecoveryFailedException(MessageOperationBase.java:1993) at oracle.bam.common.messaging.api.MessageConsumerRegistry.onRecoveryFailedException(MessageConsumerRegistry.java:804) at oracle.bam.common.messaging.base.operation.MessageOperationBase.recover(MessageOperationBase.java:1831) at oracle.bam.common.messaging.base.operation.MessageOperationBase.onOpenException(MessageOperationBase.java:1217) at oracle.bam.common.messaging.base.operation.MessageOperationBase.performOpen(MessageOperationBase.java:1188) at oracle.bam.common.messaging.base.operation.MessageOperationBase.open(MessageOperationBase.java:1129) ... 3 more Caused by: oracle.bam.common.messaging.api.exception.RecoveryFailedException: BAM-00523: Resource recovery for destination "jms/topic" failed. at oracle.bam.common.messaging.base.operation.MessageOperationBase.performRecovery(MessageOperationBase.java:1945) at oracle.bam.common.messaging.base.operation.MessageOperationBase.recover(MessageOperationBase.java:1822) ... 6 more Caused by: oracle.bam.common.messaging.api.MessageFrameworkException: BAM-00500: Exception in messaging framework "BAM-00500: Exception in messaging framework "Cannot instantiate class: weblogic.jni.WLInitialContextFactory".". at oracle.bam.common.messaging.api.jms.JMSMessageConsumerRegistry.acquireResources(JMSMessageConsumerRegistry.java:730) at oracle.bam.common.messaging.base.operation.MessageOperationBase.performOpen(MessageOperationBase.java:1177) ... 4 more Caused by: oracle.bam.common.messaging.api.MessageFrameworkException: BAM-00500: Exception in messaging framework "Cannot instantiate class: weblogic.jni.WLInitialContextFactory". at oracle.bam.common.messaging.base.connection.jms.JMSConnectionFactory.newInstance(JMSConnectionFactory.java:317) at oracle.bam.common.messaging.base.connection.jms.JMSConnectionFactory.newInstance(JMSConnectionFactory.java:47) at oracle.bam.common.messaging.base.connection.ConnectionFactoryBase.getInstance(ConnectionFactoryBase.java:82) at oracle.bam.common.messaging.api.jms.JMSMessageConsumerRegistry.acquireResources(JMSMessageConsumerRegistry.java:677) ... 5 more Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jni.WLInitialContextFactory [Root exception is oracle.classloader.util.AnnotatedClassNotFoundException: Missing class: weblogic.jni.WLInitialContextFactory Dependent class: com.sun.naming.internal.VersionHelper12 Loader: jre.bootstrap:1.5.0_11 Code-Source: unknown Configuration: jre bootstrap This load was initiated at OracleBamWeb.web.oracle-bam-web:0.0.0 using the Class.forName() method. The missing class is not available from any code-source or loader in the system.] at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247) at javax.naming.InitialContext.init(InitialContext.java:223) at javax.naming.InitialContext.<init>(InitialContext.java:197) at oracle.bam.common.messaging.base.connection.jms.JMSConnectionFactory.newInstance(JMSConnectionFactory.java:300) ... 8 more Caused by: oracle.classloader.util.AnnotatedClassNotFoundException: Missing class: weblogic.jni.WLInitialContextFactory Dependent class: com.sun.naming.internal.VersionHelper12 Loader: jre.bootstrap:1.5.0_11 Code-Source: unknown Configuration: jre bootstrap This load was initiated at OracleBamWeb.web.oracle-bam-web:0.0.0 using the Class.forName() method. The missing class is not available from any code-source or loader in the system. at oracle.classloader.PolicyClassLoader.handleClassNotFound(PolicyClassLoader.java:2169) at oracle.classloader.PolicyClassLoader.internalLoadClass(PolicyClassLoader.java:1716) at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1672) at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1657) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:242) at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:654) ... 12 more ...
      EventParam 1 ...
      State oracle.bam.web.architect.Sources ...
      Event startEMS ...
      Assembly Architect



      Anybody knows what to do?
        • 1. Re: BAM cannot connect to WEBLOGIC
          614067
          Mario
          Have you made sure that the connection with Weblogic is established and the message gets published to the topic? From my experience there could be two points of failure -
          1. The message doesn't get published to oc4J ( configuration of JNDI properties, jms.xml, etc.) -
          2. Message gets published to the oc4J ( can be verified by watching the console or via a jmslistener) but is not interpreted by EMS

          Payal
          • 2. Re: BAM cannot connect to WEBLOGIC
            MarioMesquita
            Hi Payal

            Yep, I'm sure that the connection with Weblogic is ok. I've checked this via java program. My java program has the jms config mentioned above,
            I just addded the file weblogic.jar in the classpath, and the java program works fine (it is able to publish and consume jms messages).

            However, when I added the same file weblogic.jar on BAM classpath and try the same jms config, it doesn't works (it throws the exception above).
            I guess that it's a problem with classpath config on BAM.

            The main question is: Have somebody ever seen BAM (ems) and Weblogic JMS connection working fine?

            []'s
            Mario
            • 3. Re: BAM cannot connect to WEBLOGIC
              665667
              Hi Mario

              have u resolve this problem?, because i had the same problem....!!!!!
              • 4. Re: BAM cannot connect to WEBLOGIC
                MarioMesquita
                Unfortunelly not, actually I doubt if somebody in this world have done such a thing. It is like they(Oracle) advertise something that they dont know how to do.
                • 5. Re: BAM cannot connect to WEBLOGIC
                  614067
                  Mario
                  Just wanted to confirm that you have defined the JMS topic in JMS.xml ?
                  Were you able to test the EMS by clicking on the Test button? Did it show the Status as OK?

                  We are evaluating the error message and I will get back to you with more information.

                  Payal

                  Edited by: user611064 on Oct 21, 2008 9:39 AM
                  • 6. Re: BAM cannot connect to WEBLOGIC
                    MarioMesquita
                    Hi Payal,

                    Answering:
                    Just wanted to confirm that you have defined the JMS topic in JMS.xml ?
                    Yes we did

                    Were you able to test the EMS by clicking on the Test button? Did it show the Status as OK?
                    We press the test button but we got that error above, so the status went not OK

                    Mario
                    • 7. Re: BAM cannot connect to WEBLOGIC
                      614067
                      Mario
                      Does the "Topic/Queue Connection Factory Name:" and "Topic/Queue Name:" (as entered in Architect) exist? do "jms/confactory" and "jms/topic" show up in the WLS Admin Console?

                      Regards
                      Payal

                      Edited by: user611064 on Oct 22, 2008 3:08 PM
                      • 8. Re: BAM cannot connect to WEBLOGIC
                        MarioMesquita
                        Payal,

                        yes, the topic name exists for sure. I've done a JMS read/write test using a java program and it works fine. The problem occurs just when I use BAM 11 tp4.

                        Mario
                        • 9. Re: BAM cannot connect to WEBLOGIC
                          MohanSoundararajan
                          Is this problem solved ?
                          I too face similar problem . . .
                          It says 'Test failed - BAM-00553: Resources start for destination "jms/mytestqueue" failed'

                          However this queue exists and I can produce and consume from this queue through stand alone java programs.

                          In my case, BAM runs on a seperate Weblogic domain and the JMS queue is on another weblogic domain, however both on the same machine.


                          Initial Context Factory: weblogic.jndi.WLInitialContextFactory.
                          JNDI Service Provider URL: t3://localhost:7001. ( this is the weblogic domain, where my jms queue resides )
                          Topic/Queue Connection Factory Name: weblogic/jms/ConnectionFactory.
                          Topic/Queue Name: jms/mytestqueue.
                          JNDI Username: .
                          JNDI Password: .
                          JMS Message Type: MapMessage.
                          • 10. Re: BAM cannot connect to WEBLOGIC
                            459652
                            This functionality was broken in 11g TP4 which was based on OC4J. FMW 11g since then has switched to using Weblogic. Please use latest early access or beta version of the product. Please contact BAM product management if you need access to this.
                            • 11. Re: BAM cannot connect to WEBLOGIC
                              632592
                              The new version of BAM the beta version doesnt allowed the user to install over UBUNTU, just Red Hat, SUSE and a I think it is called AsiaUX. This is a big BS because they are doing a type of discrimination, just because Ubuntu you can download for free, but they forgot that Ubuntu if you want support you have to pay for it. So it is a big shame for Oracle doing this.

                              Mario
                              • 12. Re: BAM cannot connect to WEBLOGIC
                                732201
                                I was able to connect successfully....the JNDI Provider URL needs to point to bam server port(in my case wasnt 7001).