Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

BindException in DirectClickThroughUiPlugin when using 2 Eclipse instances

loic dev
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 15, 2012

Hi,

I have installed:

- com.atlassian.connector.eclipse.feature.group (3.0.2.v20111010)

- com.atlassian.connector.eclipse.jira.feature.group (3.0.2.v20111010)

Everything works fine in my Eclipse.

I am developing my own Eclipse plugin (PDE). When testing it, it seems that the second instance of Eclipse tries to start a server on the same port that the one used by the main Eclipse. When I start my test (i.e. start a second instance of Eclipse) I get the following stack trace in my main Eclipse console:

!ENTRY com.atlassian.connector.eclipse.directclickthrough.ui 1 0 2012-03-15 15:32:58.808

!MESSAGE Unable to run embedded web server, Direct Click Through will not be available

!STACK 0

java.net.BindException: Address already in use: JVM_Bind

at java.net.PlainSocketImpl.socketBind(Native Method)

at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383)

at java.net.ServerSocket.bind(ServerSocket.java:328)

at java.net.ServerSocket.<init>(ServerSocket.java:194)

at org.mortbay.jetty.bio.SocketConnector.newServerSocket(SocketConnector.java:80)

at org.mortbay.jetty.bio.SocketConnector.open(SocketConnector.java:73)

at org.mortbay.jetty.AbstractConnector.doStart(AbstractConnector.java:283)

at org.mortbay.jetty.bio.SocketConnector.doStart(SocketConnector.java:147)

at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)

at org.mortbay.jetty.Server.doStart(Server.java:235)

at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)

at com.atlassian.connector.eclipse.internal.directclickthrough.ui.DirectClickThroughUiPlugin$2.runImpl(DirectClickThroughUiPlugin.java:90)

at com.atlassian.connector.eclipse.internal.core.jobs.JobWithStatus.run(JobWithStatus.java:50)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

I don't know why you need to start a server, but could you update your code to catch this exception and deal with it ? This exception prevents me automated test to run. If you cannot avoid this exception, I will have to uninstall your plugins in order to carry on...

Thanks.

1 answer

1 accepted

0 votes
Answer accepted
jjaroczynski
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.
March 15, 2012

Hi,

Atlassian Connector for Eclipse tries to start the server because you have activated Direct Click Through feature (it allows to open file/task from other Atlassian products like Bamboo, Fisheye or Crucible). If you don't need the feature then simply deactive it in Windows | Preferences | Atlassian Connector | Direct Click Through.

If you want to use the feature you can ignore the exception message as it does not affect your debug Eclipse instance and does not have impact on your automated tests - it is just a log printout of caught exception.

Depending on how you start the debug instance of Eclipse you can also disable Direct Click Through only for this instance (or change port) while it stays enabled for your main Eclipse instance.

Best,

Jacek

loic dev
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 19, 2012
Hi thanks for the explanation. I deactivated direct click. Now I don't see the exception anymore. Thanks again. Now I can focus on my own exceptions :) Cheers.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events