WAIT_FOR_BEFORE_START does not work for / context applications

Solution Verified - Updated -

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.2.0

Issue

  • We were trying to avoid connectors starting before our application, which is deployed to the root context. We tried using the WAIT_FOR_BEFORE_START property added in EAP 6.2.0 to correct this and so set it to the / context:

    ./standalone.sh -Dorg.apache.catalina.connector.WAIT_FOR_BEFORE_START=/

    The connectors never start with this set though even after our / context application is deployed.

Resolution

  • Upgrade to EAP 6.2.1+
  • As a workaround, don't deploy your application to the / context. You could instead use a rewrite rule to rewrite traffic from / to the /application context to fulfil both needs.

Root Cause

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.