Latest documentation lives at http://doc.jspwiki.org/2.4.

Installation Documentation#

Installing on Windows#

Comments and Small Snippets Below:#

* RefactorMe, please!



Please see the README document contained in the JSPWiki distribution for up-to-date information. (The attached version is from the cutting-edge 2.1 series - make sure you read the README of the distribution you are installing, too.)

If you are upgrading, see UpgradingJSPWiki.


Some problems you may find while installing JSPWiki#

The items below are stumbling points people have reported. If you notice an installation problem that you suspect is not yours, please add a description here.


I am trying to import the JSPWiki source code into Netbeans. Does anybody know of a step-by-step tutorial as none of Netbeans imports tools seem to work.


After Installation#

NoClassDefFound#

After you installed JSPWiki you got the exception shown below. Example: ViewPermission class not found

in the log you get something like:

*root cause*
java.lang.NoClassDefFoundError:
....

Problem: you have probably got some old, generated JSPs in your Tomcat work directories. These are referencing the older classes (e.g., ViewPermission class). Make sure you stop Tomcat, flush (delete) your work directory, then restart. - Andrew

Other#

Hi, I'm trying to get JSPWiki 2.4.0 beta to build from sources and deploy on Tomcat 5/Suse 9.3. I need the sources because I intend to create a new template. The issue that I'm having is that wiki compiles and installs - no complaints, but I cannot get passed the login screen. In other words, the authentication is banning me from even viewing pages. I properly configured jspwiki.properties file and I build it with:

ant war
command. The jar file is then copied manually to Tomcat/webapps directory

Please, help anyone.
ipolevoy

April 5 2006 Update:

I finally made it work properly. I changed two things:

  1. I was running Tomcat as root on Suse 9.3. I re-configured it to run as a regular user
  2. I downloaded the latest Tomcat: 5.5.17

Not sure which of these steps fixed the problem, but I do not have it anymore.
Thanks for responses.

ipolevoy


Hi ipolevoy, I'm also experiencing this problem. If I deploy the release 2.4.0-beta binary and set my properties, everything works correctly. However if I try to deploy the tagged 2.4.0-beta with the same properties file I cannot access any of my pages. I built using with ant war and a self signed certificate (generated during the build), Have you found a solution to this?

Todd

jspwiki.policy file is not found - Jan 7 2006 #

Hi, I have spent hours banging my head against the keyboard. When I deploy JSP wiki, I can't get past the login screen, because jspwiki.policy file does not seem to load. I verified all many times, and all seem well. I ge a forbidden screen. To see what policy is loaded, I created a test jsp page, and put this code there:
Java Security Policy: <%=System.getProperty("java.security.policy")%>
which produces this output:
Java Security Policy: jndi:/localhost/wiki/WEB-INF/jspwiki.policy
So, the right policy file seems to load, but policies specified in it are not taking any effect. I have had this same situation with many different environments: tomcat 5.5.17, 5.5.20, JBoss, etc.

This is a plea for help!

- ipolevoy


Hi,

I'm using DailyRazor.com to webhost my JSPWiki. I attempted to follow the Really simple installation instructions but couldn't find where the /webapps directory was located with my ftp connection to the site.

Site support recommended I use the "Tomcat Web Application Manager" to download the JSPWiki.war file and start it. I did this and then entered http://myhost/JSPWiki/Install.jsp. This page said I had properly installed my stuff in the web container but after filling out and submitting the form, and then restarting the JSPWiki applicaton all I got was a basic index page (from http://myhost/JSPWiki), no wiki! I've also tried adding the :8080 (http://myhost:8080/JSPWiki). Is there something simple I'm missing here?


Coincidentally, I, also, am trying to get my JSPWiki running at DailyRazor. I am trying to run in a shared JVM, because I expect the load on the site to be small and I am setting it up for a non-profit organization. One problem I have run into is that configuration errors are written to the log files, but with a shared TomCat, I do not have access to the log files. The error I get says "please check the log files". It would be really nice if the actual error was saved internally, and displayed in this page.

If you find the solution to your hosting/configuration problem, please post it here.


I am also using DailyRazor with private hosting. I tested both with WAR and with folder. both of them did not even start using the Tomcat Manager. This is the exception I see:

INFO TP-Processor10 org.apache.catalina.core.ContainerBase.Catalina.hussam.ws./manager(info) - HTMLManager: start: Starting web application at '/wiki' INFO TP-Processor10 org.apache.catalina.core.ContainerBase.Catalina.hussam.ws./wiki(info) - Assigning new engine to 18859192 INFO TP-Processor10 org.apache.catalina.core.ContainerBase.Catalina.hussam.ws./wiki(info) - No jspwiki.propertyfile defined for this context, using default from /WEB-INF/jspwiki.properties INFO TP-Processor10 org.apache.catalina.core.ContainerBase.Catalina.hussam.ws./wiki(info) - Loading cascading properties... INFO TP-Processor10 org.apache.catalina.core.ContainerBase.Catalina.hussam.ws./wiki(info) - No cascading properties defined for this context INFO TP-Processor10 org.apache.catalina.core.ContainerBase.Catalina.hussam.ws./wiki(info) - JSPWiki: Unable to load and setup properties from jspwiki.properties. Work directory does not exist: /p/web/www-data/working_directory/ INFO TP-Processor10 org.apache.catalina.core.ContainerBase.Catalina.hussam.ws./wiki(info) - ERROR: Failed to create a Wiki engine: JSPWiki: Unable to load and setup properties from jspwiki.properties. Work directory does not exist: /p/web/www-data/working_directory/ ERROR TP-Processor10 org.apache.catalina.core.ContainerBase.Catalina.hussam.ws./wiki(info) - Exception starting filter WikiJSPFilter com.ecyrd.jspwiki.InternalWikiException: No wiki engine, check logs. at com.ecyrd.jspwiki.WikiEngine.getInstance(WikiEngine.java:340) at com.ecyrd.jspwiki.ui.WikiServletFilter.init(WikiServletFilter.java:55) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:223) at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:304) at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:77) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3598) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4168) at org.apache.catalina.manager.ManagerServlet.start(ManagerServlet.java:1175) at org.apache.catalina.manager.HTMLManagerServlet.start(HTMLManagerServlet.java:527) at org.apache.catalina.manager.HTMLManagerServlet.doGet(HTMLManagerServlet.java:104) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:199) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:684) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:876) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595)


I have done my first installation of JSPWiki 2.0.52 on a SuSE9.2 using Tomcat5. While accessing the the first page using http://myhost:8080/JspTestWiki i get the following error:

