6 Replies Latest reply on Feb 6, 2018 4:59 PM by Subba Rao Bhamidipati

    Oracle EBS "Push Notification" Service Component is failing to start

    Subba Rao Bhamidipati

      Hi,

      We are trying to configure and enable "Push Notifications" for Oracle EBS enterprise distribution Mobile apps.

      After providing all MCS configuration details in "Mobile Push Notification Configuration", we are getting below error.

       

      Maximum number of errors (10) have been reached for this Service Component -> oracle.apps.fnd.cp.gsc.ProcessorException: Queue handler invoker has not been initialized. Outbound agent name is : FND_MBL_NOTIFICATION_OUT Any inputs on this would be much appreciated.

       

      Also attached the screenshot of the error.

       

      Thanks,

      Subba

        • 1. Re: Oracle EBS "Push Notification" Service Component is failing to start
          mdtaylor

          Please post the error messages from the Generic Service Component logs for that mobile processor.  They should be accessible from Oracle Applications Manager in Workflow or Generic Services.

          • 2. Re: Oracle EBS "Push Notification" Service Component is failing to start
            Subba Rao Bhamidipati

            Hi,

             

            Thank you for the reply.

            Below are some of the few logs we captured,

             

            ========= Last few lines of error message

            [Jan 23, 2018 1:07:54 PM EST]:1516730874315:-1:-1:nchlarbycm02.red.hat.local:10.177.72.8:-1:-1:1:20420:SYSADMIN(0):-1:Thread[BES Dispatch Thread,5,main]:2035383740:77393:1516730864174:5:UNEXPECTED:[SVC-GSM-FNDMBLPNTFSVC-416972 : oracle.apps.fnd.cp.gsc.SvcComponentContainer.onBusinessEvent(BusinessEvent)]:An unexpected RuntimeException or other Throwable occurred -> java.lang.NoClassDefFoundError: org/codehaus/jackson/map/JsonMappingException

            [Jan 23, 2018 1:07:54 PM EST]:1516730874316:-1:-1:nchlarbycm02.red.hat.local:10.177.72.8:-1:-1:1:20420:SYSADMIN(0):-1:Thread[BES Dispatch Thread,5,main]:2035383740:77393:1516730864174:5:EXCEPTION:[SVC-GSM-FNDMBLPNTFSVC-416972 : oracle.apps.fnd.cp.gsc.SvcComponentStateMachine.updateComponentStatus(Logger, Connection, int, String, String)]:BEGIN (Logger{mLog=[$Header: AppsLog.java 120.4.12010000.8 2016/08/12 17:31:28 rsantis ship $ @6806467 {oracle.apps.fnd.profiles.ExtendedProfileStore@8d0351}],mUniqueId=SVC-GSM-FNDMBLPNTFSVC-416972,mLevel=4}, oracle.jdbc.driver.T4CConnection@1ac978a, 10080, STOPPED_ERROR, Could not handle the control event -> java.lang.NoClassDefFoundError: org/codehaus/jackson/map/JsonMappingException)

            [Jan 23, 2018 1:07:54 PM EST]:1516730874325:-1:-1:nchlarbycm02.red.hat.local:10.177.72.8:-1:-1:1:20420:SYSADMIN(0):-1:Thread[inboundThreadGroup1,5,inboundThreadGroup]:2035383740:77393:1516730874325:6:UNEXPECTED:[SVC-GSM-FNDMBLPNTFSVC-416972-10080 : oracle.apps.fnd.cp.gsc.SvcComponentProcessor.read()]:Queue handler invoker has not been initialized. Outbound agent name is : FND_MBL_NOTIFICATION_OUT

            [Jan 23, 2018 1:07:54 PM EST]:1516730874393:-1:-1:nchlarbycm02.red.hat.local:10.177.72.8:-1:-1:1:20420:SYSADMIN(0):-1:Thread[inboundThreadGroup1,5,inboundThreadGroup]:2035383740:77393:1516730814303:4:UNEXPECTED:[SVC-GSM-FNDMBLPNTFSVC-416972-10080 : oracle.apps.fnd.cp.gsc.SvcComponentProcessor.read()]:Queue handler invoker has not been initialized. Outbound agent name is : FND_MBL_NOTIFICATION_OUT

            [Jan 23, 2018 1:08:34 PM EST]:1516730914270:-1:-1:nchlarbycm02.red.hat.local:10.177.72.8:-1:-1:1:20420:SYSADMIN(0):-1:Thread[ComponentMonitor,5,main]:2035383740:77393:1516730794192:2:EXCEPTION:[SVC-GSM-FNDMBLPNTFSVC-416972 : oracle.apps.fnd.cp.gsc.SvcComponentMonitor.startAutomaticComponents()]:Starting automatic component 10080

            [Jan 23, 2018 1:08:44 PM EST]:1516730924205:-1:-1:nchlarbycm02.red.hat.local:10.177.72.8:-1:-1:1:20420:SYSADMIN(0):-1:Thread[BES Dispatch Thread,5,main]:2035383740:77393:1516730924205:7:EXCEPTION:[SVC-GSM-FNDMBLPNTFSVC-416972 : oracle.apps.fnd.cp.gsc.SvcComponentContainer.onBusinessEvent(BusinessEvent)]:(BusinessEvent{name=oracle.apps.fnd.cp.gsc.SvcComponent.start, key=SVC:23-JAN-2018, priority=50, correlationId=null, sendDate=Tue Jan 23 13:08:34 EST 2018, receiveDate=null, From Agent: , To Agent: , Last Subscription= , Error Message=null, Error Stack=null, CONTAINER_TYPE=GSM, CONTAINER_PROCESS_ID=416972, COMPONENT_ID=10080, BES_PAYLOAD_OBJECT=false, BES_FROM_AGENT=WF_CONTROL@ARBQA.CENTRAL.HQ.INTERNAL})

             

            ==================

            • 3. Re: Oracle EBS "Push Notification" Service Component is failing to start
              mdtaylor

              Have you created a Mobile Cloud Instance and applied the required Mobile Foundation Release 7.0 patches to your EBS Source?

               

              https://docs.oracle.com/cd/E26401_01/doc.122/e64384/T656045T667296.htm#8523435

               

              If your EBS source instance is in the cloud, you may need some additional ports opened to make this connection work.

              • 4. Re: Oracle EBS "Push Notification" Service Component is failing to start
                Subba Rao Bhamidipati

                Yes, we have created MCS instance and setup mobile backend as per documentation .

                Our EBS instance is on-prem, not in cloud and it’s been patched upto Release 7.0.

                 

                are there any other setups we need to do on EBS?

                 

                Thank you for the help on this.

                 

                Thanks,

                Subba

                • 5. Re: Oracle EBS "Push Notification" Service Component is failing to start
                  Vijay Shanmugam-Oracle

                  Validate below in your env.

                   

                  1) Check $APPL_TOP/admin/adjborg2.txt. This file should have entries for

                   

                  $FND_TOP/java/3rdparty/stdalone/jackson_mapper.zip

                  $FND_TOP/java/3rdparty/stdalone/jackson_core.zip

                   

                  2) Verify the two zip files exist in the corresponding folders.

                   

                  3) adjborg2.txt is used to generate appsborg2.zip that should contain the class org/codehaus/jackson/map/JsonMappingException

                   

                  For example,

                  unzip -l $COMMON_TOP/java/lib/appsborg2.zip | grep JsonMappingException

                   

                  appsborg2.zip file is in $AF_CLASSPATH used by MCS Push Service Component.

                   

                  4) If either adjborg2.txt does not have the jackson_*.zip files or if appsborg2.zip does not have class org/codehaus/jackson/map/JsonMappingException, then possibly there are issues with application of

                   

                  Patch 24383252:R12.ATG_PF.B - ATG - 12.1 CONSOLIDATED PATCH FOR MOBILE APPLICATIONS FOUNDATION RELEASE 7

                   

                  You may want to re-apply this patch.

                   

                  If adjborg2.txt has the entries for jackson_*.zip but appsborg2.zip does not have the class, you can use adadmin to force regenerate the appsborg2.zip and check.

                   

                  5) After confirming the class is present in appsborg2.zip, bounce Concurrent Manager and test again.

                  • 6. Re: Oracle EBS "Push Notification" Service Component is failing to start
                    Subba Rao Bhamidipati

                    Thank You so much for the detailed reply with steps.

                    In our case, the issue is happening in multi-node environment, where certain files missing from one node. When our DBA's copied the file to all nodes and bounce the concurrent manager, the issue is resolved.

                     

                    We are now able to see "Running" status for "MCS Push Notification Provider? component in EBS.

                    Thank you all for the help!