Question

We have a Nexus server which worked fine until friday. Nexus was stopped and since we are unable to start it again but I can’t figure out why ?

I think it’s a Jetty problem. Here is the stack strace:

jvm 1    | 2012-08-13 09:31:10 WARN  [er_start_runner] - org.mortbay.log - failed SelectChannelConnector@*:8080
jvm 1    | java.net.SocketException: Unresolved address
jvm 1    |  at sun.nio.ch.Net.translateToSocketException(Net.java:58)
jvm 1    |  at sun.nio.ch.Net.translateException(Net.java:84)
jvm 1    |  at sun.nio.ch.Net.translateException(Net.java:90)
jvm 1    |  at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:61)
jvm 1    |  at org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:216)

The configuration is (jetty.xml):

<Configure id="Server" class="org.mortbay.jetty.Server">
    <Call name="addConnector">
        <Arg>
            <New class="org.mortbay.jetty.nio.SelectChannelConnector">
              <Set name="host">${application-host}</Set>
              <Set name="port">${application-port}</Set>
            </New>
        </Arg>
    </Call>

    <Set name="handler">
      <New id="Contexts" class="org.mortbay.jetty.handler.ContextHandlerCollection">
          <!-- The following configuration is REQUIRED, and MUST BE FIRST. 
               It makes the Plexus container available for use in the Nexus webapp. -->
          <Call name="addLifeCycleListener">
              <Arg>
                <New class="org.sonatype.plexus.jetty.custom.InjectExistingPlexusListener" />
              </Arg>
          </Call>

          <!-- The following configuration disables JSP taglib support, the validation of which
               slows down Jetty's startup significantly. -->
          <Call name="addLifeCycleListener">
              <Arg>
                <New class="org.sonatype.plexus.jetty.custom.DisableTagLibsListener" />
              </Arg>
          </Call>
      </New>
    </Set>

    <New id="NexusWebAppContext" class="org.mortbay.jetty.webapp.WebAppContext">
      <Arg><Ref id="Contexts"/></Arg>
      <Arg>${webapp}</Arg>
      <Arg>${webapp-context-path}</Arg>
      <Set name="extractWAR">false</Set>
    </New>

    <Set name="stopAtShutdown">true</Set>
    <Set name="sendServerVersion">true</Set>
    <Set name="sendDateHeader">true</Set>
    <Set name="gracefulShutdown">1000</Set>
</Configure>

and the plexus.properties:

application-port=8081
application-host=0.0.0.0
runtime=${basedir}/runtime
apps=${runtime}/apps
nexus-work=${basedir}/../../data/nexus/sonatype-work/nexus
nexus-app=${runtime}/apps/nexus
webapp=${runtime}/apps/nexus/webapp
webapp-context-path=/nexus
security-xml-file=${nexus-work}/conf/security.xml
application-conf=${nexus-work}/conf
runtime-tmp=${runtime}/tmp

# If this file is present, it will be used to configure Jetty.
jetty.xml=${basedir}/conf/jetty.xml

# Uncomment this to use the debug js files
#index.template.file=templates/index-debug.vm

Nexus version is 1.9.2.3

I can’t understand:
why it wants to start a connector at port 8080 (while I only set port 8081) and
what means the address * (and why not 0.0.0.0) ? And of course why it doesn’t want to start anymore ?

Thanks a lot for all your ideas!

Answer 1

Solved!

The file jetty.xml had only the ‘r’ permission which is not enough: it must have the ‘x’ permission too. So Jetty was unable to read the file jetty.xml and in that case it tries to start a default connector on ‘*:8080’ => * is not resolvable (I don’t know why they used * instead of 0.0.0.0 ???)

So it was a configuration issue.