java.io.FileNotFoundException: /opt/www/tomcat5/base/work/Catalina/localhost/JspTestWiki/org/apache/jsp/Wiki_jsp.java (No such file or directory)
	java.io.FileOutputStream.open(Native Method)
	java.io.FileOutputStream.<init>(FileOutputStream.java:179)
	java.io.FileOutputStream.<init>(FileOutputStream.java:70)
	org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:188)
	org.apache.jasper.compiler.Compiler.compile(Compiler.java:470)
	org.apache.jasper.compiler.Compiler.compile(Compiler.java:451)
	org.apache.jasper.compiler.Compiler.compile(Compiler.java:439)
	org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511)
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295)
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
The package of the requested file seems very funny to me. Is there any idea whats going wrong here ?

--Rainer

This is a Tomcat configuration/permission problem. It has nothing to do with JSPWiki. There is no write permission on the $CATALINA_HOME/work/Catalina/localhost directory. So JSPs are not able to be compiled.

--Rainer


Anyone know what is going on here??

org.apache.jasper.JasperException: Failed to load or instantiate TagExtraInfo class: com.ecyrd.jspwiki.tags.AttachmentsIteratorInfo

JD


If you receive an error 500 with the text "Code of a method longer than 65535 bytes", install the IBM jikes compiler. This compiler generated smaller code.

Marty


Killer Anybody have an idea on how to configure Apache, Tomcat4 and JSPWiki with authentication 2.0 so that the Apache proxies the request correctly both ways? If I just use ProxyPass and jspwiki.baseURL the authentication cookies are screwed up...

If this is what we met on jspwiki.org, then the answer is simple: don't forget to set up the virtualhosts on Tomcat as well. --JanneJalkanen

I had a problem like this. It was solved by taking care that the ProxyPass directive had the same context-uri it had in my jboss-tomcat. --MarkusSateri


MarkGriffith Trying to get jspwiki-2.0.39 running on WebLogic, we seem to be not allowing compilation of the jsp page because of:
  • Translation of /templates/default/ConflictContent.jsp failed: (line 1): Error in using tag library uri='/WEB-INF/jspwiki.tld' prefix='wiki': The Tag class 'com.ecyrd.jspwiki.tags.AttachmentsIteratorTag' has no setter method corresponding to TLD declared attribute 'page', (JSP 1.1 spec, 5.4.1)

Not sure if this is a bug in WebLogic's validator, vaugness in the spec, or bug in Wikki?

Janne Jalkanen: It's a bug I thought I had fixed. There is very easy workaround - the code is correct, so you can remove any conflicting attribute "page" entries from the jspwiki.tld. There is one with all of the Iterator Tags. Sorry. There is a fix on JSPWikiDownload.


EasyGo

I am getting the below error when I am trying to run

http://localhost:8080/JSPWiki/Wiki.jsp in my browser. I have put the .war file in the web apps directory. Any help greatly appreciated.

JSP container : tomcat

An unknown exception java.lang.NullPointerException was caught by Error.jsp. #

I have read the readme file and did exactly the same way.

Thanks!

Are you sure that you have

  • Created the proper directories
  • Unzipped the WAR file?

You should unzip the .war file as mentioned in the Documentation and edit WEB-INF/jspwiki.properties

--Kostas


-- JanneJalkanen

Got the same error message, was a little too eager. I just had to change the jsp.fileSystemProvider.pageDir property and restart Tomcat ;-) (And read the documentation ...).

-- Duif

I've the same problem as well. My solution was to delete the trailing space character after the classname. :-)

-- SteffenStundzig

I had the same problem. The root cause (for me) was that wordpad (and notepad) copied the white space from the end of "VersioningFileProvider" to the "-" character so that the "jspwiki.pageProvider" property was set to "VersioningFileProvider ". Deleting the trailing space resolved the issue.

-- MikeFauzy


HelgeTesgaard:

  • Date: 03/30/03
  • JSPWiki version: 2.0.36 (Note! the problems mentioned below are not related to JSPWiki. They are caused by the default configuration of the debian tomcat4 package.)
  • Java version: 1.3
  • Your operating system: Debian Woody

Followed the section "Ready-built packages" on the page JSPWikiDownload

Problems:

  1. the folder /usr/share/jspwiki was not created by the JSPWiki debian package post install script (/var/lib/dpkg/info/jspwiki.postinst), so i had to create it explicitly. And the installation went smoothly. JSPWiki Debian package no longer uses /usr/share/jspwiki but instead /var/lib/jspwiki as per Debian policy. This directory is created by the package. --Killer
  2. The java policy problem. The debian tomcat4 package has fine grained java classloading/resource access security enabled by default. The /etc/init.d/tomcat4 script has a TOMCAT4_SECURITY="yes" flag that can be set to no. Setting it to no has no effect caues the tomcat4 package also installs the file /etc/default/tomcat4 that overides the settings in the /etc/init.d/tomcat4 script. Therefore set the property TOMCAT4_SECURITY="no" in the file /etc/default/tomcat4 The latest version (of the Debian jspwiki package) should require no fooling around with Tomcat security. It should work both with security on and security off. --Killer
  3. tomcat4 process runs as the user tomcat4. Therefor the folder /etc/jspwiki/default must be changed to be owned by tomcat4: chown -R tomcat4 /etc/jspwiki/default

the policy problem may be solved if the policy file /usr/share/tomcat4/conf/policy.d/05jspwiki.policy:

grant codeBase "file:/var/lib/tomcat4/webapps/JSPWiki/-" {
  permission java.util.PropertyPermission "user.dir", "read";
  permission java.io.FilePermission "/var/log/tomcat4/*", "read";
  permission java.io.FilePermission "/var/log/tomcat4/*", "write";
  permission java.io.FilePermission "/var/lib/jspwiki/default", "read";
  permission java.io.FilePermission "/var/lib/jspwiki/default", "write";
  permission java.io.FilePermission "/var/lib/jspwiki/default/*", "read";
  permission java.io.FilePermission "/var/lib/jspwiki/default/*", "write";
  permission java.io.FilePermission "/var/lib/tomcat4/webapps/JSPWiki/*", "read";
  permission java.io.FilePermission "/var/lib/tomcat4/webapps/JSPWiki/*", "write";
};
is changed to reflect the path printed in the tomcat log file /var/log/tomcat4/catalina.out:
Using CATALINA_BASE:   /usr/share/tomcat4
Using CATALINA_HOME:   /usr/share/tomcat4
Using CATALINA_TMPDIR: /usr/share/tomcat4/temp
Using JAVA_HOME:       /usr/lib/j2se/1.3

