Unable to open debugger port in IntelliJ IDEA

Question

I have a problem that I can not set up my application in debug mode with IntelliJ IDE, but run mode is OK.

My OS is Windows 7, IDE is IntelliJ IDEA, web container is Tomcat 6. I have tried for a long time, changed the HTTP port and the JMX port, but it did not work.

When I set up the app in debug mode with IntelliJ, it failed and the event log is:

16:05:35 Error running tomcat: Unable to open debugger port : java.net.BindException "Address already in use: JVM_Bind".

What is normal practise and port for tomcat6 to allow debugging? You might need to enable some flags / settings... — vikingsteve, Oct 09 '14 at 12:36
@vikingsteve thank you! Tt is an occasional case, when I restart my computer, eveything is OK.May be some port is conflict, but I dont know which one is. — feng smith, Oct 10 '14 at 01:27
Cool :) There are also some handy tools to see which application is holding a port - worth perhaps using such a tool to identify quickly the source of the conflict. In worst case looking in windows task manager and stopping tomcat.exe, java.exe, etc might help. — vikingsteve, Oct 10 '14 at 07:49
Must be careful! Must not set the http port below 1024 if you are not the admin or root.Or you are always get the error " Error running tomcat: Unable to open debugger port" — tiramisu, Aug 29 '17 at 07:13

score 190 · Accepted Answer · answered Apr 28 '15 at 09:08

190

the key to the issue is in debugger port. I was having the same problem, I was killing every process listening on port 8081 (my http port), 1099 (JMX port), tomcat shutdown port, every java.exe, and still nothing.

The thing is this debugger port is different. If you run the application, it will go through the port you have Tomcat configured for, 8080, 8081 or whatever. But if you run it in Debug mode, it goes through a different port.

If you go edit your Tomcat configuration from IntelliJ, the last tab is Startup/Connection. Here go see the configuration for Debug mode, and you'll see its port. Mine was 50473. I changed it to 50472, and everything started working again.

answered Apr 28 '15 at 09:08

T.M.

3,111
1
18
15

19

Thanks, it works. And for those who want to solve it by closing the process holding the port, open task manager->performance->resource monitor-> network , you can find the process there. – matrix Nov 20 '17 at 06:12
7

What a pitty that there is no "autoassign unused port" option XD – Gandalf Mar 20 '18 at 11:11
Thanks a lot. - @T.M. I was also killing all the processes. – Raj Rajeshwar Singh Rathore Apr 09 '18 at 10:54
thanks, changing the port from Startup/Connection did it for me – Csa77 Jul 08 '19 at 17:19
It's a pity this is still happening with Intellij 2019.2.3. The change of debug port is the only way I was able to get it to work (other than rebooting my machine) – cakidnyc Oct 25 '19 at 02:57
5

I took the advice of changing the port but I had to change it to something far away from 50473. I tried 50450, 50500, and 50400 and was still getting the same error message for all those ports. what ended up working was choosing 8085 (and I only chose that since it's close to my server's 8080 port) – rhavelka Nov 05 '19 at 22:30
2

If this doesn't work, make sure to check your event log for preceeding errors. In my case the JMX port was the one that was actually blocked, but the debugger port message overlayed it. Unblocking the JMX port resolved both error messages in my case, unsure why IntelliJ complained about the debugger port also. – kjosh Jul 29 '20 at 09:41
The killing processes on the JMX port worked for me, thanks. – Sajad Jun 06 '22 at 06:18

score 74 · Answer 2 · answered Jul 06 '18 at 01:50

74

If you're on windows you can bypass the socket issue completely by switching to shared memory debugging.

answered Jul 06 '18 at 01:50

Avner

4,286
2
35
42

8

This is what helped me in the end. Before this, I needed to change ports every few hours, sometimes even that did not help... Ending the java processes also did nothing. – IntelliData Nov 01 '18 at 14:29
Many thanks for this suggestion. After changing to Shared memory IntelliJ failed on another issue (my server.xml was corrupted). Fixed it and moved back to Transport. All good. – Jacques Koorts Aug 07 '19 at 10:30
5

In my case it's extremely frustrating as there is NEVER any process using the port that IntelliJ says is already in use. This option seems to have worked and hopefully I'll never again waste time using diagnostic tools to find these non-existent processes reported by IntelliJ. – user1445967 Oct 16 '19 at 18:51
Thanks for this tip. In my case, this started happening suddenly, without any known modification - neither an update or a new program install. Just after a Windows 7 reboot after months of using IntelliJ. Not happening on any of my other computers. And no program is using that port. I'd like to find an explanation. – Pere Nov 16 '20 at 14:07
2

This deserves more upvotes. Solved my problem. – Rai Nov 05 '21 at 13:25

