Skip to content

Commit

Permalink
Merge pull request #2371 from telefonicaid/AlvaroVega-patch-1
Browse files Browse the repository at this point in the history
Update debugging.md
  • Loading branch information
fgalan authored Apr 17, 2024
2 parents f62eff7 + 564c2bf commit 3f7005e
Showing 1 changed file with 13 additions and 2 deletions.
15 changes: 13 additions & 2 deletions doc/cygnus-ngsi/user_and_programmer_guide/debugging.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ cygnus:
volumes:
- ${CYGNUS_CONF}/agent.conf:/opt/apache-flume/conf/agent.conf
environment:
- CYGNUS_JAVA_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=6006
- CYGNUS_JAVA_OPTS=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:6006
- CYGNUS_SKIP_CONF_GENERATION=true
log_driver: json-file
log_opt:
Expand Down Expand Up @@ -53,6 +53,17 @@ Warning: JAVA_HOME is not set!
Listening for transport dt_socket at address: 6006
```

## Attaching java jdb debugger
```
jdb -attach 127.0.0.1:6006
```
```
Set uncaught java.lang.Throwable
Set deferred uncaught java.lang.Throwable
Initializing jdb ...
>
```

## Attaching IntelliJ debugger.

Once the container is up and running it's time to setup IntelliJ.
Expand Down Expand Up @@ -91,4 +102,4 @@ When de debugger is attached you will see the output:
Connected to the target VM, address: 'localhost:6006', transport: 'socket'
```

This means the IntelliJ debugger attached successfully to the container.
This means the IntelliJ debugger attached successfully to the container.

0 comments on commit 3f7005e

Please sign in to comment.