Thanks, I will fix the incorrect use of symlinks in the permissions file. --Killer


Debian Users#

If you are not using the jspwiki package, use the above policy file as an example to construct a policy for your own jspwiki. /var/lib/jspwiki/default is where the datafiles are stored. --KarlThePagan

AndrewArnold:

  • Date: 03/06/03
  • JSPWiki version: 2.0.32
  • Java version: 1.1.7b
  • Your operating system: RedHat Linux 6.2
  • The web server and servlet container used: Tomcat 4.0.6, JServe 1.1.12
  • The used page provider: VersioningFileProvider
  • Used browsers: IE

After installing and testing jspWiki on my local Windows XP machine, I uploaded it to a hosting service so that I could use it as an internal collaboration tool in my organization. I've successfully got jspWiki running, however I'm having problems with file permissions when creating and saving Wiki pages.

When the system creates a new page, it is the owner and by default does not provide write access to anyone else. So new pages cannot be edited. Same problem w/pre-existing pages. Only the owner gets write permission, group and others get only read permission. Is there a mechanism in the jspWiki system to set permissions for writing files?, or can one do it by hacking Edit.jsp?

Thx,

--AndrewArnold

Umm, huh? JSPWiki engine takes care of all page creations and edits. So if Tomcat at your host site gives out permissions like: tomcat4:rw, group:none, world:none, it should not matter as all subsequent edits are done as a tomcat4-user, not as whatever JSPWiki-user. If your problem is that Tomcat creates the page as some other user than it is then using for edit requests, then the Tomcat at your host site is very broken.

Your problem may be that the host sysadmin has set up your JSPWiki incorrectly, but then you shouldn't be able to even create new pages. In that case Tomcat is running as a different user from the user having permissions to the JSPWiki file repository.

--Killer

It might also be a good idea to look at the umask command, which can be used to give permissions such as rw-rw-rw by default. However, I am a bit worried about the "java 1.1.7" you specify above. JSPWiki should NOT work with Java 1.1; we require 1.2. Are you absolutely sure that it is correct?

--Janne Jalkanen


VictorJalencas:

I have started this page because there seems to be none dealing with installation issues (other than the one dedicated to installing on Windows) but if such page exists please add this content to it. Let me ask some questions that have arisen installing JSPWiki, this page might prove useful in the future to other users.

My setup:

A laptop running Debian Woody, with Apache 1.3.23 and Tomcat 4.0 (using mod_jk to talk to apache). RCS from the 5.7-13 debian package

After installing JSPWiki in /var/www/claddagh/CRDWiki (in the directory where I keep the claddagh.ulysses.carotena.net virtual host) I set it up to use RCS, and at first use the same directory for the Wiki files (though later I have moved it to /var/www/claddagh/CRDWiki/WikiFiles for cleanliness). Each time I try to edit a file, I get the Concurrent modification message (and of course, there's only me accessing the server). Also, the message appears after a long delay. If I use the FileSystemProvider I get the same result, so my guess (that it's RCS's fault) seems unfounded. I also get what seems a repetead set of headers visible at the top of the page:

HTTP/1.1 200 OK Date: Thu, 11 Apr 2002 21:36:00 GMT Server: Apache/1.3.23 (Unix) Debian GNU/Linux PHP/4.1.2 mod_jk/1.1.0 Connection: close Transfer-Encoding: chunked, chunked Content-Type: text/html; charset=UTF-8

what's this chunked encoding? the User-Agent is mozilla 0.9.8, btw.

I have no experience dealing with RCS, so I just installed the package the debian way and have not configured it further. Could it be that I need to initialize the repository or something?

Or could it be a file permissions issue? since I installed tomcat from source, I start it up each time I use it as root (I have not bothered to create a init.d script yet), so tomcat effectively runs as root.

Any help is welcome. I have experience installing all kind of packages, so it kind of pisses me off. I have no desire (yet) to swim into the sources, and it seems like the problem some other user must have found before.

JanneJalkanen: You don't need to create an RCS repository. JSPWiki will take care of it. The only thing you must be sure of is that you run JSPWiki always as the same user, otherwise RCS will prevent you from modifying the file. RCS locks files by default with its own locking scheme, and this can sometimes be an annoyance. You can easily check the current locker using the "rlog <filename>" command. If this is something else than the user you're running under, then you're in trouble, and must break the lock by hand using "rcs -u" -command.

You can also do an general "rcs -U" to all your files, which prevents locking from being used. Unfortunately, this needs to be done for each file as it is created. Hm. I wonder if there is a way to do this automatically from within JSPWiki...

Your second issue is with getting a "concurrent modification" -message. This only occurs when when the modification date of the page on disk is different from the modification date embedded within the edited document. It is odd that you're seeing that constantly, as that suggest that there is something deeply wrong somewhere. I'll think about this further, but more information would be nice.

The third issue is the repeated headers... I'm seeing this sometimes myself, and I suspect it has something to do with Mozilla-Tomcat-Apache combination. I have no clue why it is occurring, only that it's occurring more rarely with Mozilla 0.9.9, and almost never with other browsers. Almost always a reload solves this. Anyway, it's harmless and can be safely ignored.

This site is a bog standard Debian "woody", with the code slapped directly from CVS after an "ant dist" (well okay, I store web.xml and jspwiki.properties), so the issue should not be there. Apache is our own installation, not the Debian installation, so it's hard to say whether that would be the culprit.


rolf: I notized an error message in /var/log/catalina.out stating somthing like WebappClassLoader: ... Offending class: javax/servlet.class

I deleted j2ee.jar from JSPWiki/WEB-INF/lib (because it is somewhere else on the system) and the error message is gone.

-- Rolf 17.5.2003


simon: Is there a way to use the same JSPWiki from several different contexts (in Tomcat) in order to set up multiple wikis (different content) on the same host (without duplicating the war)?

All the important stuff (like where to store the pages) seems to be defined in jspwiki.properties, not in web.xml, and hence not easily overridable. If I'm just dim, enlighten me...

I am not certain about this, since I haven't tried, but I think you can drop the JSPWiki JAR files into the $TOMCAT_HOME/shared/lib, and just recreate the contexts in server.xml. You still need to create the different directories for the webapps, and also put the JSP files in them, though I think you can probably use symbolic linking so that you don't have to replicate them as well. You also need a separate jspwiki.properties in webapp/WEB-INF for each webapp...

Try it out and let us know what happens :-).

