Show TOC

 JSPM Cannot Be StartedLocate this document in the navigation structure

Problem 1: Not Enough Disk Space Is Available

JSPM cannot be started. The following error message is displayed:

class com.sap.sdt.util.diag.DevelopmentSupportRequiredException:
Assertion failed for (handler != null) at com.sap.sdt.util.diag.SDT.check(SDT.java:36)

Possible Reasons

Check if the last /usr/sap/<SID>/<Central instance name>/j2ee/JSPM/trc/JSPM<_xx>.TRC file contains the following error message:

[Error]: com.sap.sdt.tools.var.VariableAdmin [Thread[main,5,main]]:
Unable to load variable handler for /<Name> : Could not load namespace /<Name> from file
<Drive>:\usr\sap\<SID>\<Central instance name>\j2ee\JSPM\data\variables\
<File name>.xml.
org.xml.sax.SAXException has occurred: Fatal Error: com.sap.engine.lib.xml.parser.ParserException:
Document is not well-formed: Start-tag StringValue is different from end-tag VariableHandler

This error message means that the following file is corrupted: /usr/sap/<SID>/<Central instance name>/j2ee/JSPM/data/variables/<File name>.xml .

This can happen if not enough disk space is available to store the file.

Solution

If necessary, free some disk space. For more information, see Requirements for Free Disk Space .

If a file in the /usr/sap/<SID>/<Central instance name>/j2ee/JSPM/data/variables directory is corrupted or is empty (size is 0), and if:

  • The file name contains MetaData , delete it and try to start JSPM again.
  • The file name does not contain MetaData , redeploy JSPM using SDM.

Problem 2: GUIConnection Port Is in Use

JSPM cannot be started. The following error message is displayed:

Could not start JSPM. GUI connection port 6240 on localhost is already in use.
Turn off the application which uses this port or change the
/dialog/SDTServerConnection/port property in the
<Drive>:\usr\sap\<SID>\<Central instance name>\j2ee\JSPM\param\
jspm_config.txt file.

Possible Reasons

Either another application or another running instance of JSPM is using the GUI connection port 6240.

Solution

If another running instance of JSPM is using port 6240, use this instance or stop it.

If another application is using port 6240, in the /usr/sap/<SID>/<Central instance name>/j2ee/JSPM/param/jspm_config.txt file, change the value of the /dialog/SDTServerConnection/port property by specifying a port that is currently not in use and try to start JSPM.

Problem 3: JSPM Hangs On During Logon

JSPM hangs on during logon. The log files contain the following message:

Checking connectivity for SDM server on host <J2EE_Engine_Host>, port <SDM_Port>
SDM server version is <xxx>, SDM client version is <xxx>

Possible Reasons

SDM with a version lower than SAP NetWeaver 7.0 SPS04, hangs on when closing the connection to the SDM server if the /usr/sap/<SID>/<Central instance name>/SDM/program/temp directory does not exist. JSPM waits for a response and hangs on too.

Solution

Stop JSPM. Create the /usr/sap/<SID>/<Central instance name>/SDM/program/temp directory and try to start JSPM.