You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jspwiki.apache.org by Jason Morris <ja...@sydney.edu.au> on 2015/11/13 01:19:14 UTC

re: Glassfish 4.0 installation instructions

Hello!
Does anyone have a complete and updated list of the instructions for installing & configuring JSPWiki on Glassfish 4.0?
Thanks!

Jason C. Morris | PhD Candidate
Department of Environmental Sciences | Faculty of Agriculture and Environment
THE UNIVERSITY OF SYDNEY, NSW, 2006
phone: +61 02 8627 1152


Re: Glassfish 4.0 installation instructions

Posted by Juan Pablo Santos Rodríguez <ju...@gmail.com>.
Hi Jason,

if you're using 2.10.1 you may be affected by
https://issues.apache.org/jira/browse/JSPWIKI-880

Other than that you shouldn't have any issues. Note that JSPWIKI-880 is
fixed on current trunk, so you could grab the latest snapshot from
https://repository.apache.org/content/groups/snapshots/org/apache/jspwiki/
and you should be set to go.

(this reminds me we should really look into releasing 2.10.2; there are
some i18n keys missing for some translations, but other than that current
trunk seems ok enough..)


HTH,
juan pablo

On Fri, Nov 13, 2015 at 1:55 AM, Jason Morris <ja...@sydney.edu.au>
wrote:

