Troubleshooting

If errors occur while you are working with JSPM, we recommend that you view the log files. More information: Viewing Log Files The following sections describe the solutions to the most common errors that may occur while you are working with JSPM:
• • • • •

Viewing Log Files JSPM Cannot Be Started JSPM Does Not Display Packages from Inbox Directory Error at the Check Queue Wizard Step Error During Deployment

Viewing Log Files

You can view logs that are generated by JSPM. You can also view logs generated by other applications that are integrated with JSPM. If JSPM is started, you can view logs using the integrated Log Viewer in the JSPM. You can also view .LOG files with any text viewer or editor. By default, all logs that are generated by the JSPM are stored in the /usr/sap/<SID>/<Instance name>/j2ee/JSPM/log directory. You can view logs both from the current logon session and from previous sessions. Logs from every session are written to a subdirectory whose name contains the time stamp of the session. The following table describes the most important log files and their content: Log File JSPM_MAIN.LOG Contains Information About Main JSPM processes. It may contain references to other log files that are generated by the JSPM or by other

EXCHANGE_KERNEL_BINARIES. A severity level denotes the level of importance of a given record.LOG IGS update. • ERROR Logs with this severity are generated when the application can recover from an error but cannot perform a required operation due to the error. • FATAL . ENGINE_OPERATION.LOG Starting and stopping of the system. The system parameters that JSPM has DETECT_SYSTEM_PARAMETERS.LOG inbox directory. You can view list formatted logs with different severity levels. • WARNING Logs with this severity are generated when the application can recover from an anomaly and perform a required operation. EXCHANGE_IGS_BINARIES. you can view OUT and ERR files. for example.LOG Kernel update. which are standard output and error streams from external processes. • PATH Logs with this severity contain information that is relevant to tracing the execution flow. • INFO Logs with this severity contain information about what has been performed.LOG that JSPM has detected. In addition to LOG files. The following are the possible severity levels with an increasing severity: • Log File DEBUG Logs with this severity contain extensive and low level information that is relevant to debugging.Contains Information About integrated applications. The scan of the content of the global EPS SCAN_INBOX. but attention from a user is required. entering and leaving a method.LOG detected during startup. The components deployed on the system DETECT_SYSTEM_COMPONENTS.

