error developing crucible plugin

Headley Murray January 13, 2013

I keep getting the following error when trying to test my crucible plugin:

I run the atlas-debug command.

[INFO] Starting fecru on ports 3990 (http) and 39901 (control)
[INFO] FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=
AGENT_ERROR_TRANSPORT_INIT(197)
[WARNING] ERROR: transport error 202: bind failed: Address already in use
[WARNING] ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(5
10)
[WARNING] JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initial
ized [../../../src/share/back/debugInit.c:690]
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Unable to execute mojo

Embedded error: Fisheye failed to start.
Java returned: 1 See log for details.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8 minutes 36 seconds
[INFO] Finished at: Sun Jan 13 21:26:34 CST 2013
[INFO] Final Memory: 79M/189M
[INFO] ------------------------------------------------------------------------
C:\atlastutorial\arc-code-review>

1 answer

1 accepted

0 votes
Answer accepted
Renjith Pillai
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 13, 2013

The error shows that the port 3990 or 39901 is in use. Run a netstat and see if any application is already listening on that?

Did you start another plugin and is it running?

Headley Murray January 13, 2013

Active Connections
Proto Local Address Foreign Address State
TCP 127.0.0.1:1029 Helism-PC:5354
TCP 127.0.0.1:1301 Helism-PC:1302
TCP 127.0.0.1:1302 Helism-PC:1301
TCP 127.0.0.1:1303 Helism-PC:1304
TCP 127.0.0.1:1304 Helism-PC:1303
TCP 127.0.0.1:1305 Helism-PC:1306
TCP 127.0.0.1:1306 Helism-PC:1305
TCP 127.0.0.1:1311 Helism-PC:1312
TCP 127.0.0.1:1312 Helism-PC:1311
TCP 127.0.0.1:1314 Helism-PC:1315
TCP 127.0.0.1:1315 Helism-PC:1314
TCP 127.0.0.1:1517 Helism-PC:1518
TCP 127.0.0.1:1518 Helism-PC:1517
TCP 127.0.0.1:5354 Helism-PC:1029
TCP 127.0.0.1:14456 Helism-PC:14457
TCP 127.0.0.1:14457 Helism-PC:14456
TCP 127.0.0.1:14460 Helism-PC:14462
TCP 127.0.0.1:14462 Helism-PC:14460 ESTABLISHED
TCP 192.168.1.124:26687 17.151.224.37:https CLOSE_WAIT
TCP 192.168.1.124:26691 17.151.224.18:https CLOSE_WAIT
TCP 192.168.1.124:26692 17.151.224.94:https CLOSE_WAIT
TCP 192.168.1.124:34609 st11p01st-hpaj262332-bz:5223 ESTABLISHED
TCP 192.168.1.124:34628 a23-43-240-60:https CLOSE_WAIT
TCP 192.168.1.124:35391 lb1:https TIME_WAIT
TCP 192.168.1.124:35392 lb1:https TIME_WAIT
TCP 192.168.1.124:35393 lb1:https ESTABLISHED
TCP 192.168.1.124:35394 lb1:https ESTABLISHED
TCP 192.168.1.124:35395 lb1:https ESTABLISHED
TCP 192.168.1.124:35396 lb1:https ESTABLISHED
TCP 192.168.1.124:35397 lb1:https ESTABLISHED
TCP 192.168.1.124:35399 lb1:https TIME_WAIT
TCP 192.168.1.124:35402 atl14s07-in-f30:https ESTABLISHED

Headley Murray January 13, 2013

no other plugins are running

Renjith Pillai
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 13, 2013

Try netstat -anlp

The above command did not list the listening ports, isn't it?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events