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 Fri, 27 Jul 2007 03:54:03 GMT


David Jencks updated GERONIMO-1471:

    Fix Version/s:     (was: 1.x)
                       (was: 2.0)
                   Wish List

GBean dependencies can work only if the connector is not in with the web container but rather
in with the web app that requires it or a child configuration of all the web apps that require
it.  I think this is the most satisfactory solution as otherwise we will be introducing some
kind of "started but not running state" that might be hard to understand.

> Connector dependencies
> ----------------------
>                 Key: GERONIMO-1471
>                 URL:
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: Clustering, Tomcat, web
>         Environment: Deploying a web application in a cluster.
>            Reporter: Greg Wilkins
>            Assignee: Greg Wilkins
>             Fix For: Wish List
> 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.
You can reply to this email to add a comment to the issue online.

View raw message