(SM-2202) Java Connector Troubleshooting
- SNP
This document provides instructions and information on how to troubleshoot the most common problems related to Java connector setup.
Check if the Java connector is running
Open transaction /DVD/JCO_MNG
On the left side of the screen, select the connector that is being used. Usually, the Java connector is connected using DATAVARD_JAVA_CONN RFC.
The status of the connector for the specific app.server can be seen on the right side of the screen.
Click the restart button
Check Java logs
Open transaction /DVD/JCO_MNG
On the left side of the screen, select the connector that is being used. Usually, the Java connector is connected using DATAVARD_JAVA_CONN RFC.
On the right side of the screen, click logs to display Java logs.
In the selection screen, it is possible to set several parameters like the Date of the log, Number of lines, etc. It is also possible to select a specific filter for messages. Message filters are DEBUG, TRACE, INFO, WARN, ERROR. Click the display button to display logs.
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 Java connector doesn't start, these are the possible issues. Even if Java doesn't start, some information can be sometimes seen in the logs. Click on the Logs button to check logs.
ACLs on SAP gateway doesn't allow registration of 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 Java connector have incorrect program ID | Check Program ID in Config tab in /dvd/jco_mng. Make sure that the RFC that is connecting to this 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 'Communication Data' user) | Correct user type in transaction SU01 |
RFC user does not exist or is locked | Create/unlock the user in transaction SU01 |
Java runtime environment is lower than 1.7 | Java connector supports only releases >=1.7. Update the JRE. |
Wrong settings | Double-check the setup in /dvd/jco_mng Config and Dependencies tab |
Install directory doesn't exist | The latest versions of Storage Management create an installation directory on its own. In case you have an older version (<1903), make sure the directory exists |
libsapjco3.so is not in $LD_LIBRARY_PATH | Make sure that libsapjco3.so is in $LD_LIBRARY_PATH of <SID>adm user. Keep in mind that $LD_LIBRARY_PATH is only updated after app.server restart. |
None of the above | Try to manually start the JVM with debug mode. Examples: Oracle Java export WORKDIR=/usr/sap/<SID>/<instance_DIR>/work/dvd_conn/jco204 IBM Java /usr/bin/java -Xmx2G |