Unable to open debugger port through IntelliJ

Question

I've got a server running on DigitalOcean and a JAR file that I want to debug. I first start the JAR on the remote server using

java -jar Server.jar -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005

but on the console I see no output like "listening on port 5005...".

When I press debug in IntelliJ it says

unable to open debugger port (198.xxx.xxx.xx:5005): java.net.ConnectException "Connection refused"

This is my IntelliJ configuration:

I also tried using -Xdebug but it still didn't work.

If I set suspend=y it should wait until a debugger is connected, but instead, it starts without problems.

SOLO · Accepted Answer · 2018-10-17 18:03:23Z

21

The command to start the remote Java process in debug mode looks correct. If you don't see "Listening to Port blah" when you start the server JAR, then it might mean that the debug args are not being picked up. Another way to quickly check this would be to test with a telnet localhost 5005 on the machine where the server JAR is being executed. The telnet will fail if that port is not being used.

I suggest that you try the following, since the order of the parameters might be significant (I'll add some official evidence for this later):

java "agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005" -jar Server.jar

edited Oct 17, 2018 at 18:03

SOLO

8789 silver badges19 bronze badges

answered Nov 16, 2016 at 20:24

Ashutosh Jindal

18.9k4 gold badges68 silver badges95 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Renato Back Over a year ago

I would just like to stress out the fact that the order of the parameters does matter.

Kajzer Over a year ago

Where is the official evidence? Huh? HUH? Joke.

Rafael Reyes · Accepted Answer · 2022-02-14 15:28:43Z

20

this command worked for me:

export JAVA_OPTS='-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=0.0.0.0:5005'

by default idea remote dialog suggest:

'agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005'

change it to:

'agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=0.0.0.0:5005'

and issues port 5005.

edited Feb 14, 2022 at 15:28

Rafael Reyes

2,6658 gold badges38 silver badges53 bronze badges

answered Oct 20, 2018 at 2:41

suifengpiao14

2092 silver badges2 bronze badges

6 Comments

mbartn Over a year ago

It worked for me, but I don't know why... Problem was with intellij connecting to tomcat inside docker container.

K. Siva Prasad Reddy Over a year ago

While connecting to remote server from Intellij IDEA, when I used export JAVA_OPTS='-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5505' it didn't work. But when I used address=0.0.0.0:5505 then it worked.

Lukenzo Over a year ago

Lifesaver! Thank you. I spent last hour trying different configurations and all I was missing was "0.0.0.0" part before port

abinthomas12914 Over a year ago

This in setenv '-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=0.0.0.0:5505' work for me

Instein Over a year ago

Adding "0.0.0.0:" makes it work! Thanks! But what's the difference did "0.0.0.0:" make?

|

martijnn2008 · Accepted Answer · 2017-05-05 11:33:25Z

5

This command worked for me:

java -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005 -jar Server.jar

edited May 5, 2017 at 11:33

martijnn2008

3,6805 gold badges33 silver badges42 bronze badges

answered May 5, 2017 at 8:52

Vidya Priyadarshini

511 silver badge1 bronze badge

1 Comment

Vishal_Kotecha Over a year ago

pretty old thread but want to highlight one thing - I was using same command but had address=*:5005, I changed it to address=5005 and it worked like a charm

Amin Heydari Alashti · Accepted Answer · 2020-11-23 09:08:39Z

Thanks to suifengpiao14 but I'm going to describe the problem a bit more in detail.

I checked multiple things, and at the end found the reason: actually as like as a restful service we want to be accessible from out of the server we are running it that we should set 0.0.0.0 as the nameserver, here we should do a similar one. I checked the difference between the server from which I can remotely debug and the one which I can't. using netstat command:

for the server which I was ok with:

tcp        0      0 0.0.0.0:5005            0.0.0.0:*               LISTEN      8323/java

for the server which I had problem with:

tcp        0      0 127.0.0.1:5005            0.0.0.0:*               LISTEN      8323/java

So, using below jvm options should be helpful:

'agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005'
'agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=0.0.0.0:5005'

invzbl3 · Accepted Answer · 2022-03-16 17:20:31Z

I've reproduced similar issue:

Unable to open debugger port (localhost:5005): java.net.ConnectException "Connection refused (Connection refused)"

I had it while running debugger w/ command line arguments for remote JVM using Run/Debug configurations:

-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005

by attaching IDE with exposed debug agent server.

Since I've used Kubernetes cluster, the reason was:

once the pod has been created and was running as expected, I needed to proceed to set up port forwarding with the kubectl port-forward command, with the port to expose locally for traffic from the application before running debugger.

Based on kubectl port-forward syntax:

kubectl port-forward <resource-type/resource-name> [local_port]:<pod_port>

In format like:

kubectl port-forward <pod-name> -n <namespace> 5005:5005

or in a shorter form:

kubectl port-forward <pod-name> 5005:5005

The client listens on port 5000 locally and forwards to 5000 in the pod.

Accordingly entrypoint.sh file of the service was configured w/ the following command for Kubernetes cluster:

java -Djava.security.egd.=file:/dev/./urandom -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005 -Xmx400m -jar /service.jar

As result, running port-forward before debugger solved the issue.

Ashrik Ahamed · Accepted Answer · 2023-04-26 05:27:07Z

1

When running debugger port in tomcat, you should start the tomcat server with this command:

catalina.bat jpda start

answered Apr 26, 2023 at 5:27

Ashrik Ahamed

4754 silver badges12 bronze badges

Comments

jacob · Accepted Answer · 2017-11-01 20:55:00Z

0

In my case it was because under settings -> build, execution, deployment -> debugger I had a built in server running on the same port as which I was trying to attach my debugger to for some reason.

answered Nov 1, 2017 at 20:55

jacob

5397 silver badges16 bronze badges

Comments

luke8800gts · Accepted Answer · 2022-02-02 15:42:19Z

0

For people like me who sometimes forget to read...

Copy and paste the arguments to the command line when JVM is started
says the Run/Debug Configuration in IntelliJ, directly under:
-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005

Means: Copy this line and go to your docker configuration. Add an environment variable (modify options dropdown). Paste it there with JAVA_OPTS= prepended.

Now when you did every correctly, you will have
Listening for transport dt_socket at address: 5005
and
Command line argument: -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005

This is who I solved it...

answered Feb 2, 2022 at 15:42

luke8800gts

4384 silver badges7 bronze badges

Comments

Procrastinator · Accepted Answer · 2022-09-14 06:45:29Z

0

One of the reason is that the port is not enabled. You can try by enabling the port using the below command

firewall-cmd --zone=public --permanent --add-port=8001/tcp

Once the port is up, restart tomcat & try connecting again. Hope it helps.

edited Sep 14, 2022 at 6:45

Procrastinator

2,67445 gold badges31 silver badges37 bronze badges

answered Sep 9, 2022 at 6:57

swapnil sharma

1

Comments

Bawantha · Accepted Answer · 2023-01-26 07:08:32Z

0

This might help someone That port in JVM debug is not your web app port

answered Jan 26, 2023 at 7:08

Bawantha

4,0084 gold badges29 silver badges40 bronze badges

Comments

womd · Accepted Answer · 2023-08-29 07:18:34Z

0

this solved it for me:

net stop winnat

net start winnat

IntelliJ IDEA - Address localhost:1099 is already in use

answered Aug 29, 2023 at 7:18

womd

3,50131 silver badges23 bronze badges

Comments

Timur · Accepted Answer · 2023-12-21 11:24:38Z

0

Remote debugger needs to connect to the JVM that is already running in debug mode. Make sure you start the app you want to debug first with the JVM options suggested by the IDE. Then start Remote configuration to connect and debug this app. ~CrazyCoder

answered Dec 21, 2023 at 11:24

Timur

1,37214 silver badges14 bronze badges

Collectives™ on Stack Overflow

Unable to open debugger port through IntelliJ

12 Answers 12

2 Comments

6 Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

12 Answers 12

2 Comments

6 Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related