> Thanks for the quick reply, Dave.
> I've had great success using JSPWiki on Tomcat... been using it for years.
> I tried exactly the procedure you mentioned, and I get wonky results with
> login not working using simple XML database authentication.
> I'll rip it all out, get the latest binary, and go through the config file
> again, and re-install from the Admin console.
> Can I ping you with questions? Don't want to spam you.
> Cheers,
> Jason
>
> -----Original Message-----
> From: Dave Koelmeyer [mailto:dave.koelmeyer@davekoelmeyer.co.nz]
> Sent: Friday, 13 November 2015 11:46 AM
> To: user@jspwiki.apache.org
> Subject: Re: Glassfish 4.0 installation instructions
>
> On 13/11/15 13:19, Jason Morris wrote:
> > Hello!
> > Does anyone have a complete and updated list of the instructions for
> installing & configuring JSPWiki on Glassfish 4.0?
> > Thanks!
>
> Hi Jason,
>
> I don't, but I do use GlassFish - assuming you're not using
> container-managed authentication it's as simple installing the WAR as a
> web app using the GlassFish GUI, and running the JSPWiki installer. Some
> of the paths for JSPWiki's configuration files will differ from Tomcat
> here and there, shoot if you need.
>
> (I'm planning to check out Payara at some stage however
> (http://www.payara.co/home), as a migration path from GlassFish.)
>
> --
> Dave Koelmeyer
> http://blog.davekoelmeyer.co.nz
> GPG Key ID: 0x238BFF87
>
>
>

Re: Glassfish 4.0 installation instructions

Posted by Dave Koelmeyer <da...@davekoelmeyer.co.nz>.
On 13/11/15 13:55, Jason Morris wrote:
> Thanks for the quick reply, Dave.
> I've had great success using JSPWiki on Tomcat... been using it for years.
> I tried exactly the procedure you mentioned, and I get wonky results with login not working using simple XML database authentication.
> I'll rip it all out, get the latest binary, and go through the config file again, and re-install from the Admin console.
> Can I ping you with questions? Don't want to spam you.

Hi Jason,

Perfectly fine, fire away (off-list if you prefer).

Cheers,
Dave

-- 
Dave Koelmeyer
http://blog.davekoelmeyer.co.nz
GPG Key ID: 0x238BFF87



>
> -----Original Message-----
> From: Dave Koelmeyer [mailto:dave.koelmeyer@davekoelmeyer.co.nz] 
> Sent: Friday, 13 November 2015 11:46 AM
> To: user@jspwiki.apache.org
> Subject: Re: Glassfish 4.0 installation instructions
>
> On 13/11/15 13:19, Jason Morris wrote:
>> Hello!
>> Does anyone have a complete and updated list of the instructions for installing & configuring JSPWiki on Glassfish 4.0?
>> Thanks!
> Hi Jason,
>
> I don't, but I do use GlassFish - assuming you're not using
> container-managed authentication it's as simple installing the WAR as a
> web app using the GlassFish GUI, and running the JSPWiki installer. Some
> of the paths for JSPWiki's configuration files will differ from Tomcat
> here and there, shoot if you need.
>
> (I'm planning to check out Payara at some stage however
> (http://www.payara.co/home), as a migration path from GlassFish.)
>


RE: Glassfish 4.0 installation instructions

Posted by Jason Morris <ja...@sydney.edu.au>.
Thanks for the quick reply, Dave.
I've had great success using JSPWiki on Tomcat... been using it for years.
I tried exactly the procedure you mentioned, and I get wonky results with login not working using simple XML database authentication.
I'll rip it all out, get the latest binary, and go through the config file again, and re-install from the Admin console.
Can I ping you with questions? Don't want to spam you.
Cheers,
Jason

-----Original Message-----
From: Dave Koelmeyer [mailto:dave.koelmeyer@davekoelmeyer.co.nz] 
Sent: Friday, 13 November 2015 11:46 AM
To: user@jspwiki.apache.org
Subject: Re: Glassfish 4.0 installation instructions

On 13/11/15 13:19, Jason Morris wrote:
> Hello!
> Does anyone have a complete and updated list of the instructions for installing & configuring JSPWiki on Glassfish 4.0?
> Thanks!

Hi Jason,

I don't, but I do use GlassFish - assuming you're not using
container-managed authentication it's as simple installing the WAR as a
web app using the GlassFish GUI, and running the JSPWiki installer. Some
of the paths for JSPWiki's configuration files will differ from Tomcat
here and there, shoot if you need.

(I'm planning to check out Payara at some stage however
(http://www.payara.co/home), as a migration path from GlassFish.)

-- 
Dave Koelmeyer
http://blog.davekoelmeyer.co.nz
GPG Key ID: 0x238BFF87



Re: Glassfish 4.0 installation instructions

Posted by Dave Koelmeyer <da...@davekoelmeyer.co.nz>.
On 13/11/15 13:19, Jason Morris wrote:
> Hello!
> Does anyone have a complete and updated list of the instructions for installing & configuring JSPWiki on Glassfish 4.0?
> Thanks!

Hi Jason,

I don't, but I do use GlassFish – assuming you're not using
container-managed authentication it's as simple installing the WAR as a
web app using the GlassFish GUI, and running the JSPWiki installer. Some
of the paths for JSPWiki's configuration files will differ from Tomcat
here and there, shoot if you need.

(I'm planning to check out Payara at some stage however
(http://www.payara.co/home), as a migration path from GlassFish.)

-- 
Dave Koelmeyer
http://blog.davekoelmeyer.co.nz
GPG Key ID: 0x238BFF87



Re: Glassfish 4.0 installation instructions

Posted by Rolf Schumacher <ro...@august.de>.
Tried to move a JSPWiki installation from one computer hosting tomcat7 
to an newly configured on hosting tomcat8.

- copied the pages folder
- copied tomcat/lib/jspwiki-custom.properties
- dropped the JSPWiki war file beneath tomcat/webapps

It wont start, problems with ehcache I guess.

Any idea what I should do?

Regards


Rolf

This is catalina.out:

13-Feb-2016 15:00:46.889 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Server 
version:        Apache Tomcat/8.0.32
13-Feb-2016 15:00:46.890 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Server 
built:          Feb 2 2016 19:34:53 UTC
13-Feb-2016 15:00:46.890 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Server 
number:         8.0.32.0
13-Feb-2016 15:00:46.890 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log OS 
Name:               Linux
13-Feb-2016 15:00:46.891 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log OS 
Version:            3.16.0-4-amd64
13-Feb-2016 15:00:46.891 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log 
Architecture:          amd64
13-Feb-2016 15:00:46.891 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Java 
Home:             /usr/lib/jvm/java-7-openjdk-amd64/jre
13-Feb-2016 15:00:46.891 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log JVM 
Version:           1.7.0_95-b00
13-Feb-2016 15:00:46.891 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log JVM 
Vendor:            Oracle Corporation
13-Feb-2016 15:00:46.891 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log 
CATALINA_BASE:         /opt/apache-tomcat-8.0.32
13-Feb-2016 15:00:46.891 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log 
CATALINA_HOME:         /opt/apache-tomcat-8.0.32
13-Feb-2016 15:00:46.892 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Command line 
argument: 
-Djava.util.logging.config.file=/opt/tomcat/conf/logging.properties
13-Feb-2016 15:00:46.892 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Command line 
argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
13-Feb-2016 15:00:46.892 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Command line 
argument: -Djava.awt.headless=true
13-Feb-2016 15:00:46.892 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Command line 
argument: -Xmx512M
13-Feb-2016 15:00:46.892 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Command line 
argument: -Djava.endorsed.dirs=/opt/tomcat/endorsed
13-Feb-2016 15:00:46.892 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Command line 
argument: -Dcatalina.base=/opt/tomcat
13-Feb-2016 15:00:46.892 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Command line 
argument: -Dcatalina.home=/opt/tomcat
13-Feb-2016 15:00:46.892 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Command line 
argument: -Djava.io.tmpdir=/tmp/tomcat-tmp
13-Feb-2016 15:00:46.892 INFO [main] 
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR 
based Apache Tomcat Native library which allows optimal performance in 
production environments was not found on the java.library.path: 
/usr/java/packages/lib/amd64:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib
13-Feb-2016 15:00:47.016 INFO [main] 
org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler 
["http-nio-8080"]
13-Feb-2016 15:00:47.034 INFO [main] 
org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a 
shared selector for servlet write/read
13-Feb-2016 15:00:47.037 INFO [main] 
org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler 
["ajp-nio-8009"]
13-Feb-2016 15:00:47.039 INFO [main] 
org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a 
shared selector for servlet write/read
13-Feb-2016 15:00:47.040 INFO [main] 
org.apache.catalina.startup.Catalina.load Initialization processed in 673 ms
13-Feb-2016 15:00:47.067 INFO [main] 
org.apache.catalina.core.StandardService.startInternal Starting service 
Catalina
13-Feb-2016 15:00:47.067 INFO [main] 
org.apache.catalina.core.StandardEngine.startInternal Starting Servlet 
Engine: Apache Tomcat/8.0.32
13-Feb-2016 15:00:47.093 INFO [localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployWAR Deploying web 
application archive /opt/apache-tomcat-8.0.32/webapps/JSPWiki.war
13-Feb-2016 15:00:49.114 INFO [localhost-startStop-1] 
org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was 
scanned for TLDs yet contained no TLDs. Enable debug logging for this 
logger for a complete list of JARs that were scanned but no TLDs were 
found in them. Skipping unneeded JARs during scanning can improve 
startup time and JSP compilation time.
log4j:WARN No appenders could be found for logger 
(org.apache.wiki.util.PropertyReader).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for 
more info.
13-Feb-2016 15:00:49.685 SEVERE [localhost-startStop-1] 
org.apache.catalina.core.StandardContext.startInternal One or more 
Filters failed to start. Full details will be found in the appropriate 
container log file
13-Feb-2016 15:00:49.685 SEVERE [localhost-startStop-1] 
org.apache.catalina.core.StandardContext.startInternal Context 
[/JSPWiki] startup failed due to previous errors
13-Feb-2016 15:00:49.697 WARNING [localhost-startStop-1] 
org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads 
The web application [JSPWiki] appears to have started a thread named 
[net.sf.ehcache.CacheManager@4a4f8d22] but has failed to stop it. This 
is very likely to create a memory leak. Stack trace of thread:
  java.lang.Object.wait(Native Method)
  java.util.TimerThread.mainLoop(Timer.java:552)
  java.util.TimerThread.run(Timer.java:505)
13-Feb-2016 15:00:49.704 INFO [localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployWAR Deployment of web 
application archive /opt/apache-tomcat-8.0.32/webapps/JSPWiki.war has 
finished in 2,610 ms
13-Feb-2016 15:00:49.705 INFO [localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deploying web 
application directory /opt/apache-tomcat-8.0.32/webapps/host-manager
13-Feb-2016 15:00:49.747 INFO [localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web 
application directory /opt/apache-tomcat-8.0.32/webapps/host-manager has 
finished in 42 ms
13-Feb-2016 15:00:49.747 INFO [localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deploying web 
application directory /opt/apache-tomcat-8.0.32/webapps/manager
13-Feb-2016 15:00:49.791 INFO [localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web 
application directory /opt/apache-tomcat-8.0.32/webapps/manager has 
finished in 44 ms
13-Feb-2016 15:00:49.791 INFO [localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deploying web 
application directory /opt/apache-tomcat-8.0.32/webapps/ROOT
13-Feb-2016 15:00:49.809 INFO [localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web 
application directory /opt/apache-tomcat-8.0.32/webapps/ROOT has 
finished in 18 ms
13-Feb-2016 15:00:49.810 INFO [localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deploying web 
application directory /opt/apache-tomcat-8.0.32/webapps/examples
13-Feb-2016 15:00:50.067 INFO [localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web 
application directory /opt/apache-tomcat-8.0.32/webapps/examples has 
finished in 258 ms
13-Feb-2016 15:00:50.067 INFO [localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deploying web 
application directory /opt/apache-tomcat-8.0.32/webapps/docs
13-Feb-2016 15:00:50.083 INFO [localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web 
application directory /opt/apache-tomcat-8.0.32/webapps/docs has 
finished in 16 ms
13-Feb-2016 15:00:50.085 INFO [main] 
org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler 
["http-nio-8080"]
13-Feb-2016 15:00:50.090 INFO [main] 
org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler 
["ajp-nio-8009"]
13-Feb-2016 15:00:50.091 INFO [main] 
org.apache.catalina.startup.Catalina.start Server startup in 3051 ms
13-Feb-2016 15:00:50.573 INFO [net.sf.ehcache.CacheManager@4a4f8d22] 
org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading 
Illegal access: this web application instance has been stopped already. 
Could not load [net.sf.ehcache.util.ProductInfo]. The following stack 
trace is thrown for debugging purposes as well as to attempt to 
terminate the thread which caused the illegal access.
  java.lang.IllegalStateException: Illegal access: this web application 
instance has been stopped already. Could not load 
[net.sf.ehcache.util.ProductInfo]. The following stack trace is thrown 
for debugging purposes as well as to attempt to terminate the thread 
which caused the illegal access.
     at 
org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1328)
     at 
org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1316)
     at 
org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1181)
     at 
org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1142)
     at 
net.sf.ehcache.util.UpdateChecker.buildParamsString(UpdateChecker.java:133)
     at 
net.sf.ehcache.util.UpdateChecker.buildUpdateCheckUrl(UpdateChecker.java:123)
     at net.sf.ehcache.util.UpdateChecker.doCheck(UpdateChecker.java:68)
     at 
net.sf.ehcache.util.UpdateChecker.checkForUpdate(UpdateChecker.java:60)
     at net.sf.ehcache.util.UpdateChecker.run(UpdateChecker.java:51)
     at java.util.TimerThread.mainLoop(Timer.java:555)
     at java.util.TimerThread.run(Timer.java:505)