How to enable Fisheye/Crucible to listen to web requests on additional ports

Still need help?

The Atlassian Community is here for you.

Ask the community

Purpose

This page covers how to enable your Fisheye/Crucible instance to listen to web requests on additional ports besides those specified in the Fisheye/Crucible user interface or in the config.xml file.

This can be used, for example, in the following use cases:

  • create an unproxied application link

Solution

The web interface and config.xml for Fisheye/Crucible will not allow the server to listen to web requests on multiple ports, the following steps show how to achieve this.

  1. Stop Fisheye/Crucible
  2. Create a file named jetty-web.xml in <Fisheye installation directory>/content/WEB-INF with the following content: 

    <?xml version="1.0" encoding="ISO-8859-1"?>
    <!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN" "http://www.eclipse.org/jetty/configure.dtd" >
    <Configure class="org.eclipse.jetty.webapp.WebAppContext">
        <Get name="server">
          <Call name="addConnector">
            <Arg>
              <New class="org.eclipse.jetty.server.nio.SelectChannelConnector">
               <Set name="port"><Property name="jetty.port" default="8065"/></Set>
              </New>
            </Arg>
          </Call>
        </Get>
    </Configure>

    8065 should be replaced with the additional port you'd like to listen on. This port must not conflict with any other ports being used on the server or those already being used by Fisheye/Crucible.

  3. Start Fisheye/Crucible

Last modified on Jul 31, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.