Remedy service takes long time to start

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Remedy AR System Server


    COMPONENT:

    AR System Server


    APPLIES TO:

    This specifically observed in Remedy environment 9.1 Sp4 in patch 1 and Patch2



    PROBLEM:

    During a remedy service startup we see below error in arerror , armonitor , ardebug log
     

                         
    Tue Jul 24 15:15:43.173 2018 Application context refresh failed (OsgiBundleXmlApplicationContext(bundle=com.bmc.cmdb.rest, config=OSGI-INF/blueprint/application-context.xml))Tue Jul 24 15:15:43.175 2018 Unable to create application context for [com.bmc.cmdb.rest], unsatisfied dependencies: Dependency on [(objectClass=com.bmc.cmdb.services.dataset.DatasetService)] (from bean [&datasetService]), Dependency on [(objectClass=com.bmc.cmdb.services.graph.GraphWalkService)]  (from bean [&graphWalkService]), Dependency on [(objectClass=com.bmc.cmdb.services.classes.ClassService)] (from bean [&classService]), Dependency on [(objectClass=com.bmc.cmdb.services.commonservices.CommonService)] (from bean [&commonJobsService]), Dependency on [(objectClass=com.bmc.cmdb.services.version.VersionService)]  (from bean [&versionService]), Dependency on [(objectClass=com.bmc.cmdb.services.ai.AIJobService)] (from bean [&aiJobsService]), Dependency on [(objectClass=com.bmc.cmdb.services.instance.InstanceService)] (from bean [&instanceService]), Dependency on [(objectClass=com.bmc.cmdb.services.dashboardconfig.DashboardConfigService)]  (from bean [&dashboardConfigService]), Dependency on [(objectClass=com.bmc.cmdb.services.ne.NERuleService)] (from bean [&neRuleService]), Dependency on [(objectClass=com.bmc.cmdb.services.noe.NOEService)] (from bean [&noeService]), Dependency on [(objectClass=com.bmc.cmdb.services.config.ConfigurationSettingsService)]  (from bean [&configurationSettingsService]), Dependency on [(objectClass=com.bmc.cmdb.services.ai.JobSchedulingService)] (from bean [&jobSchedulingService]), Dependency on [(objectClass=com.bmc.cmdb.services.dataflow.DataFlowService)] (from bean [&dataFlowService]), Dependency on [(objectClass=com.bmc.cmdb.services.commonservices.CommonService)]  (from bean [&commonService]), Dependency on [(objectClass=com.bmc.cmdb.services.health.HealthService)] (from bean [&healthService]), Dependency on [(objectClass=com.bmc.cmdb.services.ne.NEJobService)] (from bean [&neJobService]), Dependency on [(objectClass=com.bmc.cmdb.services.common.logger.Logger)]  (from bean [&logger]), Dependency on [(objectClass=com.bmc.cmdb.services.re.REJobService)]  (from bean [&reJobsService]), Dependency on [(objectClass=com.bmc.cmdb.services.attributes.AttributeService)] (from bean [&attributeService]), Dependency on [(objectClass=com.bmc.cmdb.services.ne.NEUtilityService)] (from bean [&neUtilityService]), Dependency on [(objectClass=com.bmc.cmdb.services.datasources.DataSourceService)]  (from bean [&dataSourceService]), Dependency on [(objectClass=com.bmc.cmdb.services.query.QueryByPathService)]  (from bean [&queryByPathService]) Tue Jul 24 15:15:43.236 2018 Application context refresh failed (OsgiBundleXmlApplicationContext(bundle=com.bmc.cmdb.services, config=OSGI-INF/blueprint/application-context.xml)) Tue Jul 24 15:15:43.237 2018 Unable to create application context for [com.bmc.cmdb.services], unsatisfied dependencies: Dependency on [(objectClass=com.bmc.cmdb.server.internal.services.v1.Api)] (from bean [&cmdbApi])
      
    In armonitor.log
                            
    <MNTR> <TNAME: Thread-3                 > <INFO > <ProcessMonitor$1                   > <      ProcessMonitor.java:293       > /* Tue Jul 24 18 16:37:27.0256  */ Tue Jul 24 16:37:26.904 2018 Loading the AR Server configuration..success <MNTR> <TNAME: Thread-3                 > <INFO > <ProcessMonitor$1                   > <      ProcessMonitor.java:293       > /* Tue Jul 24 18 16:37:27.0417  */ Tue Jul 24 16:37:27.417 2018 This server is running in normal mode. <MNTR> <TNAME: Thread-3                 > <INFO > <ProcessMonitor$1                   > <      ProcessMonitor.java:293       > /* Tue Jul 24 18 16:56:50.0650  */ Tue Jul 24 16:56:50.642 2018 Application context refresh failed (OsgiBundleXmlApplicationContext(bundle=com.bmc.cmdb, config=OSGI-INF/blueprint/application-context.xml))<MNTR> <TNAME: Thread-3                 > <INFO > <ProcessMonitor$1                   > <      ProcessMonitor.java:293       > /* Tue Jul 24 18 16:56:50.0652  */ org.springframework.context.ApplicationContextException: Application context initialization for 'com.bmc.cmdb' has timed out waiting for (|(objectClass=com.bmc.arsys.services.v1.platform.Api)(objectClass=com.bmc.arsys.services.v1.platform.XmlApi)(objectClass=com.bmc.arsys.services.v1.platform.Workflow)(objectClass=com.bmc.arsys.services.v1.platform.Log)(objectClass=com.bmc.arsys.services.v1.platform.PropertyEncoderDecoder)(objectClass=com.bmc.arsys.services.v1.platform.Evaluator)(objectClass=com.bmc.arsys.services.v1.platform.PostUpgradeActivity)) <MNTR> <TNAME: Thread-3                 > <INFO > <ProcessMonitor$1                   > <      ProcessMonitor.java:293       > /* Tue Jul 24 18 16:56:50.0652  */     at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489) [bundlefile:2.0.0] <MNTR> <TNAME: Thread-3                 > <INFO > <ProcessMonitor$1                   > <      ProcessMonitor.java:293       > /* Tue Jul 24 18 16:56:50.0653  */     at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54) [bundlefile:2.0.0] <MNTR> <TNAME: Thread-3                 > <INFO > <ProcessMonitor$1                   > <      ProcessMonitor.java:293       > /* Tue Jul 24 18 16:56:50.0653  */     at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109) [bundlefile:2.0.0] <MNTR> <TNAME: Thread-3                 > <INFO > <ProcessMonitor$1                   > <      ProcessMonitor.java:293       > /* Tue Jul 24 18 16:56:50.0654  */     at java.util.TimerThread.mainLoop(Timer.java:555) [na:1.8.0_171] <MNTR> <TNAME: Thread-3                 > <INFO > <ProcessMonitor$1                   > <      ProcessMonitor.java:293       > /* Tue Jul 24 18 16:56:50.0654  */     at java.util.TimerThread.run(Timer.java:505) [na:1.8.0_171] <MNTR> <TNAME: Thread-3                 > <INFO > <ProcessMonitor$1                   > <      ProcessMonitor.java:293       > /* Tue Jul 24 18 16:56:50.0655  */ Tue Jul 24 16:56:50.651 2018 Unable to create application context for [com.bmc.cmdb], unsatisfied dependencies: Dependency on [(objectClass=com.bmc.arsys.services.v1.platform.Evaluator)] (from bean [&evaluator]), Dependency on [(objectClass=com.bmc.arsys.services.v1.platform.XmlApi)] (from bean [&xmlApi]), Dependency on [(objectClass=com.bmc.arsys.services.v1.platform.Api)] (from bean [&api]), Dependency on [(objectClass=com.bmc.arsys.services.v1.platform.PropertyEncoderDecoder)] (from bean [&PropertyEncoderDecoder]), Dependency on [(objectClass=com.bmc.arsys.services.v1.platform.PostUpgradeActivity)] (from bean [&postUpgradeActivity]), Dependency on [(objectClass=com.bmc.arsys.services.v1.platform.Workflow)] (from bean [&workflow]), Dependency on [(objectClass=com.bmc.arsys.services.v1.platform.Log)] (from bean [&log]) <MNTR> <TNAME: Thread-3                 > <INFO > <ProcessMonitor$1                   > <      ProcessMonitor.java:293       > /* Tue Jul 24 18 16:56:50.0655  */ org.springframework.context.ApplicationContextException: Application context initialization for 'com.bmc.cmdb' has timed out waiting for (|(objectClass=com.bmc.arsys.services.v1.platform.Api)(objectClass=com.bmc.arsys.services.v1.platform.XmlApi)(objectClass=com.bmc.arsys.services.v1.platform.Workflow)(objectClass=com.bmc.arsys.services.v1.platform.Log)(objectClass=com.bmc.arsys.services.v1.platform.PropertyEncoderDecoder)(objectClass=com.bmc.arsys.services.v1.platform.Evaluator)(objectClass=com.bmc.arsys.services.v1.platform.PostUpgradeActivity)) <MNTR> <TNAME: Thread-3                 > <INFO > <ProcessMonitor$1                   > <      ProcessMonitor.java:293       > /* Tue Jul 24 18 16:56:50.0656  */     at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489) [bundlefile:2.0.0] <MNTR> <TNAME: Thread-3                 > <INFO > <ProcessMonitor$1                   > <      ProcessMonitor.java:293       > /* Tue Jul 24 18 16:56:50.0656  */     at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54) [bundlefile:2.0.0] <MNTR> <TNAME: Thread-3                 > <INFO > <ProcessMonitor$1                   > <      ProcessMonitor.java:293       > /* Tue Jul 24 18 16:56:50.0657  */     at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109) [bundlefile:2.0.0] <MNTR> <TNAME: Thread-3                 > <INFO > <ProcessMonitor$1                   > <      ProcessMonitor.java:293       > /* Tue Jul 24 18 16:56:50.0657  */     at java.util.TimerThread.mainLoop(Timer.java:555) [na:1.8.0_171] <MNTR> <TNAME: Thread-3                 > <INFO > <ProcessMonitor$1                   > <      ProcessMonitor.java:293       > /* Tue Jul 24 18 16:56:50.0658  */     at java.util.TimerThread.run(Timer.java:505) [na:1.8.0_171]
      
      

     


    CAUSE:

    This is due to bad cache in bundle-cache directory


    SOLUTION:

     

    As a solution after checking with R&D team they confirmed that there seems some corruption in bundle-Cache directory.

    During startup Remedy service tries to load this corrupted directory which causes this delay or no startup of remedy service.

    Recommend clearing the bundle-cache directory contents

    Location of bundle-cache:

      
       
    • (windows) C:\Program Files\BMC Software\ARSystem\bundle-cache
    •  
    • (linux) /opt/bmc/ARSystem/bundle-cache
       
       
    1. navigate to the bundle-cache folder location
    2.  
    3. delete the contents of this folder (DO NOT DELETE THE FOLDER ITSELF)
    4.  
    5. restart AR Server
       




     

     


    Article Number:

    000156212


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles