Jules,The one that I pointed you two in the second message in this thread.
AbstractReplicatedStoreyou've declared your webapp as distributed and ignored the message that Jetty gave you on startup about not being able to provide distributed session management (probably becaise you are running 'default' not 'all' - this one is also in the FAQ, I believe).
Honestly, I made the error ok.
Which FAQ?
The SessionManager that *you* have asked for by specifying that your webapp is <distributable/>
But the current behaviour contradicts the behaviour of least surprise.
Your session manager is broken. When you fix the errors that you are getting during deployment it will work properly.
*my* session manager is the one that comes with JBoss 3.2.0 RC 4
out of the box. Or what do you mean?
No doubt you are using xdoclet to produce your web.xml - unfortunately it defaults to declaring all webapps distributable. You will need to set distributable="false" in your build.xml
Where exactly?
I will inquire in that direction too. xdoclet 1.2b2 doesn't know this attribute to the jbosswebxml subtask. Ok, this is a xdoclet problem.
<webdoclet
destdir="output"
excludedtags="@version,@author,@todo"
force="true"
>
<fileset dir="${src.src}">
<include name="**/*Servlet.java"/>
<include name="**/*Filter.java"/>
<include name="**/*Listener.java"/>
</fileset>
<deploymentdescriptor
servletspec="2.3"
distributable="false"
sessiontimeout="30"
/>
</webdoclet>How do you decide you are in a cluster if :Again: with the principle of least surprise, Jetty should, when it finds out that it is not in a cluster, fall back to single node operation no matter what <distributable/> is.
1). The jar that contains the clustering implementation is not available (which it isn't in the default config - javagroups.jar)
2). you are the first node to come up.
??
My approach is that the developer should know what they are doing. If they ask Jetty to do something that it cannot do, it should error - behaviour after that is undefined. If Jetty pretended to be working, the problem would just bite you much harder after a lot more investigation later. Better that you are forced to resolve it as soon as it occurs.
Yes the error messages could be better, and will be on the next development iteration.
Jules
Thanks
Heiko
________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs SkyScan service. For more information on a proactive anti-virus service working around the clock, around the globe, visit http://www.messagelabs.com ________________________________________________________________________
------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