score 60 · Answer 3 · edited Jan 05 '18 at 23:59

60

For me, IntelliJ Event Log (right bottom corner) had below logs:

Error running EntitmentTooling-Debug: Cannot run program "/path-to/apache-tomcat-8.5.15/bin/catalina.sh" (in directory "path-to/apache-tomcat-8.5.15/bin"): error=13, Permission denied

Error running EntitmentTooling-Debug: Unable to open debugger port (127.0.0.1:58804): java.net.SocketException "Socket closed"

The command

$ chmod a+x /path-to/apache-tomcat-8.5.15/bin/catalina.sh

to sufficiently change privileges worked for me.

edited Jan 05 '18 at 23:59

hoefling

59,418
12
147
194

answered May 24 '17 at 05:19

Chandan

601
5
3

looking at `Event Log` is the key here, previous error was the root cause – yunandtidus Apr 06 '20 at 06:10
This is the best answer. Works perfectly! – Manoj Shrestha Apr 09 '20 at 16:04
Thanks your answer solve my problem after several month – saba safavi Aug 02 '20 at 06:50

score 18 · Answer 4 · edited Jun 20 '20 at 09:12

I have encountered the same error while using IntelliJ. Since I have started multiple instances of IntelliJ. While starting two instance it started properly. However, when starting another one, it was giving below error.

unable to open debugger port (127.0.0.1:debug-port-number) java.net.socketexception interrupted function call accept failed

There are basically two places you can check your ports related to debugging in IntelliJ

JMX port - you can find this is
In Startup/Configuration, there is debug option just click this.

What to Check: If IntelliJ is throwing above error, means issue is any of the above listed ports. To verify this open event log (its available in right corner down) and check the exact message. Event log will have message like below

11:19 PM    Error running 'Tomcat-tp': Address localhost:1098 is already in use

11:19 PM    Error running 'Tomcat-tp': Unable to open debugger port (127.0.0.1:51787): java.net.SocketException "Interrupted function call: accept failed"

Solution-1 Check the JMX port of current intelliJ which is not starting with the working one and verify if JMX ports are not duplicated within IntelliJ instance or any of the software which is running in your machine is not using this port.

Solution-2 If JMX is not duplicated then verify your debug port, check in all IntelliJ instance and do the changes.

Surely either JMX or Debug port is having issue just use unique JMX and Debug port and it will work.

Hope this will help someone.

Thank you. I always have multiple instances of IntelliJ running. — cs_pupil, May 14 '20 at 17:06
Thanks! Even though I recieved an error about my debugger port, the problem was in fact the duplicated JMX port. — Florian Wicher, Oct 20 '20 at 09:30

score 11 · Answer 5 · answered Jan 24 '17 at 05:14

This works for me consistently (it happens to me from time to time, when I do things such a restart tomcat when I am running the integration tests, for example)

1) Find the process that has the port 1099 open

sudo netstat -anp | grep tcp | grep 1099
cp6       0      0 :::1099                 :::*                    LISTEN      9857/java

2) kill it

kill 9857

3) Start Tomcat.

score 8 · Answer 6 · answered Feb 22 '16 at 21:54

I had same issue in windows 7 and IntellijIdea 14. I killed the java processes by going CTRL+ALT+ESc, find java and kill it. Now Re-Run, the application again it should be fine.. You can also do it with command line or shell(linux), but I found this easier for myself

score 6 · Answer 7 · edited Oct 31 '17 at 08:18

6

I solved the issue by this way.

I tried to kill all the java.exe processes but it was useless.
Then I tried deleting the Tomcat server
I re-deployed the project and restarted the project and it worked.

See these links for more information:

Delete Tomcat

Add a new Tomcat

edited Oct 31 '17 at 08:18

clemens

16,716
11
50
65

answered Oct 31 '17 at 05:50

Abbot

61
1
3

I solved the issue by my way. why not share it with others? – Abbot Oct 31 '17 at 06:14
Sorry. It looked like you were asking a new question. Got confused because of the present tense("*I have the same issue*") – adiga Oct 31 '17 at 06:18
That's okay. Approved a pending edit on the answer which should fix all the grammatical mistakes. – adiga Oct 31 '17 at 06:22

score 5 · Answer 8 · answered Nov 13 '17 at 15:29

5

I had this exact message.

The reason was that some IDE (I use Eclipse and Intellij) failed to shutdown the tomcat server. Or maybe crashed before it could do so.

The solution was to navigate to C:\...\apache-tomcat-xxx\bin and run shutdown.

answered Nov 13 '17 at 15:29

Florian F

1,300
1
12
28

score 5 · Answer 9 · answered Jul 07 '19 at 08:49

5

All the other solutions unfortunately did not work. This is what worked for me . I simply changed the debugger port to some other port number.

