MidTier - Error HTTP 404 error accessing when using Tomcat 8.5 or better installed with the Windows installer

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 Mid Tier


    APPLIES TO:

    Tomcat 8.5 or better on a Windows platform



    PROBLEM:

    After installing Midtier against a Windows based Tomcat 8.5, the HTTP 404 error code displays when trying to access the midtier.
    The tomcat/logs/localhost-<current date>.log show errors as follows: 

       
    SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.listenerStart Exception sending context initialized event to listener instance of class [com.remedy.arsys.share.ServiceLocator]     java.lang.RuntimeException: Error while acquiring lock...java.io.FileNotFoundException: D:\Program Files\BMC Software\ARSystem\midtier\cache\cache.lck (Access is denied) Please ensure that only one Midtier is running and you have appropriate permissions and restart Midtier. If this does not solve the problem then please contact BMC support.         at com.remedy.arsys.share.ServiceLocator.contextInitialized(ServiceLocator.java:74)         at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4699)         at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5165)         at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)         at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:743)         at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:719)         at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:705)         at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:614)         at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1823)         at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)         at java.util.concurrent.FutureTask.run(Unknown Source)         at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)         at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)         at java.lang.Thread.run(Unknown Source)
       
      

     


    CAUSE:

    The Windows installer for Tomcat 8.5 or better sets the logon id for the service as Local Service


    SOLUTION:

    The problem occurs because the Tomcat 8.5 or better Windows installer sets the login id for the Tomcat service as Local Service.  This does not have the permissions needed for the midtier application. 
    As of Tomcat 8.5, the Windows installer has this change:
    63310: Update to Commons Daemon 1.2.0. This provides improved support for Java 11. This also changes the user configured by the Windows installer for the Windows service from Local System to the lower privileged Local Service

    Reference:  https://tomcat.apache.org/tomcat-8.5-doc/changelog.html

    To resolve the problem, there are two possible solutions:

    Solution 1.  Update the Tomcat service logon to Local System.

    a.  Open the Windows Services panel
    b.  Rightclick on the Tomcat service and select Properties from the popup menu.
    c.  Go to the Logon tab
    d.  Select Local System and save the changes.
    e.  Restart the Tomcat service

    User-added image

    Solution 2.   Add Local Service to the permissions for the midtier directory.

    a.  In Windows Explorer, go to the AR System installation directory.
    b.  Rightclick on the midtier directory and select Properties
    c.  Go to the Security tab
    d  Click Edit
    e.  Click Add.  
    f.   Click Locations and then select the server name that appears at the top of the tree
    g.  Enter the name "Local Service" in the field labeled: Enter the object names to select
    h.  Click OK
    i.  Give Local Service all BUT Full Control 
    j.  Click Apply and OK to back out of the panels.
    k.  Restart the Tomcat service.

     


    Article Number:

    000182501


    Article Type:

    Solutions to a Product Problem



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