-- JanneJalkanen

I am convinced it works, but the issue is not disk space, but ease of setup -- I'm looking to setup a "large number" of wikis, basically one per "project" (whatever that means). The idea is that it becomes almost trivial to do authorization in the webserver (a project = one base URL = one wiki = one set of people involved).

-- simon

Actually, there is now a fix in 2.0.47 (and the CVS head). It is now possible to define the jspwiki.properties file location using servlet parameters, which makes it entirely possible to set up multiple wiki instances using the exact same file set, but different repositories, etc.

Check it out from CVS (branch JSPWIKI_2_0_BRANCH) and let me know how it works for you. The documentation is in a file called MultipleWikis.

There is still a known bug : the generated RSS feed file goes to a wrong location :-/.

-- JanneJalkanen

Ok, wonderful! This is the cheap solution to the multiple wiki problem.

To top it off, it'd be nice if you could use any jspwiki.properties parameter as a context parameter to override whatever is in the jspwiki.properties file. The idea being that you would not even need to make a new jspwiki.properties file if the only difference between two wikis is the location of the page directory. (Ease of deployment)

-- simon


Hi, I tried to install Tomcat4 2.0.49 with Woody but it won't run on the specified port 8080. After try and search I found in the original Source config file a little different statement about the Port. In the original package tomcat4 runs on port 8080. In the woody config/server.xml it is set to 8180. And now its running :-)

axellander@web.de


Installed on Orion 2.0.1 with no trouble.

Unpacked the WAR somewhere and installed as follows:

  • in application.xml, added a web-module: <web-module id="wiki" path="../wiki" />
  • in default-web-site.xml, added a web-app: <web-app application="default" name="wiki" root="/wiki" />

Restarted the server for good measure and it worked :)

JeroenWenting


I tested JSP Wiki on Resin 2.1 on a win2k server at home with no problems, and uploaded it to my hosting provider (win 2003 Resin 2.1), and again, no problems.

Then I edited the .properties file, but now I find no way to get JSP Wiki to load the new configuration. I am stuck with pages and error log stored somewhere on the providers disk, unaccessible to me, until the server eventually is restarted. (I have no access to the system except scp/ftp to my own webapps and content catalogs)

Any way to signal a .properties reload to the servlet?

update: Any change to web.xml does it.

--FrodeHernes

mailto:frode@strikk.com

Err... No? I didn't even think of someone needing this kind of functionality =). But at least with Tomcat you can restart an individual context via the admin-app, without having to restart the entire container. Can't you do the same in Resin?

--JanneJalkanen

Anyhow, I have tested a couple of other java based Wikis, and this is by far the most suitable for my needs!

  • Very easy for kids to use, I am setting up a scout wiki (lik when site is live)
  • Easy to translate, my site is now 95% Norwegian without any code changes
  • Low requirements, installed at a hosted Resin 2.1 without admin access and without database possibilities.
  • Very easy to customize, the /mrg/ template looked a lot like what I was looking for, just changed some colors and small styles.
  • Works with Norwegian characters (æøåÆØÅ) both in links and in text.

Aargh, finally up and running, see: http://strikk.com/jspwiki/Wiki.jsp?page=Forside

I had to move templates and images from webapps/jspwiki/templates to /jspwiki/webapps (understandable for images as they are not caught by Resin but given to iis, but I don't know why I had to do it for the .jsp files)

I frequently get: "Tag failed, check logs: null " when clicking on the Edit page link, and now and then on ordinary pagelinks, have to investigate this later.

--FrodeHernes


Regarding what FrodeHernes mentioned above about "Easy to translate"

I disagree, I'm translating JSPWiki to another language as well and JSPWiki does not use *.properties file (as of version 2.1.89-cvs).

It's still painful to translate texts straight away from JSPs and in it's a bit ridiculous for a Java based application :). I don't appreciate hunting down texts spread all over lots of files. It will be way much easier to translate from properties file.

--HarodRuthgar

JSPWiki will have proper localization in 2.4... Sorry, we just haven't had the time to get there yet.

-- JanneJalkanen


Just installed JSPWiki thru debian apt-get install jspwiki 2.0.52 was drawn. The installer placed JSPWiki under /usr/share/java/webapps.

Removed the manually installed version from .../tomcat4/webapps/JSPWiki and linked that name to /usr/share/java/webapps/JSPWiki.

Restarted Tomcat and found JSPWiki not working with the following text in tomcats logging:

...
2003-10-25 20:25:07 WebappLoader[/JSPWiki]: Deploy JAR /WEB-INF/lib/xmlrpc.jar 
       to /usr/share/java/webapps/JSPWiki/WEB-INF/lib/xmlrpc.jar
2003-10-25 20:25:07 ContextConfig[/JSPWiki]: Missing application web.xml, using defaults only
2003-10-25 20:25:07 ContextConfig[/JSPWiki] Exception processing JAR at resource path 
       /WEB-INF/lib/oscache.jar
javax.servlet.ServletException: Exception processing JAR at resource path /WEB-INF/lib/oscache.jar
	at org.apache.catalina.startup.ContextConfig.tldScanJar(ContextConfig.java:930)
	at org.apache.catalina.startup.ContextConfig.tldScan(ContextConfig.java:868)
	at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:647)
...
	at java.lang.reflect.Method.invoke(Method.java:324)
	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
----- Root Cause -----
java.io.IOException: No such file or directory
	at java.io.UnixFileSystem.createFileExclusively(Native Method)
	at java.io.File.checkAndCreate(File.java:1313)
	at java.io.File.createTempFile(File.java:1401)
	at java.io.File.createTempFile(File.java:1438)
	at sun.net.www.protocol.jar.URLJarFile$1.run(URLJarFile.java:169)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.net.www.protocol.jar.URLJarFile.retrieve(URLJarFile.java:164)
	at sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:42)
...
	at java.lang.reflect.Method.invoke(Method.java:324)
	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)

2003-10-25 20:25:07 ContextConfig[/JSPWiki]: Marking this application unavailable due to 
         previous error(s)
2003-10-25 20:25:07 StandardManager[/JSPWiki]: Seeding random number generator class 
         java.security.SecureRandom
2003-10-25 20:25:08 StandardManager[/JSPWiki]: Seeding of random number generator has been completed
2003-10-25 20:25:08 StandardContext[/JSPWiki]: Context startup failed due to previous errors
2003-10-25 20:44:27 StandardHost[localhost]: Removing web application at context path /webdav
2003-10-25 20:44:27 StandardHost[localhost]: Removing web application at context path /JSPWiki
...