Intelij-> preferences->Build, execution, deployment ->Debugger-> Built in server->port(change value )

answered Jul 07 '19 at 08:49

Rachita Nanda

4,509
9
42
66

score 4 · Answer 10 · answered May 14 '21 at 11:33

4

My fix was the change debug port from 54444 to 7070

answered May 14 '21 at 11:33

Oleh Tatsiun

749
6
7

score 3 · Answer 11 · edited Dec 03 '14 at 17:42

3

It happens occasionally that when I restart my computer, everything is OK. Perhaps there is a port conflict.

Restart the computer works because instances of Java or Tomcat are killed during the restart. You can also consider killing the specific processes from Task Manager

This also happens if there is an issue in the context.xml file. In my case, I had accidentally changed the context value.

edited Dec 03 '14 at 17:42

Ken Keenan

9,818
5
32
49

answered Oct 11 '14 at 02:41

feng smith

1,487
2
9
22

I tried all the mentioned solutions and nothing worked except for computer restart. – Sarah Tammam Feb 26 '19 at 16:01
I think this is an underrated solution. It will fix most permission issues / file locking issues / zombie process issues. It's inconvenient, but the other solutions are also inconvenient, and this option lets you get up, stretch, get a drink :) – AlexMA Jul 09 '21 at 19:55

score 3 · Answer 12 · answered May 24 '16 at 01:52

3

I have the same issue,because my computer's DNS miss 127.0.0.1 localhost. When I add 127.0.0.1 localhost to my host file,it become ok.

answered May 24 '16 at 01:52

vince

31
1

1

I had the same problem and this solution also did the trick for me. Alternatively, provide the IP in the Intellij Debug configuration instead of the host name "localhost". – martin_wun Sep 06 '16 at 11:41

score 3 · Answer 13 · edited Jun 20 '16 at 12:07

3

While debug I got this issue: It worked with

tried changing my Tomcat http port 8082 to 8083(In debug configurations on IntelliJ and in Tomcat->conf->server.xml also)
tried changing JMX port from 1099 to 1009.
tried changing debug port in Startup/Connection in debug configurations
killed all java processes in TaskManager->Processes.

edited Jun 20 '16 at 12:07

kl78

1,628
1
16
26

answered Jun 20 '16 at 10:06

Shweta Shrivastava

31
2

score 3 · Answer 14 · answered Jul 26 '17 at 15:41

There are various reasons for this.
- There might be the problem with debugger port---Please change it to resolve( answered by T.M )
- There might be some issue with intellij cache --Invalidate cache and restart will solve it ( answered by feng smith )
- There might be problem with any other Port, like JMX, AJP --- Please change these port numbers as well.
I wanted to add this as comment but not enough rep

Igor Tiulkanov · Answer 15 · 2019-12-12T13:30:20.590

3

My assumption that this exception usually occurs when Tomcat is improperly closed and still holding the ports. Usually it is enough to kill any process listening to 1099 port. For Window 10:

netstat -aon | find "1099"


taskkill /F /PID $processId

edited Dec 12 '19 at 13:30

answered Dec 12 '19 at 09:35

Igor Tiulkanov

552
5
18

score 2 · Answer 16 · answered Oct 12 '17 at 10:07

None of above methods worked in my case i.e. changing port number in run configuration, machine restart, invalidate cache in IntelliJ, killing process shown in netstat (nestat -anob | findstr <port-number> and then tskill <pid>). The only thing that finally helped was starting and shutting down tomcat manually via startup.bat and shutdown.bat (you should use correspondig .sh files on linux and macOS).

score 2 · Answer 17 · answered Feb 06 '18 at 20:58

2

The only thing that worked for me is to go to Task Manager on Windows, and end all the Java processes that is running by right click -> end Task.

answered Feb 06 '18 at 20:58

truthseeker

439
1
5
9

score 2 · Answer 18 · answered Jan 11 '19 at 10:04

Check "Run" configuration to see which port it is using (8081).
Find all the other processes using that port lsof -t -i :8081
Kill the processes on that port. kill PROCESS_ID
Run Tomcat in Debug mode.

In my case, I wasted so much time on changing debugger port but it was not the issue. Since tomcat was not able to run on the port I chose in Run configuration, I was not able to debug my service.

score 2 · Answer 19 · answered Feb 16 '19 at 10:15

2

In Server tab of Tomcat configuration in IntelliJ, change JMX port to another number.

answered Feb 16 '19 at 10:15

Majid

13,853
15
77
113

This worked for me and the accepted answer did not. – Sam Orozco May 31 '19 at 20:28

score 2 · Answer 20 · answered Jun 14 '19 at 09:36

2

Change debug port of your server configured in the Intelli J.

It will be fixed.

