Janne Jalkanen wrote:
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?
They currently (on the test server) share only the site's domain name, with one using mod_jk to providing subdomain aliasing. They're both currently running on the same Tomcat, with the base URL of each set in jspwiki.properties as: http://acme.com/wiki/ http://sub.acme.com/ aliasing 'sub' [in other words, one is reliant on mod_jk, the other isn't.] I'll check the cookie thing tomorrow when I'm back in the office. Thanks.
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.
I've not had a chance to see nor have I seen documentation on what happens when there's a whole lot of plugin jars with a whole lot of jspwiki_module.xml files, i.e., how they all interact, which gets priority, what gets called first, etc. I'd be interested in sorting this out before another site goes up, since the one going up this week isn't actually using the "assertion framework" I've developed, just a bunch of accessory plugins. The next stage of installation would involved another level of complexity. I may in the end need to move *all* the plugins into one jar with one jspwiki_module.xml file, but I've really wanted to avoid that, trying a more distributed approach though hasn't worked very well so far.
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: STREAMThis 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.
Perhaps next week I'll have a chance to track that down better. It's one of those niggling ones that's been with me for months but because it's not effecting anything that I can see I've not put a priority on it. Thanks, Murray ........................................................................... Murray Altheim <murray07 at altheim.com> === = = http://www.altheim.com/murray/ = = === SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk = = = = Boundless wind and moon - the eye within eyes, Inexhaustible heaven and earth - the light beyond light, The willow dark, the flower bright - ten thousand houses, Knock at any door - there's one who will respond. -- The Blue Cliff Record
