BindException in DirectClickThroughUiPlugin when using 2 Eclipse instances


I have installed:

- (3.0.2.v20111010)

- (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 Address already in use: JVM_Bind

at Method)






at org.mortbay.jetty.AbstractConnector.doStart(


at org.mortbay.component.AbstractLifeCycle.start(

at org.mortbay.jetty.Server.doStart(

at org.mortbay.component.AbstractLifeCycle.start(

at com.atlassian.connector.eclipse.internal.directclickthrough.ui.DirectClickThroughUiPlugin$2.runImpl(



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...


1 answer

1 accepted

This widget could not be displayed.


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.



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
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in Teamwork

What teamwork quotes inspire you?

Hey everyone! My name is Natalie and I'm an editor of the Atlassian Blog and I've got a question for you: What's your favorite quote about teamwork?  We've compiled a list here, along with...

140 views 16 7
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you