answered Jun 14 '19 at 09:36

Shahid Hussain Abbasi

2,508
16
10

Even after change also its not working .. I have open multiple instance and few of them it working not for all. – Kushwaha Mar 20 '20 at 10:25

score 1 · Answer 21 · answered Sep 24 '19 at 14:33

1

In my case I had another project open in IntelliJ, and had Tomcat running in debug mode in that project. Stopping that instance of Tomcat resolved the issue.

answered Sep 24 '19 at 14:33

Jan Peter

380
6
16

score 0 · Answer 22 · answered Nov 02 '17 at 12:08

0

In my case, there was a problem in server.xml for Tomcat/conf folder where I had extra comment tags under another comment tag. So I think, since there was some problem in server.xml, it was not able to start Tomcat. And moreover it copies the tomcat folder from your installation directory to C:\Users\username.IntelliJIdea2017.2\system\tomcat\Tomcat_service

answered Nov 02 '17 at 12:08

Arun

71
1
2

1

Your answer does not seem to help with the OP question. What should he do? – Flummox - don't be evil SE Nov 02 '17 at 12:57

score 0 · Answer 23 · answered Jan 07 '19 at 16:28

This happens when you have application running on the same port number. One way to do this by killing the process forcefully. Open command prompt as an admin. Run command 'taskkill /IM "java.exe" /F'. This worked for me in Windows. Let me know if this works.

score 0 · Answer 24 · answered Dec 20 '19 at 13:48

0

Probably you get the same error message if the standalone.xml in your standalone/configuration folder cannot be found. At least I have the same error when using a WildFly 14.0.1:

answered Dec 20 '19 at 13:48

ShadowGames

1,110
1
10
15

score 0 · Answer 25 · answered Jul 06 '20 at 10:36

0

Just restart the Android studio before try these all. I face same right now and i fix it by this way.

Happy coding :)

answered Jul 06 '20 at 10:36

happy_coding

1,064
1
13
24

score 0 · Answer 26 · answered Jul 31 '20 at 09:10

For anyone who comes here with the similar message:

Unable to open debugger port (127.0.0.1:50470):
    java.net.SocketException "Interrupted function call: accept failed"

This may be caused by something completely independent, i.e. it's not a port configuration. If you're running Tomcat, for instance, it may be that you have an invalid web.xml. Check your Event Log for any previous errors:

Cannot load C:\...\conf\web.xml: ParseError at [row,col]:[480,29]
            Message: The element type "param-value" must be terminated by the matching end-tag "</param-value>".

IntellIj error log screenshot

score 0 · Answer 27 · answered Jan 28 '21 at 09:20

I came in this scenario and as the above answers I tried to change the port like Edit Configuration -> Startup/Connection -> debug -> change the Port but it didn't solve my problem cause I was running my application in debug mode so once try to run the application as normal without debug. it solved my problem!

score 0 · Answer 28 · answered Sep 18 '21 at 23:36

This problem is sometimes just because of a misconfiguration.

Please, check if you have, for example, an SSL port number defined at your run configuration. If so, and if you don't have a right configuration for it at tomcat's server.xml, then it won't be possible to start your debug session correctly, and you will unfortunately have the same error. I think this can be shown as a different error. So, this is in my opinion an idea issue also..

The solution is, removing the SSL port number value from the run configuration of the IDE.

#intellij-idea https://stackoverflow.com/questions/tagged/intellij-idea

score 0 · Answer 29 · answered Mar 28 '22 at 20:14

This occurred to me, when I was running wildfly on intellij, and I switched the branch. I stopped wildfly, built the jar using maven, tried to re run Wildfly and got the error.

I tried changing port as mentioned in the accepted answer, but didn't work. I tried to find the process running on port, but netstat command didn't find it.

I tried restarting the OS, it also didn't help.

Then I checked the configuration folder of my Wildfly set up, that's when I realised

standalone.xml got replaced by standalone.xml.tmp

renaming it to standalone.xml helped me to resolve the error.

score -1 · Answer 30 · answered Jan 21 '21 at 10:40

-1

Running IntelliJ as Administrator in Windows did the magic for me:

answered Jan 21 '21 at 10:40

technik

1,009
11
17

score -2 · Answer 31 · answered Jun 15 '18 at 07:09

There are multiple solution for the same.

Either we may close the IDE (e.g. IntellJ)
Find t IND00123:bin devbratanand$ lsof -i:30303 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME idea 437 devbratanand 56u IPv4 0xb2720e580a7d6483 0t0 TCP 10.17.130.41:55222->vmqp-cms-pan-app1.emea.akqa.local:30303 (ESTABLISHED) IND00123:bin devbratanand$ kill -9 437

Unable to open debugger port in IntelliJ IDEA

31 Answers31

Linked