How to resolve java dispatcher startup issues?

This article answers following queries:

How to resolve java dispatcher startup issues?

What checks need to be done if java dispatcher doesn’t start during java startup?

What action need to be performed to fix java dispatcher startup issues?

-----------------------------------------------------------------------------------------

If java dispatcher doesn’t start during java startup, please check the std_dispatcher log from java work directory. It means, go to /usr/sap/<SID>/<instance>/work directory and look out for error messages. If you find below error message, this could be due to conflict between values maintained for thread mananger.

Loading: ThreadManager returned false! Kernel not loaded. System halted.

To resolve this issue, please proceed as follows:

•  Please login to config tool
•  Navigate to config tool -> dispatcher -> managers -> threadmanager
•  Please verify the values maintained for MinThreadCount, InitialThreadCount   and  MaxThreadCount.
•  Please make sure that MinThreadCount value <= InitialThreadCount <=    MaxThreadCount
•  If you are not sure about the values to be set, please maintain default values and check if dispatcher starts

If issue, didn’t get resolved even after performing above steps, please perform below mentioned additional tasks and retry to start the system

• In Config tool, navigate to Cluster-data --> Instance_IDxx --> dispatcher_IDxx --> managers --> ConfigurationManager
• In the local properties section, please make sure sqljdbc.jar exists for rdbms.driverLocation