Reputation: 471

Disconnected from the target VM, address: '127.0.0.1:62535', transport: 'socket' on intellij idea CE. I can't debug my program. Any suggestions?

Connected to the target VM, address: '127.0.0.1:63073', transport: 'socket' Disconnected from the target VM, address: '127.0.0.1:63073', transport: 'socket'

Upvotes: 47

Answers (23)

Mevlüt Beder

Reputation: 107

For me, redis was causing problems like that "Redis health check failed , Unable to connect to Redis" and when I tried to enable it, I did not get any errors from spring boot and it suddenly shut down.

management:
  health:
    redis:
      enabled: false

Upvotes: 0

Wardah Imtiaz

Reputation: 1

I had the same issue, and fixed it by :

Adding activity name in App> manifest> androidManifest.XML

Upvotes: 0

Abderrahim id boubker

Reputation: 1

In my case it was the scope in the dependency of tomcat that caused the problem. when removing it it run without stopping.

<dependency>
   <groupId>org.springframework.boot</groupId>
   <artifactId>spring-boot-starter-tomcat</artifactId>
   <scope>provided</scope>
</dependency>

Upvotes: 0

vikasdfghjl

Reputation: 1

First mark a debug market on the left statement index panel, from where you want to debug the specific program. after that this will be fixed

Upvotes: 0

Vihan Gammanpila

Reputation: 332

This problem occurs when another program uses that port, so you can change the port in the spring and use another port. You need to type this simple code in your application.properties.

server.port=8080

Upvotes: 0

KiteUp

Reputation: 328

restarting IDEA helped me with this issue

Upvotes: 1

beton

Reputation: 41

You see this message because there is nothing to debug at current marker. You can check whether your marker is in the correct place or not. also, you might be trying to debug another class that has no markers or empty you can check your run configuration or run the the class that you want debug from project files.

Upvotes: 1

user2063638

Reputation: 33

Just find your projectApplication and then Run Debug on anything you want.

For Example see bellow

SpringBootApplication
public class BitApplication {
    private final Logger logger = LoggerFactory.getLogger(BitApplication.class);

    public static void main(String[] args) {
        SpringApplication.run(BitApplication .class, args);
    }
}

Upvotes: 2

Mohammad Baharloo

Reputation: 21

This problem happen when another program is using that port, so you can change port in spring, and use another port. You just need to type this simple code in your program.

System.setProperty("server.port", "4000");

enter image description here

Upvotes: 1

Zeinab Ghaffarnasab

Reputation: 818

Try re import project into intellij I had the same problem when I wanted to import eclipse project into intellij ide and reimporting solved my issue

Upvotes: 0

yogesh joshi

Reputation: 21

In my case I had commented my all test cases and then I was trying to run test cases in debug mode. So obviously there is nothing to run. So I was getting below message. Once check if the run you are trying to do all is OK.

Connected to the target VM, address: '127.0.0.1:65223', transport: 'socket' Disconnected from the target VM, address: '127.0.0.1:65223', transport: 'socket'

Process finished with exit code 0

Upvotes: 0

Yipeng Zhang

Reputation: 37

For Maven+Spring projects, I was debugging using the Spring Boot Configuration and didn't realize that the Maven configuration was already running. Shutting Maven off and restarting did the trick.

Also if you use Docker do a docker ps -a to see if your container is running.

Upvotes: 0

Dedkov Vadim

Reputation: 436

I had a similar problem + message Could not find or load main class.

It was a project on Scala with SBT.

How I solved this one:

Run my project via SBT like this: sbt my-project/run
Stopped it (Ctrl+C)
Run debug -- it works again.

Upvotes: 0

Techflash

Reputation: 767

The above message shows that JVM started and has stopped successfully.

Now what you are expecting is to halt on the breakpoint which you have applied in your program but you can't achieve that because you might have clicked on "Mute Breakpoints" button and are trying to debug a code which does not display anything on console.

Since all breakpoints are muted, your program does not halt on the expected line.

Upvotes: 4

Dante

Reputation: 51

This issue is very simple to resolve. Click on debug again and in the right-hand corner, you should see a tool bar. There's an icon that looks like two red break points overlapping. Click on that. It will pop open a menu under any exception. Please ensure that Enabled, Suspend, All, Condition, log message to console and log evaluated expression are all checked.

Upvotes: 5

Mour_Ka