Current Log In the navigation area on the left. Procedure Viewing Logs Using the Integrated Log Viewer in the JSPM To view log files.sdt. The following error message is displayed: class com.java:36) Possible Reasons Check if the last /usr/sap/<SID>/<application server instance name>/j2ee/JSPM/trc/JSPM<_xx>. browse Log Files Files and select the log file you want to view.TRC file contains the following error message: . Choose Find.util. If You Want To View a log from the current logon session View a log from a previous logon session Then In the navigation area on the left.sap.sap. browse Log Files Old Log Files and from the subdirectory whose name contains the time stamp of the session you want to view.util.diag. Enter the string you want to search for.DevelopmentSupportRequiredException: Assertion failed for (handler != null) at com. 3.sdt.SDT. Choose the button with quick info text Find 2.diag. select the log file you want to view. JSPM Cannot Be Started Problem 1: Not Enough Disk Space Is Available JSPM cannot be started. Searching in the Log Files To search for a string in the complete message text of a non list formatted log file: 1.Logs with this severity are generated when the application cannot recover from an error and the severe situation causes fatal termination. choose the Logs tab.check(SDT.

xml.main]]: Unable to load variable handler for /<Name> : Could not load namespace /<Name> from file <Drive>:\usr\sap\<SID>\<Instance name>\j2ee\JSPM\data\variables\ <File name>.xml.sax. and if: ● The file name contains MetaData. This can happen if not enough disk space is available to store the file. Turn off the application. Solution If necessary. redeploy JSPM.lib.xml.[Error]: com. For more information.xml.engine.sdt. .SAXException has occurred: Fatal Error: com.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>/< application server instance name>/j2ee/JSPM/data/variables/<File name>. org. GUI connection port 50017 on localhost is already in use. If a file in the /usr/sap/<SID>/< application server instance name>/j2ee/JSPM/data/variables directory is corrupted or is empty (size is 0).sap. which uses this port or change the /dialog/SDTServerConnection/port property in the <Drive>:\usr\sap\<SID>\<Instance name>\j2ee\JSPM\param\ jspm_config. ● The file name does not contain MetaData.var.sap.txt file.tools. free some disk space.VariableAdmin [Thread[main.parser. see Requirements for Free Disk Space.5. Problem 2: GUI Connection Port Is in Use JSPM cannot be started. The following error message is displayed: Could not start JSPM. delete it and try to start JSPM again.

Possible Reasons Either another application or another running instance of JSPM is using the GUI connection port 5xx17. Possible Reasons At the moment JSPM was triggered by the go script another application had been using the port so the SDT server did not start and JSPM failed. For example 50118 if instanceID = 01. The initialization of JSPM in brief goes this way: . Could not bind to port 5XX18.log file. where xx is the instance ID number. If another application is using port 5xx17.BindException: Address already in use Default port is tcp/5xx18.txt file. java. There is also an error logged within the /usr/sap/<SID>/<InstanceID>/j2ee/JSPM/log/slcontroller/server.net. . where xx is the instance number.. Problem 3: JSPM Fails to Start as a Stand-Alone Tool on Business ByDesign System Connection failed to <host>:<port_number> when you started JSPM as a stand-alone tool on a Business ByDesign system. use this instance or stop it. Solution If another running instance of JSPM is using port 5xx17. change the value of the /dialog/SDTServerConnection/port property by specifying a port that is currently not in use and try to start JSPM. in the /usr/sap/<SID>/<Instance name>/j2ee/JSPM/param/jspm_config. Ports 5xx19. 5xx18 and 5xx17 (where xx is the instance ID number) should be free..

Solution 1 Free ports 5xx19. SDT Server starts SDT GUI that populates JSPM GUI If one of the previous steps fails. 1.. 5xx18. Solution 2 Change the ports with free TCP ports as follows: . JSPM starts 2.xml (/usr/sap/<SID>/<InstanceID>/j2ee/JSPM/server directory) edit the entry ServerPort value with new SDT_server_port_value. SDT Server is started 3.xml (/usr/sap/<SID>/<InstanceID>/j2ee/JSPM/server directory) edit the entry HTTPPort value with new SDT_server_HTTP_port_value. JSPM will not come up with a GUI.1. In sdtserver. In jspm_config. as shown in the following example: <HTTPSettings> <HTTPMode>on</HTTPMode> <HTTPPort>SDT_server_HTTP_port_value</HTTPPort> 3. In sdtserver. as shown in the following example: <ServerSettings> <ServerPort>SDT_server_port_value</ServerPort> 2..txt (/usr/sap/<SID>/<InstanceID>/j2ee/JSPM/param directory) set JSPM_port. and 5xx17. as shown in the following example: . where xx is the instance ID number.

xml file with the value set at step 3.xml. The behavior is due to the fact JSPM in such scenario (stand-alone tool) uses localhost by default to connect to SDT.xml (/usr/sap/<SID>/<InstanceID>/j2ee/JSPM/server directory) edit the entry ToolPort value with new JSPM_port. Change ToolPort parameter in JSPM. In JSPM./dialog/SDTServerConnection/port = JSPM_port 4.if the physical hostnames are not accessible the tool will fail to initialize. Possible Reasons JSPM is not intended to be used as a stand-alone tool within a Business ByDesing scenario. This workaround uses ports which are non-privileged and are not reserved. In case you need to use the tool as a stand-alone application on a Business ByDesign system with clustering you may encounter the symptoms mentioned above.net. Problem 4: JSPM Fails to Initialize on a Clustered Business ByDesign System When JSPM tool is started as a stand alone tool on a clustered Business ByDesign system (more than one physical host behind virtual hostname) you get an error within the GUI: java. At a later time the same ports might not work and they have to be changed once again. The tests of the tool are performed regarding the Live Update so in such cases the tool should be stable. <ToolPort> JSPM_port </ToolPort> After checking for free TCP ports and performing the steps above the JSPM GUI should be able to start.NoRouteToHostException No route to host <hostname>. The issue is related to improper host to IP resolution of the physical hostnames . . Solution To fix the issue you need to alter some configuration within jspm.

sap. Restart JSPM tool. When asked for <host>/<port>.. For more information about SAP products. Change the value from 'localhost' to the virtual hostname used by the cluster. enter the virtual hostname and SDT server port (default one 5<instance numer>18).LOG files.LOG and SCAN_INBOX_<xx>. Possible Reasons The packages are: ● Not valid or have not been downloaded successfully • • • • With a lower or equal support package level For an older release For a software component that is not currently deployed on the system. . 3.com/swdc. JSPM Does Not Display Packages from Inbox Directory Problem JSPM does not display the packages that you have placed in the global EPS inbox directory.xml file. see the last JSPM_MAIN_<xx>. ● Download only packages with a higher support package level. Open it for edit. 4. Download the packages again. For NWDI development and contain no deployable content Solution ● For more information about the validity of the files which JSPM has detected in the global EPS inbox directory. Into the <ToolSettings> section locate <ToolHost> parameter. see SAP Service Marketplace at service... 1. 2. Under /usr/sap/<SID>/< application server instance>/j2ee/JSPM/server locate jspm.

a component has status REVISE and the following error message is displayed: Archive not found in Inbox directory. JSPM does not detect the renamed or removed file and you can go on. .SCA. at the Check Queue wizard step. ● Deploy the software component (see Deploying New Software Components). place it in the global EPS inbox directory and go back to the Specify Queue wizard step.You can check the support package level of the components that are deployed on the system (see Viewing the Deployed Components). You can check the support package level of the packages that are downloaded in the global EPS inbox directory. Problem 2 JSPM shuts down at the Check Queue wizard step. The name of each package has the following syntax: <Name_xx_x>. Solution If you have accidentally renamed or removed a file. ● Download only packages for the current release level. go back to the Select Package Type wizard step. where xx is the support package level and x is the patch level. If you have intentionally renamed or removed a file. Possible Reasons JSPM has detected the required files at the Specify Queue wizard step and afterwards you have renamed some of them or removed some of them from the global EPS inbox directory. JSPM detects the file and you can go on. Error at the Check Queue Wizard Step Problem 1 During a support package stack or support package deployment.

set the heap size and permanent space Java parameters as described in SAP Note 723909. and restart JSPM as described in SAP Note 874123. Such an exception occurs if not enough AS Java memory is available.LOG file of the current logon session. There is no sufficient JVM memory for saving JSPM internal data in the XML files.OutOfMemoryError: <null> Possible Reasons It is possible that some of the temporary XML files.sdt. Solution On all operating systems – using the Config Tool. delete the corrupted XML files. Possible Reasons Check if the /usr/sap/<SID>/<application server instance name>/j2ee/cluster/<Server process>/log/defaultTrace. .doExecute(AbstractPhaseType. Error During Deployment Problem 1: Out of Memory JSPM cannot deploy all components.sap. you can find the following error: com.phases. The deployment of at least one of the components that you selected has finished either with status DEPLOYED WITH ERROR or with status NOT DEPLOYED.trc file contains an OutOfMemory exception. are not valid.In the JSPM_MAIN_<XXX>. Solution Increase JSPM JVM memory settings.AbstractPhaseType.java:751): Error java. whose name contains DataModel.ucp.<xx>. On Linux on AMD64/EM64T Linux – set the Java parameters as described in SAP Note 861215.lang. and which are located in the /usr/sap/<SID>/<application server instance name>/j2ee/JSPM/data/variables directory.

General Database Parameters and For more information about changing database parameters see Parameters. see SAP Note 764417. and Problem 2: JSPM Hangs On During Deployment JSPM hangs on during deployment.On Microsoft Windows – get the SAP Address Space Viewer and rebase the DLLs as described in SAP Note 129813 and SAP Note 736462. Menus. For more information about setting the Java parameters. Possible Reason 1 If your database is MaxDB. Changing Database . For more information about MAXUSERTASKS see SAP Note 757914. Solution 2 If your database is MaxDB. For more information about troubleshooting the AS Java. the parameter MAXUSERTASKS may have insufficient value. see Changing Log Settings Possible Reason 2 If your database is MaxDB. we recommend that you set the overwrite mode for the log area. Layout. the deployment may continue longer than expected (the maximum expected deployment time is about 3 hours). For more information. Solution 1 If your database is MaxDB. the logs may be full. If your database is MaxDB. see Features of the Config Tool. we recommend that you set the parameter MAXUSERTASKS to at least 50.