The issue I have always run into is that upgrading is a huge pain.
It is never Just JSPwiki but all the dependencies.

These are the facets for upgrades I came up with:

   - Operating System
   - let's Encrypt
   - nginx
   - Java
   - Tomcat
   - JSPWiki
      - jspwiki engine
      - jspwiki pages

Frankly speaking, this is a real pain.

Install setup created:
CATALINA_BASE: /var/lib/tomcat9
CATALINA_HOME: /usr/share/tomcat9

tomcat user home as:
/opt/tomcat and using /bin/false

And I thought page directory should be:
/opt/tomcat/jspwikipages/ldapwiki/

Then I should be able to run:

   - sudo apt update
   - sudo apt upgrade

and the Operating system, let's Encrypt, nginx, Tomcat, and Java would all
be upgraded as needed.

any thoughts?

--
-jim
Jim Willeke


On Thu, Dec 17, 2020 at 2:19 PM Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> Hi Jim,
>
> I've always have worked with an environment in which CATALINA_BASE ==
> CATALINA_HOME, said that, yes, your setup seems correct to
> me (also 2 min of google https://stackoverflow.com/a/29398713 seem to
> confirm that).
>
>
> best regards,
> juan pablo
>
> On Thu, Dec 17, 2020 at 2:19 PM Jim Willeke <j...@willeke.com> wrote:
>
> > My setup is now:
> > DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS"
> > Apache Tomcat/9.0.31 (Ubuntu)
> > Java Home:      /usr/lib/jvm/java-13-openjdk-amd64
> > JVM Version:    13.0.4+8-Ubuntu-120.04
> > CATALINA_BASE:  /var/lib/tomcat9
> > CATALINA_HOME:  /usr/share/tomcat9
> >
> > So I am assuming we would place the jspwiki.war (regardless of name) into
> > the
> > $CATALINA_BASE/tomcat9/webapps/
> > And that is where we would expect to see the folder "jspwiki" created
> when
> > the war is expanded.
> >
> > And the jspwiki.war would be owned by tomcat.
> > Is that correct?
> >
> > --
> > -jim
> > Jim Willeke
> >
> >
> > On Tue, Dec 15, 2020 at 3:44 PM Juan Pablo Santos Rodríguez <
> > juanpablo.san...@gmail.com> wrote:
> >
> > > Hi Jim,
> > >
> > > apologies, the e-mail got stuck in drafts and I didn't notice :-/
> > >
> > > the contents of the work folder were to see which war was deployed if
> > > ldapwiki.war or folder.war.. The unfound jspwiki.properties file should
> > be
> > > inside the jspwiki-main jar, under the ini folder.
> > >
> > > As for starting tomcat passing some system properties and as it seems
> > that
> > > the jspwiki.properties file can't be found when starting JSPWiki, on
> your
> > > $TOMCAT_HOME/bin/catalina.sh file, locate the commented line were the
> > > JAVA_OPTS variable is set and uncomment it and set it to something
> like:
> > >
> > > JAVA_OPTS="$JAVA_OPTS -Dlog4j.rootCategory=DEBUG,ConsoleLog" and that
> > > should be fine to start tomcat.
> > >
> > > Also, do you have any jspwiki-custom.properties file set? is so, how?
> > >
> > > Last but not least, would you mind trying with new 2.11.0.M8? it
> > contains a
> > > couple of serious fixes related to search indexing + workflows'
> > persistence
> > > on disk
> > >
> > >
> > > best regards,
> > > juan pablo
> > >
> > > On Mon, Dec 7, 2020 at 4:13 PM Jim Willeke <j...@willeke.com> wrote:
> > >
> > > > I changed to folder.war, as I was making a feeble attempt to hide
> > details
> > > > about ldapwiki.
> > > >
> > > > Not sure what you are looking for here:
> > > > ll /var/lib/tomcat9/work/Catalina/localhost/
> > > > total 24
> > > > drwxr-x--- 6 tomcat tomcat 4096 Dec  4 10:43 ./
> > > > drwxr-x--- 3 tomcat tomcat 4096 Dec  4 09:49 ../
> > > > drwxr-x--- 3 tomcat tomcat 4096 Dec  4 11:55 host-manager/
> > > > drwxr-x--- 2 tomcat tomcat 4096 Dec  4 10:43 ldapwiki/
> > > > drwxr-x--- 3 tomcat tomcat 4096 Dec  6 10:48 manager/
> > > > drwxr-x--- 2 tomcat tomcat 4096 Dec  4 09:49 ROOT/
> > > >
> > > > /var/lib/tomcat9/work/Catalina/localhost/ldapwiki/
> > > > total 8
> > > > drwxr-x--- 2 tomcat tomcat 4096 Dec  4 10:43 ./
> > > > drwxr-x--- 6 tomcat tomcat 4096 Dec  4 10:43 ../
> > > >
> > > > Sorry, No idea how I would start tomcat using
> > > > "-Dlog4j.rootCategory=DEBUG,ConsoleLog"
> > > >
> > > > systemctl status tomcat9
> > > > ● tomcat9.service - Apache Tomcat 9 Web Application Server
> > > >      Loaded: loaded (/lib/systemd/system/tomcat9.service; enabled;
> > vendor
> > > > preset: enabled)
> > > >      Active: active (running) since Sun 2020-12-06 10:48:37 UTC; 1
> day
> > 4h
> > > > ago
> > > >        Docs: https://tomcat.apache.org/tomcat-9.0-doc/index.html
> > > >     Process: 549
> > > ExecStartPre=/usr/libexec/tomcat9/tomcat-update-policy.sh
> > > > (code=exited, status=0/SUCCESS)
> > > >    Main PID: 574 (java)
> > > >       Tasks: 37 (limit: 4620)
> > > >      Memory: 255.9M
> > > >      CGroup: /system.slice/tomcat9.service
> > > >              └─574 /usr/lib/jvm/default-java/bin/java
> > > >
> > -Djava.util.logging.config.file=/var/lib/tomcat9/conf/logging.properties
> > > > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
> > > > -Djava.awt.headless=true -Djdk.tls.ephemeralDHKe>
> > > >
> > > >
> > > > --
> > > > -jim
> > > > Jim Willeke
> > > >
> > > >
> > > > On Mon, Dec 7, 2020 at 9:09 AM Juan Pablo Santos Rodríguez <
> > > > juanpablo.san...@gmail.com> wrote:
> > > >
> > > > > Hi Jim,
> > > > >
> > > > > you mention initially that the war is deployed as folder.war
> instead
> > of
> > > > > ldapwiki.war, is that correct? What files are placed inside
> > > > > $TOMCAT_HOME/work? Also, would you mind starting tomcat providing
> it
> > a
> > > > > "-Dlog4j.rootCategory=DEBUG,ConsoleLog" argument?
> > > > > That should provide more information on catalina.out
> > > > >
> > > > >
> > > > > best regards,
> > > > > juan pablo
> > > > >
> > > > > On Sun, Dec 6, 2020 at 11:55 AM Jim Willeke <j...@willeke.com>
> wrote:
> > > > >
> > > > > > Here is what I see:
> > > > > >
> > > > > > less /var/log/tomcat9/catalina.2020-12-06.log
> > > > > > 06-Dec-2020 10:48:43.248 INFO [main]
> > > > > > org.apache.catalina.startup.HostConfig.deployDescriptor
> Deployment
> > of
> > > > > > deployment descriptor
> > > > [/etc/tomcat9/Catalina/localhost/host-manager.xml]
> > > > > > has finished in [416] ms
> > > > > > 06-Dec-2020 10:48:43.252 INFO [main]
> > > > > > org.apache.catalina.startup.HostConfig.deployWAR Deploying web
> > > > > application
> > > > > > archive [/var/lib/tomcat9/webapps/ldapwiki.war]
> > > > > > 06-Dec-2020 10:48:45.254 INFO [main]
> > > > > > 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.
> > > > > > 06-Dec-2020 10:48:46.202 SEVERE [main]
> > > > > > org.apache.catalina.core.StandardContext.startInternal One or
> more
> > > > > Filters
> > > > > > failed to start. Full details will be found in the appropriate
> > > > container
> > > > > > log file
> > > > > > 06-Dec-2020 10:48:46.202 SEVERE [main]
> > > > > > org.apache.catalina.core.StandardContext.startInternal Context
> > > > > [/ldapwiki]
> > > > > > startup failed due to previous errors
> > > > > > 06-Dec-2020 10:48:46.206 WARNING [main]
> > > > > >
> > > org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads
> > > > > The
> > > > > > web application [ldapwiki] appears to have started a thread named
> > > > > > [__DEFAULT__] but has failed to stop it. This is very likely to
> > > create
> > > > a
> > > > > > memory leak. Stack trace of thread:
> > > > > >  java.base@11.0.9.1/java.lang.Object.wait(Native Method)
> > > > > >  java.base@11.0.9.1/java.lang.Object.wait(Object.java:328)
> > > > > >
> java.base@11.0.9.1/java.util.TimerThread.mainLoop(Timer.java:527)
> > > > > >  java.base@11.0.9.1/java.util.TimerThread.run(Timer.java:506)
> > > > > > 06-Dec-2020 10:48:46.206 WARNING [main]
> > > > > >
> > > org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads
> > > > > The
> > > > > > web application [ldapwiki] 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. Stack trace of thread:
> > > > > >  java.base@11.0.9.1/jdk.internal.misc.Unsafe.park(Native Method)
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> java.base@11.0.9.1/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:234)
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> java.base@11.0.9.1/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2123)
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> java.base@11.0.9.1/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182)
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> java.base@11.0.9.1/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> java.base@11.0.9.1/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1054)
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> java.base@11.0.9.1/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1114)
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> java.base@11.0.9.1/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> > > > > >  java.base@11.0.9.1/java.lang.Thread.run(Thread.java:834)
> > > > > > 06-Dec-2020 10:48:46.215 INFO [main]
> > > > > > org.apache.catalina.startup.HostConfig.deployWAR Deployment of
> web
> > > > > > application archive [/var/lib/tomcat9/webapps/ldapwiki.war] has
> > > > finished
> > > > > in
> > > > > > [2,963] ms
> > > > > >
> > > > > >
> > > > > > --
> > > > > > -jim
> > > > > > Jim Willeke
> > > > > >
> > > > > >
> > > > > > On Sat, Dec 5, 2020 at 10:23 AM Harry Metske <
> > harry.met...@gmail.com
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > does catalina.out reveal any more detail?
> > > > > > >
> > > > > > > regards,
> > > > > > > Harry
> > > > > > >
> > > > > > > On Fri, 4 Dec 2020 at 13:31, Jim Willeke <j...@willeke.com>
> > wrote:
> > > > > > >
> > > > > > > > New install.
> > > > > > > > Apache Tomcat/9.0.31 (Ubuntu)
> > > > > > > > 11.0.9.1+1-Ubuntu-0ubuntu1.20.04
> > > > > > > > JspWiki: 2.11.0.M7 (Binary download)
> > > > > > > > java --version openjdk 11.0.9.1 2020-11-04
> > > > > > > > OpenJDK 64-Bit Server VM (build
> > 11.0.9.1+1-Ubuntu-0ubuntu1.20.04,
> > > > > mixed
> > > > > > > > mode, sharing)
> > > > > > > >
> > > > > > > > No Issue accessing
> > > > > > > > http://<ipaddress>:8080/manager/
> > > > > > > >
> > > > > > > > CATALINA_BASE="/var/lib/tomcat9"
> > > > > > > > CATALINA_HOME="/usr/share/tomcat9"
> > > > > > > >
> > > > > > > > Copied war file to /var/lib/tomcat9/webapps/
> > > > > > > > drwxr-x--- 10 tomcat tomcat     4096 Dec  4 10:43 folder/
> > > > > > > > -rw-r--r--  1 tomcat tomcat 23277026 Dec  4 10:19 folder.war
> > > > > > > > drwxr-xr-x  3 tomcat tomcat     4096 Dec  4 09:49 ROOT/
> > > > > > > >
> > > > > > > > Seems like appropriate files are expanded at:
> > > > > > > > /var/lib/tomcat9/webapps/folder/ (jsps and WEB-INF/ etc)
> > > > > > > >
> > > > > > > > INFO [main] org.apache.catalina.core.ApplicationContext.log
> > > ERROR:
> > > > > > Failed
> > > > > > > > to create a Wiki engine: JSPWiki: *Unable to load and setup
> > > > > properties
> > > > > > > from
> > > > > > > > jspwiki.properties. Failed to start.* Caused by: null; please
> > > check
> > > > > log
> > > > > > > > files for better information.
> > > > > > > >
> > > > > > > > find /var/lib/tomcat9/webapps/ldapwiki/ -type f -name
> > > > "*.properties"
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> /var/lib/tomcat9/webapps/ldapwiki/META-INF/maven/org.apache.jspwiki/jspwiki-war/pom.properties
> > > > > > > >
> > > > > > > > Any Ideas?
> > > > > > > > --
> > > > > > > > -jim
> > > > > > > > Jim Willeke
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Reply via email to