Geek Answers Handbook

FATAL ERROR in native method: JDWP There is no initialized error when starting the hybrid server in debug mode

While trying to start my hybrisserver in debug mode, I received the following error messages and hybrisserver stopped. I tried, but could not decide. Any help please.

 FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)<br/> ERROR: transport error 202: bind failed: Permission denied<br/> ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)<br/> JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]<br/> JVM exited while loading the application.<br/> Reloading Wrapper configuration...<br/> Launching a JVM...<br/> FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)<br/> ERROR: transport error 202: bind failed: Permission denied<br/> ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)<br/> JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]<br/> JVM exited while loading the application.<br/>

The line had 5 failed starts, each of which lasted less than 300 seconds.
Refuse.
A configuration problem may occur: check the logs.

 <-- Wrapper Stopped<br/>

An error has occurred in the process.

+5
source share
3 answers

@thijsraets is true. Either you need to check where the port is located (8000), or override the default value for something else in the local.properties file.

 tomcat.debugjavaoptions=-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,address=8001,suspend=n

Run "ant all." This will configure debug for port 8001.

OR

You can change the JVM options in the wrapper-debug.conf file ...

 wrapper.java.additional.23=-Xrunjdwp:transport=dt_socket,server=y,address=8001,suspend=n
+8
source

For people who are facing this problem, something else seems to be tied to the debug port, try changing the port to: tomcat.debugjavaoptions

+3
source

The same thing happened to me and tried to kill the server and safely restart it. I have completed the following steps:

  • ps aux | grep java. this will help me find the PID process id
  • kill -9 PID

If you want to kill all tomcat processes, you can do

pkill -9 -f tomcat

this will safely restart the server.

0
source

More articles:


All Articles