(SM-2511) Java Connector Troubleshooting
This document provides instructions and information on troubleshooting the most common problems related to SNP Kyano Java Connector setup.
Check if the SNP Kyano Java Connector is running
Open transaction /DVD/JCO_MNG.
On the left side of the screen, select the connector version currently in use.
The status of the connector for the specific app.server can be seen on the right side of the screen.
Check Java logs
Open transaction /DVD/JCO_MNG.
On the left side of the screen, select the connector that is being used.
On the right side of the screen, click Logs to display Java logs.
In the selection screen, it is possible to set several parameters:
Java RFC destination: From which JCO logs are read from
Application server: From which application server are logs read from
Number of lines: How many lines are read
Date/Time from: From what timestamp logs are read
Date/Time to: To what timestamp logs are read
Read through JCO: If logs are read using the JCO or directly read by the Application server
Message filters: Which logs, based on their severity, are included.
The table of Java logs is displayed. It is possible to sort logs by each column and also refresh logs using the refresh button in the top left corner of the screen.
Possible issues
If the SNP Kyano Java Connector does not start, these are the possible issues. Even if Java does not start, some information can sometimes be seen in the logs. Click on the Logs button to check logs.
ACLs on the SAP gateway do not allow registration of the SNP Kyano Java Connector | Check ACLs in the SMGW transaction. Make sure that the program ID used in the setup is allowed to register on the gateway. |
RFC and SNP Kyano Java Connector have an incorrect program ID | Check Program ID in the Config tab in /DVD/JCO_MNG. Make sure that the RFC that is connecting to this SNP Kyano Java Connector uses the same program ID. |
RFC user has the wrong role assigned (enabling RFC communication) | Correct user role in transaction PFCG |
RFC user has the wrong user type (not System user) | Correct the user type in transaction SU01 |
RFC user does not exist or is locked | Create/unlock the user in transaction SU01 |
Java runtime environment is not suitable to run JCO | Please refer to the main page regarding the supported Java Runtime |
Wrong settings | Double-check the setup in /DVD/JCO_MNG Config and Dependencies tab |
Install directory doesn't exist | The latest versions of Kyano Storage Management create an installation directory on their own. In case you have an older version (<1903), make sure the directory exists |
Execution of external commands does not work | Execution of external commands is facilitated by the sapxpg utility (in the SAP kernel). To test the execution of sapxpg, run the SM65 analysis tool. |
CPU architecture is not x64 | Make sure to download libsapjco3.so for the relevant architecture and replace it in <installation_dir>/lib. The same is true for Java Runtime. |
None of the above | To get maximum information in the JCO log, set the following additional parameters: -Djco.trace_level=8
Try to manually start the JVM: Oracle Java su - <sid>adm
Example:
IBM Java /usr/bin/java -Xmx2G |