You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Keystore type: PKCS12
Keystore provider: SUN
Your keystore contains 2 entries
hostname, Feb 1, 2018, PrivateKeyEntry,
Certificate fingerprint (SHA1): 47:FB:13:4E:48:91:76:1D:FE:06:15:4B:8B:EB:8E:21:02:AD:37:CA
caroot, Jul 16, 2019, trustedCertEntry,
Certificate fingerprint (SHA1): 1B:E0:B8:CE:E8:CB:B7:47:3D:8E:3A:63:9D:42:FA:04:D4:47:11:99
Connect for remote debugging:
Start your app with java -jar -Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=y app.jar … parameters
Create an IntelliJ Run configuration to connect to the target: select “Remote” type of run configuration, and provide hostname and port (in this case 8000) in parameters
When an app is run, it should say “Listening to dt_socket on 8000” until you start debugging session for this configuration in IntelliJ IDEA
Use proper JDK:
Sometimes line numbers, or even class/method names in some internal packages do not make any sense because of discrepancies between the JDK IDEA is configured for, and the one that’s used by the remote process.
To mitigate this, copy the whole JDK folder from the remote host (might be something like /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.201.b09-2.el7_6.x86_64) locally, create an empty Java project in IDEA and specify this folder as a “New” SDK when creating a project – in this case your debugging session, when run in this project, will display more correct information