This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
Remedy AR System Server
AR System Mid Tier
Midtier file deployer and Java 1.8.0_231
When trying to deploy a patch or hotfix using Midtier file deployer, after running the script arpayloaddeploymentutil.bat nothing happens.
If you enable armonitor logs in debug and try again you will see the following.
*/ Executing external process stop-command net stop "Tomcat8"
*/ Unable to execute command Process[BMC:MidtierWebServer] Command[net stop "Tomcat8"]
*/ Command result :
The service name is invalid.
More help is available by typing NET HELPMSG 2185.
However if you manually run net stop "Tomcat8" over the command window, Tomcat will stop successfully.
*Note: This will impact any tomcat version not only tomcat 8 used in this article
It seems that even if File deployer sends the command ok, Java will not send it correctly to the OS If you log the Windows process monitor you will see that the OS will get the command as Command line: "net stop \"Tomcat8.5.47\"" (notice extra slashes)
This seems to be an issue on how Java 1.8.0_231 sends the command that receives from the File Deployer to Windows Server.
This has been identified as defect ID SW00563830
For the moment the workaround would be to downgrade java or install a separate java version lower to 1.8.0_231 and set the file deployer to use this one, the rest of your midtier can still use java 1.8.0_231.
To do this:
- Install the older java in a different path like C:\Java8_221
- open arminitor.cfg located at <midtier_home>\filedeployer\conf
- Change line number 2 to find the older java, for example
- "C:\Program Files\Java\jre1.8.0_221\bin\java" -classpath..... (line truncated) to "C:\Java8_221\bin\java" - classpath..... (line truncated)
- Restart BMC Midtier file deployer service and try again