geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Wilkins (JIRA)" <>
Subject [jira] Created: (GERONIMO-1471) Connector dependencies
Date Sat, 14 Jan 2006 14:38:20 GMT
Connector dependencies

         Key: GERONIMO-1471
     Project: Geronimo
        Type: Improvement
  Components: Clustering, connector, Tomcat, web  
 Environment: Deploying a web application in a cluster.
    Reporter: Greg Wilkins
 Assigned to: Greg Wilkins 
     Fix For: 1.1

It is highly desirable that the HTTP connectors can be made dependent on the correct startup
of one or more webapplications.   This is to prevent a server with failed webapps to join
a cluster, or for
it a server to join a cluster before required webapplications are fully deployed.

It should be possible to add GBean dependancies in the web container plans, however an opinion
has been expressed that this is not flexible enough and would be difficult to configure and
So a specific mechanism has been proposed.

Issues to consider are:

 + How should the dependencies be expressed: specific webapp, all webapps, 
    number of webapps?

 + Where should they be expressed?  In the container plan, or perhaps as some
    form or required webapp flag in the geronimo-web.xml ?

 + If the dependencies are not meet, what state should the connector be in?  Should it be
   just not be started, or should it start, but have internal state (eg open/closed)  as this

   would allow a future conversation with advanced load balancers.

 + Should the server port be opened - but no requests accepted?   This will reserver
    the port and verify that no other resource is using it while the webapps are started.
    Need to verify that this will not upset any load balancers.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message