• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Tomcat can't find deployed JSPWiki

 
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi there,
Last weekend, I have installed XAMPP Version 7.2.4 as a first step to lear web programming, and to check some web-based tools.
One of the first things that I have looked at is JSPWiki. Unfortunately, I even can't get the INstall script to run.
- The Tomcat Web Application Manager is saying that the app is deployed, but when I click on the JSPWiki entry on the mamager page, I get a 404 error and the message that "The requested resource is not available"
- Accessing localhost:8080/JSPWiki/Install.jsp gives the same error.
- If I start the application from the application manager, I get an exception. The last lines from the console are (line breaks in words or phrases have been manually removed):

Caused by: org.apache.wiki.api.exceptions.WikiException: Failed to start. Caused by: Failed to instantiate class org.apache.wiki.api.engine.PluginManager; please check log files for better information.
       at org.apache.wiki.WikiEngine.initialize(WikiEngine.java:650)
       at org.apache.wiki.WikiEngine.<init>(WikiEngine.java:428)
       ... 39 more
Caused by: org.apache.wiki.api.exceptions.WikiException: Failed to instantiate class org.apache.wiki.api.engine.PluginManager
       at org.apache.wiki.util.ClassUtil.getMappedObject(ClassUtil.java:377)
       at org.apache.wiki.WikiEngine.initialize(WikiEngine.java:557)
       ... 40 more
Caused by: java.lang.InstantiationException: org.apache.wiki.api.engine.PluginManager
       at java.lang.Class.newInstance(Class.java:427)
       at org.apache.wiki.util.ClassUtil.getMappedObject(ClassUtil.java:369)
       ... 41 more
Caused by: java.lang.NoSuchMethodException: org.apache.wiki.api.engine.PluginManager.<init>()
       at java.lang.Class.getConstructor0(Class.java:3082)
       at java.lang.Class.newInstance(Class.java:412)
       ... 42 more
Apr 23, 2018 10:40:42 PM org.apache.catalina.core.StandardContext startInternal
SCHWERWIEGEND: Error filterStart
Apr 23, 2018 10:40:42 PM org.apache.catalina.core.StandardContext startInternal
SCHWERWIEGEND: Context [/JSPWiki] startup failed due to previous errors
Apr 23, 2018 10:40:42 PM org.apache.catalina.loader.WebappClassLoader clearRefer
encesThreads
SCHWERWIEGEND: The web application [/JSPWiki] appears to have started a thread named [__DEFAULT__] but has failed to stop it. This is very likely to create a memory leak.
Apr 23, 2018 10:40:42 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SCHWERWIEGEND: The web application [/JSPWiki] appears to have started a thread named [Statistics Thread-__DEFAULT__-1] but has failed to stop it. This is very likely to create a memory leak.


I have read various posts how to install JSPWiki properly, and nopbody seems to have stumbled over such a fundamental error. I am sure its something simple, but I can't getthings to work.
My software environment:
- Windows 7 Home Premium
- JDK 1.8.0_45 64 bit installed on C:
- XAMPP installed on E:
- No environment variables JAVA_* and JDK_* set.
If you need more infos, please let me know, I want to get that thing started!
Thanks, Peter
 
Saloon Keeper
Posts: 22273
151
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't think you need XAMPP to run JSPWiki, so let's ignore that for the moment.

The error messages you are getting are the kind of thing that usually happens when you have mis-matched application code and library versions.

How you are getting that running JSPWiki is not clear, though unless you got hold of a bad build.

According to what small amount of installation information they provide, you should be able to just drop a copy of the JSPWiki.war file into the TOMCAT_HOME/webapps directory and start Tomcat (for example with the TOMCAT_HOME\bin\startup.bat file) and go to http://localhost:8080/JSPWiki.

For ease in debugging, I recommend that you start Tomcat from a command shell, not the Windows Service Manager, and be sure that the environment variable JAVA_HOME is set to a directory containing a JDK version 8 or higher. It's also important that JAVA_HOME references a JDK and not a JRE, because Tomcat needs the extra resources that the developer's kit provides. For one thing, Tomcat uses the javac compiler to compile the JSPs!
 
Peter Kolb
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Tim,
thanks a lot for your response.
I have downloaded the WAR file from http://www.apache.org/dist/jspwiki/2.10.3/binaries/webapp/JSPWiki.war.
Unfortunately, neither running the cataline_start.bat directly from the command line nor explictly specifying the JAVA_HOME variable ion the setenv.bat has had any effect. During startup, Tomcat (or better: the startup.bat) finds the JDK by querying the registry.
I can understand why I can't start JSPWiki, since it is mentioned that an installation is required. But since neither the ressource http://localhost:8080/JSPWiki nor http://localhost:8080/JSPWiki/Install.jsp is found, i can't run the installation.
I will probably get a pure tomcat installation and see whether that is working.
 
Tim Holloway
Saloon Keeper
Posts: 22273
151
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Tomcat may be able to find a JDK from the Windows registry, but this would be a solution of last resort. Java is designed so that multiple JDK's and JRE's of different (or even the same) version can be installed on a machine and in operation at the same time. So JAVA_HOME is the way to explicitly and unambiguously inform Tomcat which one to use. And, again, it MUST be a JDK. A JRE lacks the extra resources that Tomcat needs.

Beyond that, all I can say is definitely run a vanilla Tomcat from a command prompt and leave the Windows-specific options for Tomcat until you can get the standard version running.

You get a "404" error on the JSPWiki pages because the JSPWiki webapp did not start up correctly so Tomcat shut it off. As I said, I can't tell exactly why, but using a JRE to run Tomcat might explain it.
 
Peter Kolb
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Tim,
thanks again for your message.
I have removed all files from the XAMPP installation and went for Tomcat 9.0.x version. That worked. I am still bothered by the fact that I couldn't find the reason why the XAMPP installation didn't work, though boitth JAVA_HOME and JDK_HOME were properly set, but at least, things are working now.
 
    Bookmark Topic Watch Topic
  • New Topic