AtriumCore java processes information on how to restart a java plugin server without restarting ARServer.

Version 2
    Share This:

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


    PRODUCT:

    BMC Atrium CMDB Suite


    APPLIES TO:

    BMC Atrium CMDB Suite



    PROBLEM:

     

    Good to know info: 
      

    AR Java and CMDB Plugins do not require ARS Server restart to reload settings or to fix connectivity issues.
    All you need to do is to identify the relevant JAVA process and "kill" it. ARMONITOR will pick it right up and resume activity for that plugin. This takes a split second rather than the 3-10 minute restart of ARS.
    This also allows for "on the fly" changes to the java plugin configurations. Next version of ARS 8.0 will also offer a "driver" signal command to reload the ARDBC (ar.cfg) configuration.

      

     

     


    SOLUTION:

     

    Legacy ID:KA402816

      
    How to tell what java process is which?
      

     This is a fairly easy question to answer for Windows and UNIX. The secret is in the CLASSPATH.
     

      

    Each java process has a classpath which includes a fairly good clue on what plugin server it has started. You just have to know how to look for it.
    Here is how: 

      
    Windows: 
      

    1. Open Windows Task Manager > Processes (tab) .

      

    2. Click View > Select Column

      

    3. Put a check in "Command Line" and click OK.

      

    4. Stretch the "Command Line" column to max width or at least until you can see the full command line.

      

    5. Check the "Show processes from all users" 

      

    6. Sort by image name and find the "java.exe" process.

      

    7. Now look into the path and find the Java process that has CLASSPATH to arpluginsvr where the first path leads to location directory of the pluginsvr_config.xml file.

      

    8. Norm will have "ne", Shared plugins will have "shared", FTS will have "fts" and AR Java Plugin will have "pluginsvr". Right click on that java.exe and "End" that process.

      
    UNIX/Linux
      

    1. run this command as root or the user that started ARS Server: 
     

      

    ps -auxwww | grep java | grep arpluginsvr     (if this does not work run this instead) : ps -ef | grep java | grep arpluginsvr

      

    Solaris SunOs 5.10 you may need to use this instead: "/usr/ucb/ps -auxwww | grep java | grep arpluginsvr"

    2. You should see 3 or more results. Look for the CLASSPATH list of paths after it.

      

    3. You should now recognize the locations of each pluginsvr_config.xml files as the first path in the classpath.

      

    4. For Normalization you'll see a path that ends with "ne", for Shared Atrium Plugins you'll see a path with "shared", for ARS Java Plugin you'll see "pluginsvr".
    There maybe another one for Full Text Search (fts). There should be no need to restart that one.

      

    5. Identify the first number of that line. That should be the PID (Process ID) and it should match the last one loaded by armonitor process (aslo captured in the armonitor.log). This is the PID you need to "kill".

      

    6. Type this at the command prompt: 

      

    kill -9 <PID>

      

    where the PID is the number you found in step 5.

      

    7. That's it. ARMONITOR will immediately identify the killed process and load it back into memory. This will include new settings from the pluginsvr_config.xml, but not the ar.conf.

      

     NOTE: ARRECOND, ARCMDBD and AIE are not Java processes, but can be identified and restarted in similar fashion as the java processes. Both will manage getting their metadata (dynamic configuration settings managed within the ARS Server realm) once armonitor loads them back in. One advantage of the Java plugin is that the configuration updates in the pluginsvr_config.xml and log4j_config.xml will also be refreshed when the process is restarted this way.

     


    Article Number:

    000091732


    Article Type:

    Solutions to a Product Problem



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