6 Replies Latest reply on Nov 20, 2019 12:59 PM by Raj__K

    BAM integration fails with error

    3893099

      Message :AsyncMilanoMESDirectTimeBooking_HTTP_PS BAM Call failed at AsyncMilanoMESDirectTimeBooking, Please Contact Fussion Midleware Team  Payload :<fault xmlns="http://www.bea.com/wli/sb/context"><errorCode>OSB-380002</errorCode><reason>[JMSPool:169818]The JMS connection pool named "ALSB_JMS_SessionPool_-483160127" has a configured connection factory JNDI name of "jms.SAPMESCF". However, an object that is not a javax.jms.ConnectionFactory is bound to that JNDI name. The object bound to that JNDI name has type "weblogic.jms.frontend.FEConnectionFactoryImpl_12210_WLStub".</reason><location><node>AsyncOpCompletePipeline</node><pipeline>request-3fb662a.N3c1202b9.0.15c34203ba1.N7b09</pipeline><stage>InsertBAMDirectTimebooking</stage><path>request-pipeline</path></location></fault> Error Code :OSB-380002

        • 1. Re: BAM integration fails with error
          Tom B-Oracle

          I suspect a misconfiguration or an interop failure. Assuming the configuration is correct - e.g. jms.SAPMESCF is the JNDI name of a connection factory that's directly configured to be in JNDI or is the local JNDI name of a 'Foreign JMS' configuration - then the type 'weblogic.jms.frontend.FEConnectionFactoryImpl_12210_WLStub' is probably fine.  What is the version of the cluster where the JMS CF is targeted?  The version of the cluster that hosts the JNDI entry?  The version of the cluster that's reporting the error? If any of these are at 12.2.1.0 or even 12.2.1.1 or 12.2.1.2 then an interop patch may be needed. Note that 12.2.1.3 has been out for two years now, and 12.2.1.4 was just released. Tom

          • 2. Re: BAM integration fails with error
            Raj__K

            Hi, Based on the Error, the server expects JMS connection factory with JNDI "jms.SAPMESCF". However, the JNDI "jms.SAPMESCF" is not of JMS connection factory.

             

            Regards!

            • 3. Re: BAM integration fails with error
              Tom B-Oracle

              It'd be interesting to see the configuration for the CF.  It's probably a CF of some kind  given that it's class name clearly seems to be that of a CF stub (weblogic.jms.frontend.FEConnectionFactoryImpl_12210_WLStub).  This is why my initial suspicion is an interop issue of some kind, expecially as PS0 is known to have interop issues and the '12210' name hints that this is PS0.

              • 4. Re: BAM integration fails with error
                Raj__K

                Yeah @Tom B-Oracle.

                @3893099. Could you update on the connection factory information.

                • 5. Re: BAM integration fails with error
                  3893099
                  SAPMESCFConnection Factoryjms/SAPMESCFDefault Targetingosb_cluster
                  • 6. Re: BAM integration fails with error
                    Raj__K

                    Hi,

                    1. The JNDI name in the Error is "jms.SAPMESCF". However the JNDI name that you have provided now is with front slash. Could you take a look at this difference.

                    3893099 wrote:

                     

                    SAPMESCFConnection Factoryjms/SAPMESCFDefault Targetingosb_cluster

                    2. The server expects JMS connection factory with JNDI "jms.SAPMESCF". Could you check whether the connection factory is of this particular type or any other like foreign JMS CF?

                     

                    Regards!