Troubleshooting

A couple of things may go wrong when the application server tries to deploy the applications:

• Tomcat/JBoss doesn’t start properly – This means there is a configuration problem.
  • For JBoss, check the standalone.conf.bat, standalone.xml and all module.xml files for the updated libraries.
  • For Tomcat open the Tomcat configuration manager and check the Java Options.

• Look for non UTF-8 characters, new lines, typos
• Verify that the referenced paths are correct and that they are using backward slashes (“\”).
• Make sure you don’t have extra spaces in the file paths.
• Check the JVM arguments. Make sure that the heap settings are correct

• Tomcat/JBoss starts, but the deployments of the applications fail with no clear explanation in the logs – This is probably an permissions related issue.
  • Make sure that the Tomcat/JBoss process has RWLX rights to the its configuration folder and the “deployments” directory
  • Make sure that Tomcat/JBoss have RWL rights to the Match configuration folders
  • Check that the application .war files are not encrypted. In Explorer, encrypted files appear in green color. The files may become encrypted if they are downloaded from the web (via Internet Explorer).
• Tomcat/JBoss starts, the applications are deployed, but the application(s) are not accessible- This could mean a couple of things:
  • You are using an incorrect URL
  • You are trying to access the applications from localhost, but you have configured an IP address to be used
  • Incomplete/incorrect configuration of the application(s)
    • In this case an exception message will be logged and can be seen in the log, mwp.log, msm.log, mjobs.log. Most likely the error is configuration related and can be easily fixed by double checking the configuration files of the applications and updating them accordingly.

When troubleshooting it’s always best to view the logs and to try to determine what is the cause for the failure.

JBoss tips

When troubleshooting or configuring the applications, it’s always best to be able to start/stop JBoss fast (without having to wait for the JBoss service to stop). There are two different ways of starting JBoss:

• As a Service
• Standalone

Starting JBoss as a Service

Instructions:

1. Open services
2. Select the JBoss service and click on the Action Menu “start”

Starting JBoss in standalone mode

1. Go to the “bin” folder inside your JBoss installation ($JBOSS_HOME\bin)
2. Run the “standalone.bat”

During the troubleshooting/installation time, we highly recommend starting JBoss in “standalone mode” until you are sure that everything is running properly. Once everything is well configured, start JBoss as a service.

If you have followed the previous steps, you should be able to start JBoss successfully.