geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Updated: (GERONIMO-1471) Connector dependencies
Date Wed, 01 Feb 2006 22:39:15 GMT
     [ ]

David Jencks updated GERONIMO-1471:

    Component:     (was: connector)

this does not relate to j2ca connectors

> Connector dependencies
> ----------------------
>          Key: GERONIMO-1471
>          URL:
>      Project: Geronimo
>         Type: Improvement
>   Components: Clustering, Tomcat, web
>  Environment: Deploying a web application in a cluster.
>     Reporter: Greg Wilkins
>     Assignee: 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 update.
> 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
>    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