You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Greg Wilkins (JIRA)" <de...@geronimo.apache.org> on 2006/01/14 15:38:20 UTC
[jira] Created: (GERONIMO-1471) Connector dependencies
Connector dependencies
----------------------
Key: GERONIMO-1471
URL: http://issues.apache.org/jira/browse/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 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 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1471) Connector dependencies
Posted by "Prasad Kashyap (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prasad Kashyap updated GERONIMO-1471:
-------------------------------------
Fix Version/s: (was: 2.0-M5)
2.0
> Connector dependencies
> ----------------------
>
> Key: GERONIMO-1471
> URL: https://issues.apache.org/jira/browse/GERONIMO-1471
> 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: 1.x, 2.0
>
>
> 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 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-1471) Connector dependencies
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1471?page=all ]
David Jencks updated GERONIMO-1471:
-----------------------------------
Component: (was: connector)
this does not relate to j2ca connectors
> Connector dependencies
> ----------------------
>
> Key: GERONIMO-1471
> URL: http://issues.apache.org/jira/browse/GERONIMO-1471
> 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 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1471) Connector dependencies
Posted by "Matt Hogstrom (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1471?page=all ]
Matt Hogstrom updated GERONIMO-1471:
------------------------------------
Fix Version/s: 1.x
2.0
(was: 1.2)
> Connector dependencies
> ----------------------
>
> Key: GERONIMO-1471
> URL: http://issues.apache.org/jira/browse/GERONIMO-1471
> 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
> Assigned To: Greg Wilkins
> Fix For: 1.x, 2.0
>
>
> 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 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1471) Connector dependencies
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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: https://issues.apache.org/jira/browse/GERONIMO-1471
> 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 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.
-
You can reply to this email to add a comment to the issue online.