User: jules_gosnell Date: 02/03/05 16:45:39 Modified: jetty FAQ Log: update Revision Changes Path 1.3 +59 -4 contrib/jetty/FAQ Index: FAQ =================================================================== RCS file: /cvsroot/jboss/contrib/jetty/FAQ,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- FAQ 22 Feb 2002 23:53:17 -0000 1.2 +++ FAQ 6 Mar 2002 00:45:39 -0000 1.3 @@ -60,7 +60,7 @@ Currently, JBoss comes with no webapps preinstalled, so starting it up and hitting localhost:8080/ will result in your receiving a "404 Not Found" error. This is NOT a problem with your installation. It IS -correct behaviour. If you want to see something there deploy +correct behaviour. If you want to see something there, deploy something. @@ -89,8 +89,9 @@ e.g. my.war/WEB-INF/jetty-web.xml. The ConfigurationElement in jboss-service.xml and the contents of -jetty-web.xml are written in a very XML veneer over Jetty's java API, -so have your JavaDoc to hand - for further info see jetty.mortbay.org. +jetty-web.xml are written in a very thin XML veneer over Jetty's java +API, so have your JavaDoc to hand - for further info see +jetty.mortbay.org. I want to use Virtual Hosts @@ -133,11 +134,62 @@ <another link to Mortbay> +So - tell me about Distributed HttpSessions... +--------------------------------------------- + +An HttpSession is an object used in a WebApp to store conversational +state between requests. + +A WebApp may be described as 'distributable' in it's WEB-INF/web.xml. + +The J2EE requires that a 'distributable' app may be 'migrated' between +nodes of a cluster - i.e. taken down on one node and brought up on +another. Extant HttpSessions must continue to be available to the new +WebApp instance. + +Many AppServers extend this fn-ality from simply allowing migration to +providing failover i.e. If a WebApp is not undeployed from it's node +cleanly (The node may crash, hang or be too busy to process new +requests)it's HttpSessions are still made available to other instances +of the same WebApp within the cluster. + +This extension is problematic since J2EE requires that on stopping a +distributed WebApp should notify HttpSession attributes implementing +HttpSessionActivationListener before passivating/distributing +them. When the WebApp has been restarted and re-activates an +HttpSession the same attributes must be notifies again. If, because of +the reuse of this fn-ality to provide fail-over, attributes do not +receive passivation events on one node before receipt of activation +events on another, an asymmetry, which would not happen on a fully +compliant AppServer occurs. + +Our integration allows the user to specify whether this extended +behaviour (snapshotting) is required and, if so, exactly what +combination of events attributes should expect. + + +How do I set up Distributed HttpSession support ? +-------------------------------------------------- + +1. copy the ../cluster/output/lib/jbossha-httpsession.sar into deploy. + +2. In jetty-plugin.sar/META-INF/jboss-service.xml set + HttpSessionStorageStrategy to org.jboss.jetty.session.ClusteredStore + +3. In jetty-plugin.sar/META-INF/jboss-service.xml set +HttpSessionSnapshotFrequency to your required value. + +3. In jetty-plugin.sar/META-INF/jboss-service.xml set +HttpSessionSnapshotNotificationPolicy to your required value. + +Let me know of any problems and I shall look into them ASAP. + + Development ------------ There is a 'devel' target in the build.xml which should rebuild and -deploy the plugin then (perhaps) run the WebIntergration test +deploy the plugin then (perhaps) run the WebIntegration test suite. You need a JBoss up and running. @@ -160,6 +212,9 @@ [EMAIL PROTECTED] + +If you have any further questions about the integration which you feel +should be discussed in this document, please let me know, Enjoy,
_______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