Is there an access permission problem somewhere? What will be the next step closer to a solution?

oscache.jar is definitely in the place tomcat4/webapps/JSPWiki/WEB-INF/lib/oscache.jar
jspwiki.usePageCache = false and I cannot find any other file or url specified in jspwiki.properties or web.xml that might be the cause for the io exception.

-- 28.10.2003 rsc

Finally I fixed the problem without knowing why it went wrong in the first place.

Even though tomcat4.1.24 seemed to work without any error in other application (webapps) and even though the error log focused only on JSPWiki this failure was not caused by JSPWiki.
Some experiences with a different JSPWiki version came up with the same error on the Debian system. The same JSPWiki version ran fine on a WinXP system. That experience gave evidence that tomcat4 (or some system further below) was misbehaving.

Using apt-get I deleted the JSPWiki package from the Debian installation completely including any configuration. I deleted the tomcat4 package from the Debian installation completely including any configuration in the same way.

Then reinstalled tomcat4 package using apt-get install.

Then reinstalled jspwiki package using apt-get install. But: JSPWiki failed to work from the standard configuration that came with the Debian package. (!!)

Removed the jspwiki Debian package again and manually installed a downloaded version of JSPWiki (that one that worked on WinXP). Skipping the Debian package database.

Now, JSPWiki is up again and alive on my system - but I missed the expected success: I would like to recommend Debian users to install the tomcat4 and jspwiki package out of the box (this usually takes a few minutes) and have jspwiki up and running. From my experience this is - currently - not possible. - -- 12.11.2003 rsc


Problems with ProxyPass

I've got a fresh install of JSPWiki running under Tomcat, and am using ProxyPass to hook it up to Apache. However I've got problems with the Search and UserPreferences pages as well as the breadcrumbs (they're not showing).

Under Tomcat the Wiki is under /conference, in Apache I've got

ProxyPass /apps/conference full-uri-to-tomcat/conference

Breadcrumbs work if I hit Tomcat directly. However requesting FindPage or UserPreferences takes me to /conference (which 404s) instead of /apps/conference/Search.jsp.

This is probably an obvious problem! -- ldodds

Yeah, it's a common one. The reason is that Tomcat offers cookies for a different path than what your browser sees as the URL. You will need to configure tomcat so that it serves the cookies using the same path. In case of VirtualHosts, you would need to define a new VirtualHost for Tomcat, but I am not quite sure how to do it when using ProxyPass. You probably haven't configured all of the *jsp files to be redirected through to Tomcat either.

-- JanneJalkanen


Has anyone installed JSPWiki under JBoss on Windows XP?

Is it suitable to just unpackage the war file and place under %JBOSS_HOME%\server\default\deploy\GrayWiki

Where GrayWiki is the wiki name I would like to use?

David Gray Wright


FileNotFoundException#

java.io.FileNotFoundException: \tmp\jspwiki.log (系统找不到指定的路径。)
what can I do????

If you want to hide tomcat or jboss behind apache its quite easy using mod_jk.

-- Martin West


Log4JLogger Issue with 2.2.32#

I'm currently running Tomcat 5.0, JWSDP 1.5, and JSPWiki 2.0.52 with no problems. I'm trying to add a 2nd JSPWiki running 2.2.32 to the same Tomcat server, following the guidelines at MultipleWikis. When Tomcat tries to start the new Wiki, I get the following error:

FAIL - Encountered exception java.io.IOException: 
org.apache.commons.logging.LogConfigurationException: 
org.apache.commons.logging.LogConfigurationException: 
No suitable Log constructor [Ljava.lang.Class;@b00ec2 for org.apache.commons.logging.impl.Log4JLogger

I've gone through the jspwiki.properties files in each JSPWiki to ensure all properties that point to a file or an app name are unique. I also tried commenting out all references to Log4J in the 2.2.32 JSPWiki jspwiki.properties file. No luck.

Any suggestions? Is there some Java version issue here? Hmm. I'm using JRE 1.5 and J2sdk 1.4.2. Could there be a conflict there?

Thanks in advance, Wade...

JSPWiki 2.4.6 beta installation#

I have Windows XP and use Tomcat 5.5.4 webserver. I am able to use JSPWiki 2.2.33 version without problems. Now I'm tring to install JSPWiki 2.4.6 beta, but when I prove to access to page http://localhost:8080/mywiki, Error status 404 is reported. I have only changed the jspwiki.fileSystemProvider.pageDir value and the jspwiki.basicAttachmentProvider.storageDir value in the jspwiki.proprierties file. These values are setted to the same directory in my filesystem. In this directory there are all the extracted files of JSPWiki-corepages.zip. How could I resolve the problem? Thanks.

Pages linking#

I would include the LeftMenu.jsp page in my .jsp file. I have proved to use the <jsp:include page="page_included.jsp"/> tag, but an javax.servlet.ServletException is caught: "Tag failed, check logs: WikiContext may not be NULL - serious internal problem!...". How is it possible to correct this problem, or how I could include this page differently?


JSPWiki 2.4.15 installation issue#

javax.servlet.jsp.JspException: Could not print Editor tag: Illegal to flush within a custom tag
        at com.ecyrd.jspwiki.tags.ContentTag.doEndTag(ContentTag.java:156)
        at org.apache.jsp.EditTemplate$jsp._jspService(EditTemplate$jsp.java:235)
        at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:202)
        at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382)
        at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:679)
        at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:570)
        at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:493)
        at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:818)
        at org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:390)
        at com.ecyrd.jspwiki.tags.IncludeTag.doEndTag(IncludeTag.java:83)
        at org.apache.jsp.Edit$jsp._jspService(Edit$jsp.java:316)
        at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:202)
        at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382)
        at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

I am using Tomcat 4.0.1 with Java 1.4.2_05.

Any help is appreciated.

Category Documentation

Refactor Me


I tried to make Wiki 2.4.56 work in RAD 6 but can't get it to work. I have JSPWiki v2.2.33 installed in the same workspace and it works fine.
Everytime I try to run the new wiki I get this error:

