[jira] Updated: (GERONIMO-2163) WADI Integration for Jetty
[ http://issues.apache.org/jira/browse/GERONIMO-2163?page=all ] Greg Wilkins updated GERONIMO-2163: --- Attachment: GERONIMO-2163-v6c.patch This is just an update to v6b so that it applies to r439349 > WADI Integration for Jetty > -- > > Key: GERONIMO-2163 > URL: http://issues.apache.org/jira/browse/GERONIMO-2163 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Clustering >Reporter: Gianny Damour > Assigned To: Gianny Damour >Priority: Minor > Attachments: GERONIMO-2163-v3.patch, GERONIMO-2163-v3b.patch, > GERONIMO-2163-v4-old.patch, GERONIMO-2163-v4.patch, > GERONIMO-2163-v5-partial.patch, GERONIMO-2163-v5-plus.patch, > GERONIMO-2163-v6.patch, GERONIMO-2163-v6b.patch, GERONIMO-2163-v6c.patch, > geronimo-wadi-integration-preview.patch, geronimo-wadi-integration-RTC.patch, > geronimo.patch, setUpServers.tar.gz, wadi-geronimo-integration-preview.patch, > wadi.patch, wadi.zip > > > Email sent to the dev@ list. > Hi, > I have been working on a second integration attempt of WADI and I am posting > here a high-level description of the current state of progress such that > people can jump in. > At this stage, this is a Jetty only attempt and I do believe that the same > approach can be applied for Tomcat. The current integration provides (very > unreliable) HttpSession state migration. It only works for a single > Web-application; more effort is required on the WADI side to support multiple > Web-applications and this will not impact the integration piece of code. I > (more or less successfully) tested the integration with mod_proxy + > mod_proxy_balancer and mod_proxy + mod_rewrite in front of three Geronimo > servers running the WADI demo web-app. > The code changes are: > * new module to capture some clustering contracts - geronimo-clustering: > there Node, SessionManager, Session and ClusteredInvocation are defined. > * new module to provide a WADI implementation of the above - > geronimo-clustering-wadi; > * new module to capture clustering builder contracts - > geronimo-clustering-builder: there is only one interesting interface > JettyClusteringBuilder. This later defines a couple of methods to augment the > environment of a Web module being built and add clustering specific GBeans; > * new module to provide a WADI implementation of the above - > Geronimo-clustering-builder-wadi; and > * geronimo-jetty-builder and geronimo-jetty are impacted to hook in > clustering. These two modules depend on geronimo-clustering and > geronimo-clustering-builder and not on WADI specific modules. > Two new modules are added: > * jetty-clustering- wadi: this module defines default WADI GBeans such as > Dispatcher, ReplicationManagerFactory, BackingStrategyFactory et cetera; and > * jetty-clustering-builder-wadi: this module defines a builder to process > Jetty DD and add various GBeans to the module being built. > I think that the implementation is flexible enough to plug in another > clustering implementation such as Kache. > As a matter of fact, there are some severe reliability (e.g. locking issues) > and integration (only one Web-app can be clustered) issues, which need to be > fixed. So, this work is not yet ready to be RTC voted. Having said that, I > have opened a JIRA such that people can have a look to the integration. > Thanks, > Gianny -- 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-2163) WADI Integration for Jetty
[ http://issues.apache.org/jira/browse/GERONIMO-2163?page=all ] David Jencks updated GERONIMO-2163: --- Attachment: GERONIMO-2163-v6b.patch My patch fixes a couple of bugs in gianni's patch 6. - the jndi environment construction got broken -- no kernel aware references were working. - Avoid an npe when is present but no clustering builder is installed. The behavior with NamespaceDrivenBuilders is slightly different than with Gianni's original approach. Previously the wadi builder would use defaults if no wadi config was specified. In the NDB implementation, at least a single element in the wadi-cluster namespace is needed to start the builder. > WADI Integration for Jetty > -- > > Key: GERONIMO-2163 > URL: http://issues.apache.org/jira/browse/GERONIMO-2163 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Clustering >Reporter: Gianny Damour > Assigned To: Gianny Damour >Priority: Minor > Attachments: GERONIMO-2163-v3.patch, GERONIMO-2163-v3b.patch, > GERONIMO-2163-v4-old.patch, GERONIMO-2163-v4.patch, > GERONIMO-2163-v5-partial.patch, GERONIMO-2163-v5-plus.patch, > GERONIMO-2163-v6.patch, GERONIMO-2163-v6b.patch, > geronimo-wadi-integration-preview.patch, geronimo-wadi-integration-RTC.patch, > geronimo.patch, setUpServers.tar.gz, wadi-geronimo-integration-preview.patch, > wadi.patch, wadi.zip > > > Email sent to the dev@ list. > Hi, > I have been working on a second integration attempt of WADI and I am posting > here a high-level description of the current state of progress such that > people can jump in. > At this stage, this is a Jetty only attempt and I do believe that the same > approach can be applied for Tomcat. The current integration provides (very > unreliable) HttpSession state migration. It only works for a single > Web-application; more effort is required on the WADI side to support multiple > Web-applications and this will not impact the integration piece of code. I > (more or less successfully) tested the integration with mod_proxy + > mod_proxy_balancer and mod_proxy + mod_rewrite in front of three Geronimo > servers running the WADI demo web-app. > The code changes are: > * new module to capture some clustering contracts - geronimo-clustering: > there Node, SessionManager, Session and ClusteredInvocation are defined. > * new module to provide a WADI implementation of the above - > geronimo-clustering-wadi; > * new module to capture clustering builder contracts - > geronimo-clustering-builder: there is only one interesting interface > JettyClusteringBuilder. This later defines a couple of methods to augment the > environment of a Web module being built and add clustering specific GBeans; > * new module to provide a WADI implementation of the above - > Geronimo-clustering-builder-wadi; and > * geronimo-jetty-builder and geronimo-jetty are impacted to hook in > clustering. These two modules depend on geronimo-clustering and > geronimo-clustering-builder and not on WADI specific modules. > Two new modules are added: > * jetty-clustering- wadi: this module defines default WADI GBeans such as > Dispatcher, ReplicationManagerFactory, BackingStrategyFactory et cetera; and > * jetty-clustering-builder-wadi: this module defines a builder to process > Jetty DD and add various GBeans to the module being built. > I think that the implementation is flexible enough to plug in another > clustering implementation such as Kache. > As a matter of fact, there are some severe reliability (e.g. locking issues) > and integration (only one Web-app can be clustered) issues, which need to be > fixed. So, this work is not yet ready to be RTC voted. Having said that, I > have opened a JIRA such that people can have a look to the integration. > Thanks, > Gianny -- 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-2163) WADI Integration for Jetty
[ http://issues.apache.org/jira/browse/GERONIMO-2163?page=all ] Gianny Damour updated GERONIMO-2163: Attachment: GERONIMO-2163-v6.patch Many thanks for having fixed the namespace driven builder. It is now working nicely and I have been able to deploy the WADI demo web-app and also the one that you attached. I attach a new patch, v6, which is v5-partial + some minor tweaks. Regarding the console being flaky, I am trying to reproduce. Basically, I log in, navigate a couple of screens, and then log out. So far, it is working fine. Is there a specific thing that I should be do observe this problem? > WADI Integration for Jetty > -- > > Key: GERONIMO-2163 > URL: http://issues.apache.org/jira/browse/GERONIMO-2163 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Clustering >Reporter: Gianny Damour > Assigned To: Gianny Damour >Priority: Minor > Attachments: GERONIMO-2163-v3.patch, GERONIMO-2163-v3b.patch, > GERONIMO-2163-v4-old.patch, GERONIMO-2163-v4.patch, > GERONIMO-2163-v5-partial.patch, GERONIMO-2163-v5-plus.patch, > GERONIMO-2163-v6.patch, geronimo-wadi-integration-preview.patch, > geronimo-wadi-integration-RTC.patch, geronimo.patch, setUpServers.tar.gz, > wadi-geronimo-integration-preview.patch, wadi.patch, wadi.zip > > > Email sent to the dev@ list. > Hi, > I have been working on a second integration attempt of WADI and I am posting > here a high-level description of the current state of progress such that > people can jump in. > At this stage, this is a Jetty only attempt and I do believe that the same > approach can be applied for Tomcat. The current integration provides (very > unreliable) HttpSession state migration. It only works for a single > Web-application; more effort is required on the WADI side to support multiple > Web-applications and this will not impact the integration piece of code. I > (more or less successfully) tested the integration with mod_proxy + > mod_proxy_balancer and mod_proxy + mod_rewrite in front of three Geronimo > servers running the WADI demo web-app. > The code changes are: > * new module to capture some clustering contracts - geronimo-clustering: > there Node, SessionManager, Session and ClusteredInvocation are defined. > * new module to provide a WADI implementation of the above - > geronimo-clustering-wadi; > * new module to capture clustering builder contracts - > geronimo-clustering-builder: there is only one interesting interface > JettyClusteringBuilder. This later defines a couple of methods to augment the > environment of a Web module being built and add clustering specific GBeans; > * new module to provide a WADI implementation of the above - > Geronimo-clustering-builder-wadi; and > * geronimo-jetty-builder and geronimo-jetty are impacted to hook in > clustering. These two modules depend on geronimo-clustering and > geronimo-clustering-builder and not on WADI specific modules. > Two new modules are added: > * jetty-clustering- wadi: this module defines default WADI GBeans such as > Dispatcher, ReplicationManagerFactory, BackingStrategyFactory et cetera; and > * jetty-clustering-builder-wadi: this module defines a builder to process > Jetty DD and add various GBeans to the module being built. > I think that the implementation is flexible enough to plug in another > clustering implementation such as Kache. > As a matter of fact, there are some severe reliability (e.g. locking issues) > and integration (only one Web-app can be clustered) issues, which need to be > fixed. So, this work is not yet ready to be RTC voted. Having said that, I > have opened a JIRA such that people can have a look to the integration. > Thanks, > Gianny -- 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-2163) WADI Integration for Jetty
[ http://issues.apache.org/jira/browse/GERONIMO-2163?page=all ] David Jencks updated GERONIMO-2163: --- Attachment: wadi.zip GERONIMO-2163-v5-partial.patch GERONIMO-2163-v5-plus.patch I fixed the problem in the namespace builder, but there's still a problem depllying my sample app (attached). I also fixed the dislocated files. I'm running out of time, so I've included a new patch (partial) that just has geronimo-jetty-builder and geronimo-clustering-builder-wadi. If theres anything missing it should be in the -plus patch which also has some work I'm doing locally that isn't part of this rtc. Will try to investigate further. The console is still extremely flaky under jetty + wadi, even without wadi running. > WADI Integration for Jetty > -- > > Key: GERONIMO-2163 > URL: http://issues.apache.org/jira/browse/GERONIMO-2163 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Clustering >Reporter: Gianny Damour > Assigned To: Gianny Damour >Priority: Minor > Attachments: GERONIMO-2163-v3.patch, GERONIMO-2163-v3b.patch, > GERONIMO-2163-v4-old.patch, GERONIMO-2163-v4.patch, > GERONIMO-2163-v5-partial.patch, GERONIMO-2163-v5-plus.patch, > geronimo-wadi-integration-preview.patch, geronimo-wadi-integration-RTC.patch, > geronimo.patch, setUpServers.tar.gz, wadi-geronimo-integration-preview.patch, > wadi.patch, wadi.zip > > > Email sent to the dev@ list. > Hi, > I have been working on a second integration attempt of WADI and I am posting > here a high-level description of the current state of progress such that > people can jump in. > At this stage, this is a Jetty only attempt and I do believe that the same > approach can be applied for Tomcat. The current integration provides (very > unreliable) HttpSession state migration. It only works for a single > Web-application; more effort is required on the WADI side to support multiple > Web-applications and this will not impact the integration piece of code. I > (more or less successfully) tested the integration with mod_proxy + > mod_proxy_balancer and mod_proxy + mod_rewrite in front of three Geronimo > servers running the WADI demo web-app. > The code changes are: > * new module to capture some clustering contracts - geronimo-clustering: > there Node, SessionManager, Session and ClusteredInvocation are defined. > * new module to provide a WADI implementation of the above - > geronimo-clustering-wadi; > * new module to capture clustering builder contracts - > geronimo-clustering-builder: there is only one interesting interface > JettyClusteringBuilder. This later defines a couple of methods to augment the > environment of a Web module being built and add clustering specific GBeans; > * new module to provide a WADI implementation of the above - > Geronimo-clustering-builder-wadi; and > * geronimo-jetty-builder and geronimo-jetty are impacted to hook in > clustering. These two modules depend on geronimo-clustering and > geronimo-clustering-builder and not on WADI specific modules. > Two new modules are added: > * jetty-clustering- wadi: this module defines default WADI GBeans such as > Dispatcher, ReplicationManagerFactory, BackingStrategyFactory et cetera; and > * jetty-clustering-builder-wadi: this module defines a builder to process > Jetty DD and add various GBeans to the module being built. > I think that the implementation is flexible enough to plug in another > clustering implementation such as Kache. > As a matter of fact, there are some severe reliability (e.g. locking issues) > and integration (only one Web-app can be clustered) issues, which need to be > fixed. So, this work is not yet ready to be RTC voted. Having said that, I > have opened a JIRA such that people can have a look to the integration. > Thanks, > Gianny -- 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-2163) WADI Integration for Jetty
[ http://issues.apache.org/jira/browse/GERONIMO-2163?page=all ] David Jencks updated GERONIMO-2163: --- Attachment: GERONIMO-2163-v4.patch GERONIMO-2163-v4-old.patch I've reworked the patch to use (newly improved) NamespaceDrivenBuilders instead of custom builder interfaces. This solves #2 (the most serious IMO) of the problems I mentioned previously, the dependency of jetty on a wadi module, and removes the need for the geronimo-cluster-builder module entirely. The v4 patch uses the new geronmo-* module names jason just installed. In case I missed something I'm also attaching v4-old that uses yesterday's layout. I'm still having problems with the console with this patch. Currently unless I set a breakpoint somewhere in g. the login page returns to the login page. If I hit a breakpoint it acts normally. I haven't been able to get the sample config working yet. It appears to be trying to connect to activecluster on port 61618, but nothing is running there. Please examine this work and vote (for it :-)! > WADI Integration for Jetty > -- > > Key: GERONIMO-2163 > URL: http://issues.apache.org/jira/browse/GERONIMO-2163 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Clustering >Reporter: Gianny Damour > Assigned To: Gianny Damour >Priority: Minor > Attachments: GERONIMO-2163-v3.patch, GERONIMO-2163-v3b.patch, > GERONIMO-2163-v4-old.patch, GERONIMO-2163-v4.patch, > geronimo-wadi-integration-preview.patch, geronimo-wadi-integration-RTC.patch, > geronimo.patch, setUpServers.tar.gz, wadi-geronimo-integration-preview.patch, > wadi.patch > > > Email sent to the dev@ list. > Hi, > I have been working on a second integration attempt of WADI and I am posting > here a high-level description of the current state of progress such that > people can jump in. > At this stage, this is a Jetty only attempt and I do believe that the same > approach can be applied for Tomcat. The current integration provides (very > unreliable) HttpSession state migration. It only works for a single > Web-application; more effort is required on the WADI side to support multiple > Web-applications and this will not impact the integration piece of code. I > (more or less successfully) tested the integration with mod_proxy + > mod_proxy_balancer and mod_proxy + mod_rewrite in front of three Geronimo > servers running the WADI demo web-app. > The code changes are: > * new module to capture some clustering contracts - geronimo-clustering: > there Node, SessionManager, Session and ClusteredInvocation are defined. > * new module to provide a WADI implementation of the above - > geronimo-clustering-wadi; > * new module to capture clustering builder contracts - > geronimo-clustering-builder: there is only one interesting interface > JettyClusteringBuilder. This later defines a couple of methods to augment the > environment of a Web module being built and add clustering specific GBeans; > * new module to provide a WADI implementation of the above - > Geronimo-clustering-builder-wadi; and > * geronimo-jetty-builder and geronimo-jetty are impacted to hook in > clustering. These two modules depend on geronimo-clustering and > geronimo-clustering-builder and not on WADI specific modules. > Two new modules are added: > * jetty-clustering- wadi: this module defines default WADI GBeans such as > Dispatcher, ReplicationManagerFactory, BackingStrategyFactory et cetera; and > * jetty-clustering-builder-wadi: this module defines a builder to process > Jetty DD and add various GBeans to the module being built. > I think that the implementation is flexible enough to plug in another > clustering implementation such as Kache. > As a matter of fact, there are some severe reliability (e.g. locking issues) > and integration (only one Web-app can be clustered) issues, which need to be > fixed. So, this work is not yet ready to be RTC voted. Having said that, I > have opened a JIRA such that people can have a look to the integration. > Thanks, > Gianny -- 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-2163) WADI Integration for Jetty
[ http://issues.apache.org/jira/browse/GERONIMO-2163?page=all ] David Jencks updated GERONIMO-2163: --- Attachment: GERONIMO-2163-v3b.patch Previous v3 patch ommitted the new configs, included here. > WADI Integration for Jetty > -- > > Key: GERONIMO-2163 > URL: http://issues.apache.org/jira/browse/GERONIMO-2163 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Clustering >Reporter: Gianny Damour > Assigned To: Gianny Damour >Priority: Minor > Attachments: GERONIMO-2163-v3.patch, GERONIMO-2163-v3b.patch, > geronimo-wadi-integration-preview.patch, geronimo-wadi-integration-RTC.patch, > geronimo.patch, setUpServers.tar.gz, wadi-geronimo-integration-preview.patch, > wadi.patch > > > Email sent to the dev@ list. > Hi, > I have been working on a second integration attempt of WADI and I am posting > here a high-level description of the current state of progress such that > people can jump in. > At this stage, this is a Jetty only attempt and I do believe that the same > approach can be applied for Tomcat. The current integration provides (very > unreliable) HttpSession state migration. It only works for a single > Web-application; more effort is required on the WADI side to support multiple > Web-applications and this will not impact the integration piece of code. I > (more or less successfully) tested the integration with mod_proxy + > mod_proxy_balancer and mod_proxy + mod_rewrite in front of three Geronimo > servers running the WADI demo web-app. > The code changes are: > * new module to capture some clustering contracts - geronimo-clustering: > there Node, SessionManager, Session and ClusteredInvocation are defined. > * new module to provide a WADI implementation of the above - > geronimo-clustering-wadi; > * new module to capture clustering builder contracts - > geronimo-clustering-builder: there is only one interesting interface > JettyClusteringBuilder. This later defines a couple of methods to augment the > environment of a Web module being built and add clustering specific GBeans; > * new module to provide a WADI implementation of the above - > Geronimo-clustering-builder-wadi; and > * geronimo-jetty-builder and geronimo-jetty are impacted to hook in > clustering. These two modules depend on geronimo-clustering and > geronimo-clustering-builder and not on WADI specific modules. > Two new modules are added: > * jetty-clustering- wadi: this module defines default WADI GBeans such as > Dispatcher, ReplicationManagerFactory, BackingStrategyFactory et cetera; and > * jetty-clustering-builder-wadi: this module defines a builder to process > Jetty DD and add various GBeans to the module being built. > I think that the implementation is flexible enough to plug in another > clustering implementation such as Kache. > As a matter of fact, there are some severe reliability (e.g. locking issues) > and integration (only one Web-app can be clustered) issues, which need to be > fixed. So, this work is not yet ready to be RTC voted. Having said that, I > have opened a JIRA such that people can have a look to the integration. > Thanks, > Gianny -- 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-2163) WADI Integration for Jetty
[ http://issues.apache.org/jira/browse/GERONIMO-2163?page=all ] David Jencks updated GERONIMO-2163: --- Attachment: GERONIMO-2163-v3.patch I've attached a patch modified to fit the new m2-compliant module layout. I approve of the basic direction of this patch and would be +1 to applying it. However I observed some problems that should probably be addressed first: 1. wadi-group is not available on the codehaus snapshot repo, I had to build it myself. 2. (most serious IMO) this introduces a dependency of jetty-builder on clustering-builder-wadi. This appears to require wadi to be present in order to use the jetty builder. If this can be turned into a test dependency it's not a problem: if not we may need some more dependency shuffling. 3. The console doesn't work for me. I can log in but every link from the welcome page leads back to the login page. I'll try to investigate these issues further. I think this is an important patch and I think we should apply it and work through the issues. > WADI Integration for Jetty > -- > > Key: GERONIMO-2163 > URL: http://issues.apache.org/jira/browse/GERONIMO-2163 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Clustering >Reporter: Gianny Damour > Assigned To: Gianny Damour >Priority: Minor > Attachments: GERONIMO-2163-v3.patch, > geronimo-wadi-integration-preview.patch, geronimo-wadi-integration-RTC.patch, > geronimo.patch, setUpServers.tar.gz, wadi-geronimo-integration-preview.patch, > wadi.patch > > > Email sent to the dev@ list. > Hi, > I have been working on a second integration attempt of WADI and I am posting > here a high-level description of the current state of progress such that > people can jump in. > At this stage, this is a Jetty only attempt and I do believe that the same > approach can be applied for Tomcat. The current integration provides (very > unreliable) HttpSession state migration. It only works for a single > Web-application; more effort is required on the WADI side to support multiple > Web-applications and this will not impact the integration piece of code. I > (more or less successfully) tested the integration with mod_proxy + > mod_proxy_balancer and mod_proxy + mod_rewrite in front of three Geronimo > servers running the WADI demo web-app. > The code changes are: > * new module to capture some clustering contracts - geronimo-clustering: > there Node, SessionManager, Session and ClusteredInvocation are defined. > * new module to provide a WADI implementation of the above - > geronimo-clustering-wadi; > * new module to capture clustering builder contracts - > geronimo-clustering-builder: there is only one interesting interface > JettyClusteringBuilder. This later defines a couple of methods to augment the > environment of a Web module being built and add clustering specific GBeans; > * new module to provide a WADI implementation of the above - > Geronimo-clustering-builder-wadi; and > * geronimo-jetty-builder and geronimo-jetty are impacted to hook in > clustering. These two modules depend on geronimo-clustering and > geronimo-clustering-builder and not on WADI specific modules. > Two new modules are added: > * jetty-clustering- wadi: this module defines default WADI GBeans such as > Dispatcher, ReplicationManagerFactory, BackingStrategyFactory et cetera; and > * jetty-clustering-builder-wadi: this module defines a builder to process > Jetty DD and add various GBeans to the module being built. > I think that the implementation is flexible enough to plug in another > clustering implementation such as Kache. > As a matter of fact, there are some severe reliability (e.g. locking issues) > and integration (only one Web-app can be clustered) issues, which need to be > fixed. So, this work is not yet ready to be RTC voted. Having said that, I > have opened a JIRA such that people can have a look to the integration. > Thanks, > Gianny -- 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-2163) WADI Integration for Jetty
[ http://issues.apache.org/jira/browse/GERONIMO-2163?page=all ] Gianny Damour updated GERONIMO-2163: Attachment: setUpServers.tar.gz Used to set-up two Geronimo server instances. > WADI Integration for Jetty > -- > > Key: GERONIMO-2163 > URL: http://issues.apache.org/jira/browse/GERONIMO-2163 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Clustering >Reporter: Gianny Damour > Assigned To: Gianny Damour >Priority: Minor > Attachments: geronimo-wadi-integration-preview.patch, > geronimo-wadi-integration-RTC.patch, geronimo.patch, setUpServers.tar.gz, > wadi-geronimo-integration-preview.patch, wadi.patch > > > Email sent to the dev@ list. > Hi, > I have been working on a second integration attempt of WADI and I am posting > here a high-level description of the current state of progress such that > people can jump in. > At this stage, this is a Jetty only attempt and I do believe that the same > approach can be applied for Tomcat. The current integration provides (very > unreliable) HttpSession state migration. It only works for a single > Web-application; more effort is required on the WADI side to support multiple > Web-applications and this will not impact the integration piece of code. I > (more or less successfully) tested the integration with mod_proxy + > mod_proxy_balancer and mod_proxy + mod_rewrite in front of three Geronimo > servers running the WADI demo web-app. > The code changes are: > * new module to capture some clustering contracts - geronimo-clustering: > there Node, SessionManager, Session and ClusteredInvocation are defined. > * new module to provide a WADI implementation of the above - > geronimo-clustering-wadi; > * new module to capture clustering builder contracts - > geronimo-clustering-builder: there is only one interesting interface > JettyClusteringBuilder. This later defines a couple of methods to augment the > environment of a Web module being built and add clustering specific GBeans; > * new module to provide a WADI implementation of the above - > Geronimo-clustering-builder-wadi; and > * geronimo-jetty-builder and geronimo-jetty are impacted to hook in > clustering. These two modules depend on geronimo-clustering and > geronimo-clustering-builder and not on WADI specific modules. > Two new modules are added: > * jetty-clustering- wadi: this module defines default WADI GBeans such as > Dispatcher, ReplicationManagerFactory, BackingStrategyFactory et cetera; and > * jetty-clustering-builder-wadi: this module defines a builder to process > Jetty DD and add various GBeans to the module being built. > I think that the implementation is flexible enough to plug in another > clustering implementation such as Kache. > As a matter of fact, there are some severe reliability (e.g. locking issues) > and integration (only one Web-app can be clustered) issues, which need to be > fixed. So, this work is not yet ready to be RTC voted. Having said that, I > have opened a JIRA such that people can have a look to the integration. > Thanks, > Gianny -- 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-2163) WADI Integration for Jetty
[ http://issues.apache.org/jira/browse/GERONIMO-2163?page=all ] Gianny Damour updated GERONIMO-2163: Attachment: geronimo-wadi-integration-RTC.patch Patch for RTC. > WADI Integration for Jetty > -- > > Key: GERONIMO-2163 > URL: http://issues.apache.org/jira/browse/GERONIMO-2163 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Clustering >Reporter: Gianny Damour > Assigned To: Gianny Damour >Priority: Minor > Attachments: geronimo-wadi-integration-preview.patch, > geronimo-wadi-integration-RTC.patch, geronimo.patch, > wadi-geronimo-integration-preview.patch, wadi.patch > > > Email sent to the dev@ list. > Hi, > I have been working on a second integration attempt of WADI and I am posting > here a high-level description of the current state of progress such that > people can jump in. > At this stage, this is a Jetty only attempt and I do believe that the same > approach can be applied for Tomcat. The current integration provides (very > unreliable) HttpSession state migration. It only works for a single > Web-application; more effort is required on the WADI side to support multiple > Web-applications and this will not impact the integration piece of code. I > (more or less successfully) tested the integration with mod_proxy + > mod_proxy_balancer and mod_proxy + mod_rewrite in front of three Geronimo > servers running the WADI demo web-app. > The code changes are: > * new module to capture some clustering contracts - geronimo-clustering: > there Node, SessionManager, Session and ClusteredInvocation are defined. > * new module to provide a WADI implementation of the above - > geronimo-clustering-wadi; > * new module to capture clustering builder contracts - > geronimo-clustering-builder: there is only one interesting interface > JettyClusteringBuilder. This later defines a couple of methods to augment the > environment of a Web module being built and add clustering specific GBeans; > * new module to provide a WADI implementation of the above - > Geronimo-clustering-builder-wadi; and > * geronimo-jetty-builder and geronimo-jetty are impacted to hook in > clustering. These two modules depend on geronimo-clustering and > geronimo-clustering-builder and not on WADI specific modules. > Two new modules are added: > * jetty-clustering- wadi: this module defines default WADI GBeans such as > Dispatcher, ReplicationManagerFactory, BackingStrategyFactory et cetera; and > * jetty-clustering-builder-wadi: this module defines a builder to process > Jetty DD and add various GBeans to the module being built. > I think that the implementation is flexible enough to plug in another > clustering implementation such as Kache. > As a matter of fact, there are some severe reliability (e.g. locking issues) > and integration (only one Web-app can be clustered) issues, which need to be > fixed. So, this work is not yet ready to be RTC voted. Having said that, I > have opened a JIRA such that people can have a look to the integration. > Thanks, > Gianny -- 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-2163) WADI Integration for Jetty
[ http://issues.apache.org/jira/browse/GERONIMO-2163?page=all ] Gianny Damour updated GERONIMO-2163: Attachment: wadi.patch Refreshed WADI patch. > WADI Integration for Jetty > -- > > Key: GERONIMO-2163 > URL: http://issues.apache.org/jira/browse/GERONIMO-2163 > Project: Geronimo > Type: New Feature > Security: public(Regular issues) > Components: Clustering > Reporter: Gianny Damour > Assignee: Gianny Damour > Priority: Minor > Attachments: geronimo-wadi-integration-preview.patch, geronimo.patch, > wadi-geronimo-integration-preview.patch, wadi.patch > > Email sent to the dev@ list. > Hi, > I have been working on a second integration attempt of WADI and I am posting > here a high-level description of the current state of progress such that > people can jump in. > At this stage, this is a Jetty only attempt and I do believe that the same > approach can be applied for Tomcat. The current integration provides (very > unreliable) HttpSession state migration. It only works for a single > Web-application; more effort is required on the WADI side to support multiple > Web-applications and this will not impact the integration piece of code. I > (more or less successfully) tested the integration with mod_proxy + > mod_proxy_balancer and mod_proxy + mod_rewrite in front of three Geronimo > servers running the WADI demo web-app. > The code changes are: > * new module to capture some clustering contracts - geronimo-clustering: > there Node, SessionManager, Session and ClusteredInvocation are defined. > * new module to provide a WADI implementation of the above - > geronimo-clustering-wadi; > * new module to capture clustering builder contracts - > geronimo-clustering-builder: there is only one interesting interface > JettyClusteringBuilder. This later defines a couple of methods to augment the > environment of a Web module being built and add clustering specific GBeans; > * new module to provide a WADI implementation of the above - > Geronimo-clustering-builder-wadi; and > * geronimo-jetty-builder and geronimo-jetty are impacted to hook in > clustering. These two modules depend on geronimo-clustering and > geronimo-clustering-builder and not on WADI specific modules. > Two new modules are added: > * jetty-clustering- wadi: this module defines default WADI GBeans such as > Dispatcher, ReplicationManagerFactory, BackingStrategyFactory et cetera; and > * jetty-clustering-builder-wadi: this module defines a builder to process > Jetty DD and add various GBeans to the module being built. > I think that the implementation is flexible enough to plug in another > clustering implementation such as Kache. > As a matter of fact, there are some severe reliability (e.g. locking issues) > and integration (only one Web-app can be clustered) issues, which need to be > fixed. So, this work is not yet ready to be RTC voted. Having said that, I > have opened a JIRA such that people can have a look to the integration. > Thanks, > Gianny -- 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-2163) WADI Integration for Jetty
[ http://issues.apache.org/jira/browse/GERONIMO-2163?page=all ] Gianny Damour updated GERONIMO-2163: Attachment: geronimo.patch Refreshed Geronimo patch against trunk > WADI Integration for Jetty > -- > > Key: GERONIMO-2163 > URL: http://issues.apache.org/jira/browse/GERONIMO-2163 > Project: Geronimo > Type: New Feature > Security: public(Regular issues) > Components: Clustering > Reporter: Gianny Damour > Assignee: Gianny Damour > Priority: Minor > Attachments: geronimo-wadi-integration-preview.patch, geronimo.patch, > wadi-geronimo-integration-preview.patch > > Email sent to the dev@ list. > Hi, > I have been working on a second integration attempt of WADI and I am posting > here a high-level description of the current state of progress such that > people can jump in. > At this stage, this is a Jetty only attempt and I do believe that the same > approach can be applied for Tomcat. The current integration provides (very > unreliable) HttpSession state migration. It only works for a single > Web-application; more effort is required on the WADI side to support multiple > Web-applications and this will not impact the integration piece of code. I > (more or less successfully) tested the integration with mod_proxy + > mod_proxy_balancer and mod_proxy + mod_rewrite in front of three Geronimo > servers running the WADI demo web-app. > The code changes are: > * new module to capture some clustering contracts - geronimo-clustering: > there Node, SessionManager, Session and ClusteredInvocation are defined. > * new module to provide a WADI implementation of the above - > geronimo-clustering-wadi; > * new module to capture clustering builder contracts - > geronimo-clustering-builder: there is only one interesting interface > JettyClusteringBuilder. This later defines a couple of methods to augment the > environment of a Web module being built and add clustering specific GBeans; > * new module to provide a WADI implementation of the above - > Geronimo-clustering-builder-wadi; and > * geronimo-jetty-builder and geronimo-jetty are impacted to hook in > clustering. These two modules depend on geronimo-clustering and > geronimo-clustering-builder and not on WADI specific modules. > Two new modules are added: > * jetty-clustering- wadi: this module defines default WADI GBeans such as > Dispatcher, ReplicationManagerFactory, BackingStrategyFactory et cetera; and > * jetty-clustering-builder-wadi: this module defines a builder to process > Jetty DD and add various GBeans to the module being built. > I think that the implementation is flexible enough to plug in another > clustering implementation such as Kache. > As a matter of fact, there are some severe reliability (e.g. locking issues) > and integration (only one Web-app can be clustered) issues, which need to be > fixed. So, this work is not yet ready to be RTC voted. Having said that, I > have opened a JIRA such that people can have a look to the integration. > Thanks, > Gianny -- 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-2163) WADI Integration for Jetty
[ http://issues.apache.org/jira/browse/GERONIMO-2163?page=all ] Gianny Damour updated GERONIMO-2163: Attachment: wadi-geronimo-integration-preview.patch WADI patch to integrate more nicely with Geronimo. > WADI Integration for Jetty > -- > > Key: GERONIMO-2163 > URL: http://issues.apache.org/jira/browse/GERONIMO-2163 > Project: Geronimo > Type: New Feature > Security: public(Regular issues) > Components: Clustering > Reporter: Gianny Damour > Assignee: Gianny Damour > Priority: Minor > Attachments: geronimo-wadi-integration-preview.patch, > wadi-geronimo-integration-preview.patch > > Email sent to the dev@ list. > Hi, > I have been working on a second integration attempt of WADI and I am posting > here a high-level description of the current state of progress such that > people can jump in. > At this stage, this is a Jetty only attempt and I do believe that the same > approach can be applied for Tomcat. The current integration provides (very > unreliable) HttpSession state migration. It only works for a single > Web-application; more effort is required on the WADI side to support multiple > Web-applications and this will not impact the integration piece of code. I > (more or less successfully) tested the integration with mod_proxy + > mod_proxy_balancer and mod_proxy + mod_rewrite in front of three Geronimo > servers running the WADI demo web-app. > The code changes are: > * new module to capture some clustering contracts - geronimo-clustering: > there Node, SessionManager, Session and ClusteredInvocation are defined. > * new module to provide a WADI implementation of the above - > geronimo-clustering-wadi; > * new module to capture clustering builder contracts - > geronimo-clustering-builder: there is only one interesting interface > JettyClusteringBuilder. This later defines a couple of methods to augment the > environment of a Web module being built and add clustering specific GBeans; > * new module to provide a WADI implementation of the above - > Geronimo-clustering-builder-wadi; and > * geronimo-jetty-builder and geronimo-jetty are impacted to hook in > clustering. These two modules depend on geronimo-clustering and > geronimo-clustering-builder and not on WADI specific modules. > Two new modules are added: > * jetty-clustering- wadi: this module defines default WADI GBeans such as > Dispatcher, ReplicationManagerFactory, BackingStrategyFactory et cetera; and > * jetty-clustering-builder-wadi: this module defines a builder to process > Jetty DD and add various GBeans to the module being built. > I think that the implementation is flexible enough to plug in another > clustering implementation such as Kache. > As a matter of fact, there are some severe reliability (e.g. locking issues) > and integration (only one Web-app can be clustered) issues, which need to be > fixed. So, this work is not yet ready to be RTC voted. Having said that, I > have opened a JIRA such that people can have a look to the integration. > Thanks, > Gianny -- 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-2163) WADI Integration for Jetty
[ http://issues.apache.org/jira/browse/GERONIMO-2163?page=all ] Gianny Damour updated GERONIMO-2163: Attachment: geronimo-wadi-integration-preview.patch Geronimo patch to integration WADI. > WADI Integration for Jetty > -- > > Key: GERONIMO-2163 > URL: http://issues.apache.org/jira/browse/GERONIMO-2163 > Project: Geronimo > Type: New Feature > Security: public(Regular issues) > Components: Clustering > Reporter: Gianny Damour > Assignee: Gianny Damour > Priority: Minor > Attachments: geronimo-wadi-integration-preview.patch > > Email sent to the dev@ list. > Hi, > I have been working on a second integration attempt of WADI and I am posting > here a high-level description of the current state of progress such that > people can jump in. > At this stage, this is a Jetty only attempt and I do believe that the same > approach can be applied for Tomcat. The current integration provides (very > unreliable) HttpSession state migration. It only works for a single > Web-application; more effort is required on the WADI side to support multiple > Web-applications and this will not impact the integration piece of code. I > (more or less successfully) tested the integration with mod_proxy + > mod_proxy_balancer and mod_proxy + mod_rewrite in front of three Geronimo > servers running the WADI demo web-app. > The code changes are: > * new module to capture some clustering contracts - geronimo-clustering: > there Node, SessionManager, Session and ClusteredInvocation are defined. > * new module to provide a WADI implementation of the above - > geronimo-clustering-wadi; > * new module to capture clustering builder contracts - > geronimo-clustering-builder: there is only one interesting interface > JettyClusteringBuilder. This later defines a couple of methods to augment the > environment of a Web module being built and add clustering specific GBeans; > * new module to provide a WADI implementation of the above - > Geronimo-clustering-builder-wadi; and > * geronimo-jetty-builder and geronimo-jetty are impacted to hook in > clustering. These two modules depend on geronimo-clustering and > geronimo-clustering-builder and not on WADI specific modules. > Two new modules are added: > * jetty-clustering- wadi: this module defines default WADI GBeans such as > Dispatcher, ReplicationManagerFactory, BackingStrategyFactory et cetera; and > * jetty-clustering-builder-wadi: this module defines a builder to process > Jetty DD and add various GBeans to the module being built. > I think that the implementation is flexible enough to plug in another > clustering implementation such as Kache. > As a matter of fact, there are some severe reliability (e.g. locking issues) > and integration (only one Web-app can be clustered) issues, which need to be > fixed. So, this work is not yet ready to be RTC voted. Having said that, I > have opened a JIRA such that people can have a look to the integration. > Thanks, > Gianny -- 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
