1. running Apache on a Solaris box with (yes) both Tomcat 5.5 and 6,
both Java 5 and 6, and two wikis with differing permissions, I'm
getting all sorts of strange, inconsistent interactions, e.g.,
it's not uncommon for one of the wikis to request login to
simply view pages, or after a login to be browsing for awhile
and suddenly be asked to log in again. There may be Java version
interactions going on here and I've requested that each wiki be
set up in its own Solaris zone, with *only* Java 6 and Tomcat 6
available. This has yet to be done.
If these guys share the domain name, it's possible that cookies are
mixing something up. Did you check that you actually do get two
different sets of cookies from the two different wikis?
2. I'm a heavy user of plugins, using one larger jar file with a few
smaller ones. In this release I've had to remove all usage of
jspwiki_modules.xml from the installations as I've not been able
to get a wiki to start if there are any plugins missing from the
list specified in the file. I'm not sure what's happening here
and I've not had time to track this down. For now I've had to
basically remove almost all custom plugin use and not include the
jspwiki_module.xml file from any jars until I can find some time
to track this down.
Yes, that is possible. Could be that there's an uncaught exception
propagating too high up.
3. There is a possible third issue that is likely due to an embedded
use on Jetty. I've reported this before (and I think Janne may
have
answered this), and while it is inconsequential (it doesn't seem
to have any effect) it still remains. On startup I still see:
[java] java.lang.IllegalStateException: STREAM
This also seems to occur with WebLogic to some extent. I don't quite
know what I should make of it; it is probably a side effect of some
call causing the response stream to be written on Bea and Jetty, but
not on Tomcat.
/Janne