[26-09-06 14:09:48:369 CEST] 00000034 WebApp        A   SRVE0180I: [JSPWiki] [/JSPWiki1] [Servlet.LOG]: Application 1823166371 requests WikiEngine.
[26-09-06 14:09:48:369 CEST] 00000034 WebApp        A   SRVE0180I: [JSPWiki] [/JSPWiki1] [Servlet.LOG]:  Assigning new log to 1823166371
[26-09-06 14:09:48:400 CEST] 00000034 WebApp        A   SRVE0180I: [JSPWiki] [/JSPWiki1] [Servlet.LOG]: No jspwiki.propertyfile defined for this context, using default from /WEB-INF/jspwiki.properties
[26-09-06 14:09:48:432 CEST] 00000034 ServletWrappe E   SRVE0100E: Did not realize  init() exception thrown by servlet /Wiki.jsp: java.lang.VerifyError: (class: com/ecyrd/jspwiki/plugin/PluginManager, method: parsePluginLine signature: (Lcom/ecyrd/jspwiki/WikiContext;Ljava/lang/String;)Lorg/jdom/Content;) Wrong return type in method
	at com.ecyrd.jspwiki.WikiEngine.initialize(WikiEngine.java:537)
	at com.ecyrd.jspwiki.WikiEngine.<init>(WikiEngine.java:431)
	at com.ecyrd.jspwiki.WikiEngine.getInstance(WikiEngine.java:330)
	at com.ecyrd.jspwiki.WikiEngine.getInstance(WikiEngine.java:282)
	at com.ibm._jsp._Wiki.jspInit(_Wiki.java:41)
	at com.ibm.ws.jsp.runtime.HttpJspBase.init(HttpJspBase.java:70)
	at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:262)
	at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:444)
	at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:117)
	at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:171)
	at com.ibm.ws.jsp.webcontainerext.JSPExtensionProcessor.handleRequest(JSPExtensionProcessor.java:230)
	at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:394)
	at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:2837)
	at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:220)
	at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:204)
	at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1681)
	at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:77)
	at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:421)
	at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:367)

	at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:276)
	at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters(NewConnectionInitialReadCallback.java:201)
	at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:103)
	at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:548)
	at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:601)
	at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:934)
	at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1021)
	at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1332)
I imported the war file into RAD 6. Can anyone help me?

--Manie


Ahoi,

just tried to install JSPWiki (Apache 2.0.54, mod_jk 1.2.18, Tomcat 5.5.17), i the following server error:

HTTP Status 500 -

type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

org.apache.jasper.JasperException: Exception in JSP: /Error.jsp:14

11:     WikiEngine wiki;
12: %>
13: <%
14:     WikiContext wikiContext = wiki.createContext( request, 
15:                                                   WikiContext.ERROR );
16:     String pagereq = wikiContext.getName();
17: 


Stacktrace:
	org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510)
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:375)
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	com.ecyrd.jspwiki.ui.WikiServletFilter.doFilter(WikiServletFilter.java:99)
	com.ecyrd.jspwiki.ui.WikiJSPFilter.doFilter(WikiJSPFilter.java:71)

root cause

org.apache.jasper.JasperException: Exception in JSP: /Error.jsp:14

11:     WikiEngine wiki;
12: %>
13: <%
14:     WikiContext wikiContext = wiki.createContext( request, 
15:                                                   WikiContext.ERROR );
16:     String pagereq = wikiContext.getName();
17: 


Stacktrace:
	org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:504)
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393)
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:703)
	org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:670)
	org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:818)
	org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:791)
	org.apache.jsp.Wiki_jsp._jspService(Wiki_jsp.java:122)
	org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332)
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	com.ecyrd.jspwiki.ui.WikiServletFilter.doFilter(WikiServletFilter.java:99)
	com.ecyrd.jspwiki.ui.WikiJSPFilter.doFilter(WikiJSPFilter.java:71)

root cause

com.ecyrd.jspwiki.InternalWikiException: WikiEngine has not been properly started.  It is likely that the configuration is faulty.  Please check all logs for the possible reason.
	com.ecyrd.jspwiki.WikiEngine.createContext(WikiEngine.java:1915)
	org.apache.jsp.Error_jsp._jspService(Error_jsp.java:77)
	org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332)
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:703)
	org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:670)
	org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:818)
	org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:791)
	org.apache.jsp.Wiki_jsp._jspService(Wiki_jsp.java:122)
	org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332)
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	com.ecyrd.jspwiki.ui.WikiServletFilter.doFilter(WikiServletFilter.java:99)
	com.ecyrd.jspwiki.ui.WikiJSPFilter.doFilter(WikiJSPFilter.java:71)

note The full stack trace of the root cause is available in the Apache Tomcat/5.5.17 logs.
Apache Tomcat/5.5.17

But - there are no other (log) messages ..

-- Thanks in Advance - Armin Voetter

--AnonymousCoward, 15-Oct-2006


Ok, just found the other file - `/var/local/tomcat-5.5/logs/catalina_2006-10-15.log`:

INFO: JSPWiki: Unable to load and setup properties from jspwiki.properties. Property file cannot be found!null

After editing the file and entering valid paths it worked ..

--ArminVoetter, 15-Oct-2006


I'm deploying JSPWiki v 2.4 into JBoss 4.0

On server startup, I'm getting the following errors:

1) ERROR EditorManager Error parsing XML for plugin: ini/jspwiki_module.xml

2) 09:35:25,338 ERROR WebContainerAuthorizer Malformed XML in web.xml org.jdom.JDOMException: java.lang.NoClassDefFoundError: org/jdom/Text: org/jdom/Text

I have jdom.jar inside the JSPWiki.war & it containts the Text.class file

I'm clueless. I haven't altered ini/jspwiki_module.xml & it appears to be well formed xml.

Any help would be appreciated.

Thanks.

--James W., 17-Oct-2006


I found out what it was. I had to remove jaxen.jar from my jboss lib directory & just use the one that was in my WAR.

--James W., 17-Oct-2006


I was having a terrible time getting the web app to start after coping the .war file. Ultimately, it was this log line that put me on the right path (full log output below):

<log> INFO: ERROR: Failed to create a Wiki engine: JSPWiki: Unable to load and setup properties from jspwiki.properties. Failed to start managers: Page directory does not exist </log>

After changing jspwiki.fileSystemProvider.pageDir in jspwiki.properties from the default (/p/...) to a directory that actually existed, everything was happy. In detail, I edited the extracted jspwiki.properties in webapps/JSPWiki/WEB-INF as described, shutdown tomcat, deleted the WAR, then started up again, and then I was able to access the Install.jsp page per the README.

