I know David Taylor has a Jetspeed 1.6 installation at a client that has
upwards of 40,000 users. It is running in a clustered Webspehere
environment and uses the new Jetspeed Cluster (CVS only) technology to
synchronize all of Jetspeed's internal information like, registry and
what not, across clustered instances. In the process of doing this I
think he may have already "fixed" the session objects with relation to
serialization.
Santiago Gala wrote:
El jue, 30-09-2004 a las 16:54 +0800, uranus.gu escribiÃ:
So sorry to send such an email because of urgency.
I am using jetspeed 1.5, and I am trying to deploy it into a web
cluster. I use jboss-3.2.4 to provide cluster service and web server.
Jboss-3.2.4 supply web service with tomcat plug-in. I use apache2 as
load balance server.
So the configuration is war
cluster and web server load-balance server
Jetspeed 1.5 Jboss 3.2.4 (tomcat plugin)
apache2.0
I found that jetspeed 1.5 can not be clustered. If I add line
"<distributable/>" into web.xml of all clustered jetspeed.war, an
error message "There has been an error!" will be shown.
Can Jetspeed 1.5 support cluster? If no, which version of jetspeed
support cluster? If yes, how should I do, is there any document?
Distributable means "all the Session stuff is serializable". We need to
audit the information stored inside the session and make sure that the
objects stored there:
- implement serializable interface
- actually do have serializable semantics
We store quite heavy objects in the session, so I'm not sure about the
current status of it.
Thank you very much
--
"Great minds discuss ideas. Average minds discuss events. Small minds discuss people."
- Admiral Hyman Rickover
*******************************************
* Scott T. Weaver *
* <[EMAIL PROTECTED]> *
* <http://www.einnovation.com> *
* -------------------------------------- *
* Apache Jetspeed Enterprise Portal *
* Apache Pluto Portlet Container *
* *
* OpenEditPro, Website Content Management *
* <http://www.openeditpro.com> *
*******************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
