Default language.

Troubleshooting the AR System server issues when the bundle cache related error occurs

The  might not start successfully if there are issues with the bundle cache. 

Use this information to obtain appropriate logging information and troubleshooting steps to resolve any issue with the bundle cache.

Alternatively, you can create a case with BMC Support.

Related topic

Support-information


Watch the following video (3:33) to understand about deleting  bundle cache:


Symptom

The  does not start and you can see a bundle error in the arerror.log file.


Scope

  • One or more servers in the server group does not start.
  • The AR Server process is affected.


Resolution

Perform the following steps to troubleshoot the issue:

Step

Action

Description

1

Collect  logs.

For the server experiencing an error, collect logs from the following files:

  • arerror.log
  • armonitor.log
  • ardebug.log


2

Review the armonitor.log file.

In the armonitor.log file, check the references of a bundle error as shown in the example below:

Application context refresh failed (OsgiBundleXmlApplicationContext
(bundle=com.bmc.arsys.server

or

Unable to create application
context for [com.bmc.arsys.server],
unsatisfied dependencies: none

Use the table to analyze the specific errors. 


3

Review the arerror.log file.

In the arerror.log file, check the occurrence of a bundle error. See the example below:

Error encountered in bundle: com.bmc.arsys.server

or

Application context
refresh failed
(OsgiBundleXmlApplicationContext
(bundle=com.bmc.arsys.server

Use the table to analyze the specific errors. 


4

Review the ardebug.log file.

In the ardebug.log file, check Bean errors related to Spring Framework. See the example below:

org.springframework.beans.
factory.BeanCreationNotAllowedException

Use the table to analyze the specific errors. 


5

Determine a solution.

  • Use the table to analyze the specific errors and troubleshoot the issues.

  • If you cannot identify the cause, collect the logs and raise a case with BMC Support.

6

Collect relevant logs.

  • Run the Log ZipperLog zipper utility and collect logs. You must run the Log Zipper utility on each server that causes the issue.

  • Rename the zipped file to include the server name.


7

Analyze logs.

Review the logs and identify error messages or behavior. Also, use the  table to analyze possible symptoms and solutions.


8

Create a Support Ticket.

Collect and send the following information when you create a case with BMC Support:

  • User(s) that experienced the problem (if not all users)
  • Approximate timestamp when the problem was observed
  • What happened prior to the startup issue? 
  • Reason for the server restart.
  • Any recent changes to the application, database, or other components of your environment.

Attach the Log Zipper zip file up to 2 GB or share the file over FTP with BMC Support.

For more information, see the knowledge article on BMC communities SFT - Steps to send logs, files, screenshots, etc to BMC Support for a Product related case.



After you determine a specific symptom or error message, use the following table to identify the solution:


Symptom

Where

Action

Reference

The bundleplan.properties file is missing

File System

Copy the file from the server.


Application context refresh failed (OsgiBundleXmlApplicationContext
(bundle=com.bmc.arsys.server

armonitor.log

Perform the following steps:

  1. Access the bundle-cache folder, located under  \BMC Software\ARSystem.
  2. Delete all the files from the bundle-cache folder.
  3. Restart the .

Unable to create application context for
[com.bmc.arsys.server], 
unsatisfied dependencies: none

armonitor.log

Perform the following steps:

  1. Access the bundle-cache folder, located under  \BMC Software\ARSystem.
  2. Delete all the files from the bundle-cache folder.
  3. Restart the .

Application context refresh failed
(OsgiBundleXmlApplicationContext
(bundle=com.bmc.arsys.server, 

arerror.log

Perform the following steps:

  1. Access the bundle-cache folder, located under  \BMC Software\ARSystem.
  2. Delete all the files from the bundle-cache folder.
  3. Restart the .

ardebug.log

Perform the following steps:

  1. Access the bundle-cache folder, located under  \BMC Software\ARSystem.
  2. Delete all the files from the bundle-cache folder.
  3. Restart the .


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*