Reputation: 258

In IntelliJ to solve this I found the following, that the class name wasn't linked to the file name

alt+shift+f10 right Edit

The main class was only the name of the file I had as a class ImageLabel

Upvotes: 0

Bálint Áts

Reputation: 31

Probably your program has a bug before your first breakpoint, or the program never reaches that breakpint.

Upvotes: 3

John

Reputation: 6668

I had a similar error that led me directly to this thread.

Connected to the target VM, address: '127.0.0.1:57662', transport: 'socket'
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffd0e3122a0, pid=6908, tid=0x0000000000000594
#
# JRE version: Java(TM) SE Runtime Environment (8.0_131-b11) (build 1.8.0_131-b11)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.131-b11 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C  [ig75icd64.dll+0xd22a0]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\UserNamed\IdeaProjects\supercoolproject\android\assets\hs_err_pid6908.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
AL lib: (EE) alc_cleanup: 1 device not closed
Disconnected from the target VM, address: '127.0.0.1:57662', transport: 'socket'

By reading the unusual text between

Connected to the target VM, address: '127.0.0.1:63073', transport: 'socket'

and

Disconnected from the target VM, address: '127.0.0.1:63073', transport: 'socket'

I could locate a real stack trace at:

C:\Users\UserNamed\IdeaProjects\supercoolproject\android\assets\hs_err_pid6908.log

Which led me to trap my error precisely.

UPDATE, evening YMMV, I just had a similar probelm, left the debugger running while reading a paper and Java notified me via popup there was a problem but IntelliJ gave me even less to go on. The obligatory:

Connected to the target VM, address: '127.0.0.1:63073', transport: 'socket'

Disconnected from the target VM, address: '127.0.0.1:63073', transport: 'socket'

Then something about it having closed with a 255 error code. I tried recreating the error, because it's easier than tracing my memory leak, and it worked, here is the Java error:

I'm suspicious of companies (IdeaC) pushing yet another Java binary. I clicked debug this time and got:

I can't say for certain but this appears a weakness in IntelliJ 2018. My code has got bigger too, but updates seem to bring more version conflicts.

Upvotes: 0

Vishal

Reputation: 2173

This can happen for a lot of reasons. In my case the root cause was found in the hibernate entities I was using. I needed to use couple of attributes in the entity domain that were not part of related db table. When I annotated these attributes with Transient. The spring boot application started just fine.

Example:

Entity that caused error:

class ErrorDomain{
    @Column(name = "db_prop_available")
    private String dbPropAvailable;

    private String dbPropNotAvailable;
}

Entity update to fix the issue:

class OkDomain{
    @Column(name = "db_prop_available")
    private String dbPropAvailable;

    @Transient   //javax.persistence
    private String dbPropNotAvailable;
}

This is one of the reasons for the original error you posted. But I just wanted to comment if anybody has a similar case.

Upvotes: 0

crabCRUSHERclamCOLLECTOR

Reputation: 1875

This could be a variety of things, but likely you're hitting an exception before any break points hit. Do you see an exception in your console?

An exception might look like this:

Exception in thread "main" java.lang.NullPointerException

Upvotes: 1

Janelle

Reputation: 38

I needed to delete the out files that had been created by IntelliJ from my previous debugging. A simple right click and delete on the "out" folder under your project tab should do the trick. Then compile your program again.

Upvotes: 0

user6683868

Reputation:

I had the same problem. I noticed that the drop-down menu wasn't set on app. Check this out:

Upvotes: 13

Barış Akkurt

Reputation: 2256

Which line did you put breakpoint? Suppose you have the following snippet:

    public static void main(String[] args) {
        int res = add(5, 8);
        System.out.println(res);

    }

    public static int add(int a, int b)
    {
        int c=a+b;
        return c;
    }

When I put the breakpoint the line that has { under the add method. I got the very same error as you. If I put the breakpoint to the line int c=a+b;, the debugger works as expected. It's annoying, this is the solution I could come up.

Upvotes: 9

Disconnected from the target VM, address: &#39;127.0.0.1:62535&#39;, transport: &#39;socket&#39; on intellij idea CE. I can&#39;t debug my program. Any suggestions?

Answers (23)

Related Questions

Disconnected from the target VM, address: '127.0.0.1:62535', transport: 'socket' on intellij idea CE. I can't debug my program. Any suggestions?