I believe this was due to that fact that I was not running Tomcat as root, and so it was unable to create anything in /. I did not have this issue dropping the .war into the tomcat I have running on my windows workstation running a user with admin privileges. I suggest that jspwiki.fileSystemProvider.pageDir in the distro be set to something that is more likely to be accessible by the user running the tomcat engine, if possible. Assuming it does not have to be an absolute path, maybe JSPWiki/pages would work?

For the record, I am running JSPWiki 2.4.100, Tomcat 5.5.23 and JDK 1.6.0, the latest stable of each at the time of this writing.

Full Log output: Mar 23, 2007 10:21:48 AM org.apache.catalina.core.ApplicationContext log INFO: Assigning new engine to 23303925 Mar 23, 2007 10:21:48 AM org.apache.catalina.core.ApplicationContext log INFO: No jspwiki.propertyfile defined for this context, using default from /WEB-INF/jspwiki.properties Mar 23, 2007 10:21:48 AM org.apache.catalina.core.ApplicationContext log INFO: JSPWiki: Unable to load and setup properties from jspwiki.properties. Failed to start managers: Page directory does not exist Mar 23, 2007 10:21:48 AM org.apache.catalina.core.ApplicationContext log INFO: ERROR: Failed to create a Wiki engine: JSPWiki: Unable to load and setup properties from jspwiki.properties. Failed to start managers: Page directory does not exist Mar 23, 2007 10:21:48 AM org.apache.catalina.core.StandardContext filterStart SEVERE: Exception starting filter WikiServletFilter com.ecyrd.jspwiki.InternalWikiException: No wiki engine, check logs. at com.ecyrd.jspwiki.WikiEngine.getInstance(WikiEngine.java:337) at com.ecyrd.jspwiki.ui.WikiServletFilter.init(WikiServletFilter.java:56) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:221) at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:302) at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:78) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3635) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4222) at org.apache.catalina.manager.ManagerServlet.start(ManagerServlet.java:1176) at org.apache.catalina.manager.HTMLManagerServlet.start(HTMLManagerServlet.java:542) at org.apache.catalina.manager.HTMLManagerServlet.doGet(HTMLManagerServlet.java:105) at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) at java.lang.Thread.run(Thread.java:619)

--Alan Johnson, 23-Mar-2007



Installing JSPWiki an Debian-Linux with Tomcat#

--Rolf Schumacher, 06-Oct-2007


Active Directory authentication trouble with v2.8.1; but works fine with v2.6.2#

--Anthos We been using v2.6.2 all this while and works fine with Tomcat6/Active Directory. Now when I try with v2.8.1 version the Active Directory authentication doesnot seem to work. I change the log category to include ALL.

Below is the output from v2.6.2 when it works.

2009-01-21 11:51:06,427 [JSPWiki Lucene Indexer] DEBUG com.ecyrd.jspwiki.util.WatchDog  - JSPWiki Lucene Indexer: Entering state Emptying index queue, expected completion in 60 s
2009-01-21 11:51:06,427 [JSPWiki Lucene Indexer] DEBUG com.ecyrd.jspwiki.util.WatchDog  - JSPWiki Lucene Indexer: Exiting state Emptying index queue
2009-01-21 11:51:07,427 [JSPWiki Lucene Indexer] DEBUG com.ecyrd.jspwiki.util.WatchDog  - JSPWiki Lucene Indexer: Entering state Emptying index queue, expected completion in 60 s
2009-01-21 11:51:07,427 [JSPWiki Lucene Indexer] DEBUG com.ecyrd.jspwiki.util.WatchDog  - JSPWiki Lucene Indexer: Exiting state Emptying index queue
2009-01-21 11:51:07,536 [http-8443-1] DEBUG com.ecyrd.jspwiki.util.WatchDog isnews:/isnews/Login.jsp - http-8443-1: Entering state Filtering for URL /isnews/Login.jsp, expected completion in 90 s
2009-01-21 11:51:07,552 [http-8443-1] DEBUG com.ecyrd.jspwiki.auth.SessionMonitor isnews:/isnews/Login.jsp isnews:https://wstk13993:8443/isnews/Login.jsp - Looking up WikiSession for session ID=CFBFD77E83B0B311DEA945AD9459D822... found it
2009-01-21 11:51:07,552 [http-8443-1] DEBUG com.ecyrd.jspwiki.WikiContext isnews:/isnews/Login.jsp isnews:https://wstk13993:8443/isnews/Login.jsp - Creating WikiContext for session ID=CFBFD77E83B0B311DEA945AD9459D822; target=Login
2009-01-21 11:51:07,552 [http-8443-1] DEBUG com.ecyrd.jspwiki.WikiContext isnews:/isnews/Login.jsp isnews:https://wstk13993:8443/isnews/Login.jsp - Do we need to log the user in? false
2009-01-21 11:51:07,552 [http-8443-1] INFO com.ecyrd.jspwiki.WikiSession isnews:/isnews/Login.jsp isnews:https://wstk13993:8443/isnews/Login.jsp - Remote user changed to asamuel
2009-01-21 11:51:07,552 [http-8443-1] INFO com.ecyrd.jspwiki.WikiSession isnews:/isnews/Login.jsp isnews:https://wstk13993:8443/isnews/Login.jsp - User principal changed to asamuel
2009-01-21 11:51:07,552 [http-8443-1] DEBUG com.ecyrd.jspwiki.auth.SessionMonitor isnews:/isnews/Login.jsp isnews:https://wstk13993:8443/isnews/Login.jsp - Looking up WikiSession for session ID=CFBFD77E83B0B311DEA945AD9459D822... found it
2009-01-21 11:51:07,552 [http-8443-1] DEBUG com.ecyrd.jspwiki.auth.login.WebContainerLoginModule isnews:/isnews/Login.jsp isnews:https://wstk13993:8443/isnews/Login.jsp - Added Principal asamuel,Role.ANONYMOUS,Role.ALL
2009-01-21 11:51:07,552 [http-8443-1] DEBUG com.ecyrd.jspwiki.auth.login.WebContainerLoginModule isnews:/isnews/Login.jsp isnews:https://wstk13993:8443/isnews/Login.jsp - Added Principal $G(AUS)-SsdtWikiAcl.
2009-01-21 11:51:07,552 [http-8443-1] DEBUG com.ecyrd.jspwiki.auth.login.AbstractLoginModule isnews:/isnews/Login.jsp isnews:https://wstk13993:8443/isnews/Login.jsp - Removed Principal 10.32.6.15
2009-01-21 11:51:07,552 [http-8443-1] DEBUG com.ecyrd.jspwiki.auth.login.AbstractLoginModule isnews:/isnews/Login.jsp isnews:https://wstk13993:8443/isnews/Login.jsp - Committed Principal asamuel
2009-01-21 11:51:07,552 [http-8443-1] DEBUG com.ecyrd.jspwiki.auth.login.AbstractLoginModule isnews:/isnews/Login.jsp isnews:https://wstk13993:8443/isnews/Login.jsp - Committed Principal Authenticated
2009-01-21 11:51:07,552 [http-8443-1] DEBUG com.ecyrd.jspwiki.auth.login.AbstractLoginModule isnews:/isnews/Login.jsp isnews:https://wstk13993:8443/isnews/Login.jsp - Committed Principal All
2009-01-21 11:51:07,552 [http-8443-1] DEBUG com.ecyrd.jspwiki.auth.login.AbstractLoginModule isnews:/isnews/Login.jsp isnews:https://wstk13993:8443/isnews/Login.jsp - Committed Principal $G(AUS)-SsdtWikiAcl
2009-01-21 11:51:07,552 [http-8443-1] DEBUG com.ecyrd.jspwiki.auth.login.AbstractLoginModule isnews:/isnews/Login.jsp isnews:https://wstk13993:8443/isnews/Login.jsp - Removed Principal Anonymous
2009-01-21 11:51:07,552 [http-8443-1] DEBUG SecurityLog isnews:/isnews/Login.jsp isnews:https://wstk13993:8443/isnews/Login.jsp - WikiSecurityEvent.UNKNOWN (30) [source=com.ecyrd.jspwiki.auth.AuthenticationManager@cffc79, target=com.ecyrd.jspwiki.WikiSession@6ef7ba]
2009-01-21 11:51:07,552 [http-8443-1] INFO SecurityLog isnews:/isnews/Login.jsp isnews:https://wstk13993:8443/isnews/Login.jsp - WikiSecurityEvent.LOGIN_AUTHENTICATED [source=com.ecyrd.jspwiki.auth.AuthenticationManager@cffc79, princpal=org.apache.catalina.realm.GenericPrincipal asamuel, target=com.ecyrd.jspwiki.WikiSession@6ef7ba]
2009-01-21 11:51:07,552 [http-8443-1] DEBUG SecurityLog isnews:/isnews/Login.jsp isnews:https://wstk13993:8443/isnews/Login.jsp - WikiSecurityEvent.LOGIN_AUTHENTICATED [source=com.ecyrd.jspwiki.auth.AuthenticationManager@cffc79, princpal=org.apache.catalina.realm.GenericPrincipal asamuel, target=com.ecyrd.jspwiki.WikiSession@6ef7ba]
2009-01-21 11:51:07,552 [http-8443-1] WARN com.ecyrd.jspwiki.WikiSession isnews:/isnews/Login.jsp isnews:https://wstk13993:8443/isnews/Login.jsp - User profile 'asamuel' not found. This is normal for container-auth users who haven't set up a profile yet.
2009-01-21 11:51:07,552 [http-8443-1] INFO JSPWiki isnews:/isnews/Login.jsp isnews:https://wstk13993:8443/isnews/Login.jsp - Successfully authenticated user asamuel (container auth)

