JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690] - jboss

I have been trying to run with JRebel this configuration:
Here is my output:
c:\JBOSS\jboss-portal-2.7.2\bin\run.bat -c default
c:\JBOSS\jboss-portal-2.7.2\bin>set JAVA_OPTS=-Dhttp.proxyHost=188.173.32.78 -Dhttp.proxyPort=3128 -DproxySet=true
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: c:\JBOSS\jboss-portal-2.7.2
JAVA: C:\Program Files\Java\jdk1.6.0_25\bin\java
JAVA_OPTS: -Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n -Dhttp.proxyHost=188.173.32.78 -Dhttp.proxyPort=3128 -DproxySet=true -Dprogram.name=run.bat -server -Xms256m -Xmx512m -XX:MaxPermSize=256m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
CLASSPATH: C:\Program Files\Java\jdk1.6.0_25\lib\tools.jar;c:\JBOSS\jboss-portal-2.7.2\bin\run.jar
===============================================================================
[2012-07-16 12:32:53,968] Artifact app-ear:ear: Artifact is being deployed, please wait...
[2012-07-16 12:32:53,972] Artifact my-portlet:war: Artifact is being deployed, please wait...
Connected to server
[2012-07-16 12:32:54,007] Artifact app-ear:ear: Artifact is deployed successfully
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
Disconnected from server

Notice the following start up parameter in your post.
-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n
There must be some other process occupied the 8787 port.

The 8787 port is already in use.
If the 8787 port in use by another application, you need to select a different port number in file run.bat
For example, 18787

Usually this error occurs when the port is already in use. Based on my experience, this usually happen when the server didn't started successfully making the server still running in the process. If you're using windows, you can check out your Task Manager (Ctrl+Shift+Esc) and then look for "java.exe" process. Terminate it and try to start your server again.

ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
from "JAVA_OPTS: address=8787"
You set Address 8787
Find the PID
netstat -ap | grep 8787
If you still see the PID with the above command, then
there are child PIDs. To find the child PIDs
pstree -p
and
pstree -p | grep previousPID
Find the groupPID of the PID
ps x -o "%r %p %y %x %c"
Kill the found PID
kill -TERM -groupPID

This problem occurs whenever the port required to run your server is already in use by some other application. Since the port number 8080 which i used for my jetty server was already in use,it gave me this error so I just changed the port from 8080 to 7070 and it worked for me..

Check the debug port in your
standalone.sh
It must have been
DEBUG_MODE=true
DEBUG_PORT="8787"
Change the debug mode to false or pass a new debug port from the new sh file which calls this standalone --debug 8788

In my case, this argument was wrong: address=server4.example.com:8787 I was trying to run from another server, e.g., server3.example.com.

Related

Error: EADDRINUSE connect EADDRINUSE 127.0.0.1:50596 when running e2e test suit on VS code

When I run e2e test suites on VS code getting an unusual error - Error: EADDRINUSE connect EADDRINUSE 127.0.0.1:50596 don't know how to solve this, its happening to all instance and failing all test cases with same error. when I debug this in dev tools getting this error in console log (node:16612) [DEP0005] Deprecation Warning: Buffer() is deprecated due to security and usability issues. Please use the buffer. From() methods instead.
(Use Code --trace-deprecation … to show where the warning was created)
Node version >v11.15.0**
NPM. version >6.7.0
Chrome browser
This error Error: EADDRINUSE connect EADDRINUSE 127.0.0.1:50596 means the address 127.0.0.1:50596 is already used.
You can find out what's using the port 50596, and then kill the process (see https://www.printsupportcenter.com/hc/en-us/articles/115003386949-Determine-which-program-uses-or-blocks-a-port):
Windows:
netstat -ano -p tcp | find "50596"
Linux/Mac:
sudo netstat -ano -p tcp | grep ":50596"
These previous commands will give you the Process IDentifier (PID), which you can then use to kill your process:
Windows:
taskkill /PID <pid_number>
Linux/Mac:
kill <pid_number>

eclipse can not debug, but run is ok

suddenly, my eclipse does not work in debug model. when click debug button, i got these error messages, and debug failed.
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: gethostbyname: unknown host
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [debugInit.c:750]
could anyone help, or gives some help.
i have found solution. "unknown host ERROR" in error message is the key.
just because i used switchhost app to change my mac's hosts file. And line of "127.0.0.1 localhost" had been removed.
so, what need to do to solve this problem is adding "127.0.0.1 localhost" to mac's hosts file.
127.0.0.1 localhost
Add the above entry in /etc/hosts file and you should be good.

IBM Worklight : Transport error 202: bind failed: Address already in use

I have an eclipse workspace with an IBM worklight project running and I want to run another instance of eclipse with another worklight project on different ports. I have modified the server.xml which has the Http ports as follows:
<httpEndpoint host="*" httpPort="10090" httpsPort="10453" id="defaultHttpEndpoint">
<tcpOptions soReuseAddr="true"/>
and also the admin port as follows:
<jndiEntry jndiName="ibm.worklight.admin.jmx.port" value="10453"/>
But when I start the second server, I get the below error:
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]
Which port am I missing to change and where do I change that in eclipse?
You may also need to change the debug port for each server.
See here under "Java remote debug...": http://www.ibm.com/support/knowledgecenter/SSHS8R_6.3.0/com.ibm.worklight.dev.doc/devref/c_dev_test_server_and_console.html
You need to open the jvm.options file in Eclipse > Servers > development server. Then edit the port number "10777" to a different one.

IBM mobile first development server unable to start in eclipse?

Ibm mobilefirst development server failed to start showing error
objc[77281]: Class JavaLaunchHelper is implemented in both /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/bin/java and /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/lib/libinstrument.dylib. One of the two will be used. Which one is undefined.
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
/Users/test/Documents/sathyarajworkspace/eclipse/plugins/com.worklight.worklight-artifacts_7.1.0.00-20151012-1525/liberty/wlp/bin/server: line 764: 77281 Abort trap: 6 "${JAVA_CMD}" "$#"
Since i lost eclipse version of 6.3 i copied eclipse from another mac.
when i tried to run the development server this error shown.
i have also updated to current version of IBM MF still issue exist.
How to fix this issue in mac.
UPDATE:
killall -9 java
Killing java process worked.Thanks
The port is taken.
Try killing the Java process and then start the server again.
in command prompt, run lsof -i :10080
then kill the ports running with kill -9 <port_number>
in the "server" tab in eclipse, delete the "mobilefirst development server"
close eclipse, reopen eclipse, the server should recreate
start the server again

Eclipse JDWP error when trying to debug

I get the following error when trying to debug a local java application in eclipse.
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: connect failed: Connection refused
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
I read that it might be caused by something using the same port as the one eclipse wants to use for debugging, but how do I determine the port number. I couldn't find anything in the error log or the preferences.
Any ideas?
I ran into the same issue and it turns out I was specifying server=n parameter in the jdwp debug string. It turns out that if we specify server=n in the debug connection string, it'll attempt to attach/connect to that port instead of listening on it. Switching to server=y solved my issue. It's documented in the
official jpda documentation.
Maybe it's your antivirus. Are you using avast if so look at this https://feedback.avast.com/responses/eclipse-debug-functionality-not-working-after-upgrade-to-avast-2014
The solution is upgrading to the latest version of avast (http://forum.avast.com/index.php?topic=139606.0)
Please ensure that, the below entry is there in /etc/hosts file (for mac/linux)
127.0.0.1 localhost
Previously I unknowingly commented out this line, so it worked for me after reverting back. Hope this helps.