Below is the output from v2.8.1 when it DOESNOT work.

2009-01-21 11:51:04,896 [JSPWiki Lucene Indexer] DEBUG com.ecyrd.jspwiki.util.WatchDog  - JSPWiki Lucene Indexer: Entering state Emptying index queue, expected completion in 60 s
2009-01-21 11:51:04,896 [JSPWiki Lucene Indexer] DEBUG com.ecyrd.jspwiki.util.WatchDog  - JSPWiki Lucene Indexer: Exiting state Emptying index queue
2009-01-21 11:51:04,896 [WatchDog for 'JSPWiki'] DEBUG com.ecyrd.jspwiki.util.WatchDog  - Checking watchdog 'JSPWiki Lucene Indexer'
2009-01-21 11:51:09,896 [JSPWiki Lucene Indexer] DEBUG com.ecyrd.jspwiki.util.WatchDog  - JSPWiki Lucene Indexer: Entering state Emptying index queue, expected completion in 60 s
2009-01-21 11:51:09,896 [JSPWiki Lucene Indexer] DEBUG com.ecyrd.jspwiki.util.WatchDog  - JSPWiki Lucene Indexer: Exiting state Emptying index queue
2009-01-21 11:51:10,864 [http-8443-1] DEBUG com.ecyrd.jspwiki.auth.SessionMonitor  - Looking up WikiSession for session ID=5995D671DE02AC510F13E2F28479157B... not found. Creating guestSession()
2009-01-21 11:51:10,880 [http-8443-1] DEBUG com.ecyrd.jspwiki.WikiContext  - Creating WikiContext for session ID=5995D671DE02AC510F13E2F28479157B; target=Login
2009-01-21 11:51:10,880 [http-8443-1] DEBUG JSPWiki  - Login template content is: /templates/default/ViewTemplate.jsp
2009-01-21 11:51:10,943 [http-8443-1] DEBUG com.ecyrd.jspwiki.auth.SessionMonitor  - Looking up WikiSession for session ID=5995D671DE02AC510F13E2F28479157B... found it
2009-01-21 11:51:11,052 [http-8443-1] INFO com.ecyrd.jspwiki.auth.UserManager  - Attempting to load user database class com.ecyrd.jspwiki.auth.user.XMLUserDatabase
2009-01-21 11:51:11,068 [http-8443-1] WARN com.ecyrd.jspwiki.auth.user.AbstractUserDatabase  - XML user database property jspwiki.xmlUserDatabaseFile not found; trying C:\asamuel\tools\apache-tomcat-6.0.14\webapps\JSPWiki\WEB-INF\userdatabase.xml
2009-01-21 11:51:11,068 [http-8443-1] INFO com.ecyrd.jspwiki.auth.user.AbstractUserDatabase  - XML user database at C:\asamuel\tools\apache-tomcat-6.0.14\webapps\JSPWiki\WEB-INF\userdatabase.xml
2009-01-21 11:51:11,068 [http-8443-1] DEBUG com.ecyrd.jspwiki.auth.user.AbstractUserDatabase  - Database successfully initialized
2009-01-21 11:51:11,068 [http-8443-1] INFO com.ecyrd.jspwiki.auth.UserManager  - UserDatabase initialized.

Add new attachment

Only authorized users are allowed to upload new attachments.
« This page (revision-174) was last changed on 07-May-2012 10:31 by Luke