WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org
View all threadsHi All,
After installing a fresh copy of Ubuntu 18.04, I then followed the
directions on the webpage Collection Space Current Documentation -
Automated installed for CollectionSpace
https://collectionspace.atlassian.net/wiki/spaces/DOC/pages/667353186/Automated+installer+for+CollectionSpace.
Everything installed correctly as best as I can tell. I'm able to
access the core via the standard user / password, but am not able to
access any of the other tenants. Not sure if this is expected or not,
but thought it was worth noting.
I then went and followed the directions for Creating your new tenant
https://collectionspace.atlassian.net/wiki/spaces/DOC/pages/667353175/Creating+your+new+tenant#Creatingyournewtenant-Procedureforcreatinganewtenant.
I wasn't able to find anything in the xml file that matched the
description in the first red warning box. But was able to change what I
needed for the second red box. As near as I can tell, the install went
without an issue. I was confused by the second red box but tried it both
with and without the changed suggested there.
After restarting my server and CSPACE I am no longer able to log into
the core using the above user/password. Also as with the other tenants
earlier, I'm getting a standard 404 error when I try to access my new tent.
Per the instructions I do have the file - tenants-bindings/merged.xml.
Also here's a tail from my catalina.out file:
Aug 11, 2019 3:31:12 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deployment of web application archive
/usr/local/share/apache-tomcat-7.0.64/webapps/cspace-services.war has
finished in 88,878 ms
Aug 11, 2019 3:31:12 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/usr/local/share/apache-tomcat-7.0.64/webapps/ROOT
Aug 11, 2019 3:31:16 PM org.apache.catalina.startup.TldConfig execute
INFO: 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.
Aug 11, 2019 3:31:16 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deployment of web application directory
/usr/local/share/apache-tomcat-7.0.64/webapps/ROOT has finished in 3,968 ms
Aug 11, 2019 3:31:16 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/usr/local/share/apache-tomcat-7.0.64/webapps/docs
Aug 11, 2019 3:31:20 PM org.apache.catalina.startup.TldConfig execute
INFO: 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.
Aug 11, 2019 3:31:20 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deployment of web application directory
/usr/local/share/apache-tomcat-7.0.64/webapps/docs has finished in 3,788 ms
Aug 11, 2019 3:31:20 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/usr/local/share/apache-tomcat-7.0.64/webapps/cspace-ui
Aug 11, 2019 3:31:24 PM org.apache.catalina.startup.TldConfig execute
INFO: 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.
Aug 11, 2019 3:31:24 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deployment of web application directory
/usr/local/share/apache-tomcat-7.0.64/webapps/cspace-ui has finished in
4,107 ms
Aug 11, 2019 3:31:24 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/usr/local/share/apache-tomcat-7.0.64/webapps/cspace#core
Aug 11, 2019 3:31:27 PM org.apache.catalina.startup.TldConfig execute
INFO: 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.
Aug 11, 2019 3:31:27 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deployment of web application directory
/usr/local/share/apache-tomcat-7.0.64/webapps/cspace#core has finished
in 3,725 ms
Aug 11, 2019 3:31:27 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/usr/local/share/apache-tomcat-7.0.64/webapps/cspace#drawings
Aug 11, 2019 3:31:31 PM org.apache.catalina.startup.TldConfig execute
INFO: 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.
Aug 11, 2019 3:31:31 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deployment of web application directory
/usr/local/share/apache-tomcat-7.0.64/webapps/cspace#drawings has
finished in 3,666 ms
Aug 11, 2019 3:31:31 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8180"]
Aug 11, 2019 3:31:31 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Aug 11, 2019 3:31:31 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 108391 ms
Aug 11, 2019 3:34:50 PM org.apache.catalina.loader.WebappClassLoader
loadClass
INFO: Illegal access: this web application instance has been stopped
already. Could not load org.quartz.DisallowConcurrentExecution. The
eventual following stack trace is caused by an error thrown for
debugging purposes as well as to attempt to terminate the thread which
caused the illegal access, and has no functional impact.
java.lang.IllegalStateException
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1750)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1709)
at
org.quartz.impl.JobDetailImpl.isConcurrentExectionDisallowed(JobDetailImpl.java:388)
at
org.quartz.simpl.RAMJobStore.acquireNextTriggers(RAMJobStore.java:1428)
at
org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:272)
Exception in thread "Quartz_Scheduler" java.lang.NoClassDefFoundError:
org/quartz/DisallowConcurrentExecution
at
org.quartz.impl.JobDetailImpl.isConcurrentExectionDisallowed(JobDetailImpl.java:388)
at
org.quartz.simpl.RAMJobStore.acquireNextTriggers(RAMJobStore.java:1428)
at
org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:272)
Caused by: java.lang.ClassNotFoundException:
org.quartz.DisallowConcurrentExecution
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1858)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1709)
... 3 more
cspace@bellis:~/collectionspace-source$ ug 11, 2019 3:31:12 PM
org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
The web application [/cspace-services] created a ThreadLocal with key
of type [org.nuxeo.runtime.api.login.LoginConfiguration$1] (value
[org.nuxeo.runtime.api.login.LoginConfiguration$1@7aa86e95]) and a value
of type [org.nuxeo.runtime.api.login.LoginComponent$1] (value
[org.nuxeo.runtime.api.login.LoginComponent$1@318c3297]) but failed to
remove it when the web application was stopped. Threads are going to be
renewed over time to try and avoid a probable memory leak.
Aug: command not found
cspace@bellis:~/collectionspace-source$ SEVERE: The web application
[/cspace-services] created a ThreadLocal with key of type
[org.nuxeo.runtime.api.login.LoginConfiguration$1] (value
[org.nuxeo.runtime.api.login.LoginConfiguration$1@7aa86e95]) and a value
of type [org.nuxeo.runtime.api.login.LoginComponent$1] (value
[org.nuxeo.runtime.api.login.LoginComponent$1@318c3297]) but failed to
remove it when the web application was stopped. Threads are going to be
renewed over time to try and avoid a probable memory leak.
-su: syntax error near unexpected token `('
cspace@bellis:~/collectionspace-source$
Any thoughts would be most helpful. :)
Thanks
-Ben
Hi Ben,
Of the built-in tenants, only the core tenant is enabled by default, so that part is normal.
I recently pushed a couple of bug fixes for tenant creation in 5.1. Since you couldn't find the XML element referenced in the first warning, it sounds like you may have installed CollectionSpace before I made those fixes. To ensure you have the fixes, in the collectionspace-source/application directory, run the command:
git pull
Then recreate your tenant:
Let me know if that works.
Ray
From: Talk talk-bounces@lists.collectionspace.org on behalf of Ben Streissguth ben@streissguth.com
Sent: Sunday, August 11, 2019 3:46:37 PM
To: talk@lists.collectionspace.org
Subject: [Talk] Can't log into admin account after adding a new tenant
Hi All,
After installing a fresh copy of Ubuntu 18.04, I then followed the directions on the webpage Collection Space Current Documentation - Automated installed for CollectionSpacehttps://collectionspace.atlassian.net/wiki/spaces/DOC/pages/667353186/Automated+installer+for+CollectionSpace. Everything installed correctly as best as I can tell. I'm able to access the core via the standard user / password, but am not able to access any of the other tenants. Not sure if this is expected or not, but thought it was worth noting.
I then went and followed the directions for Creating your new tenanthttps://collectionspace.atlassian.net/wiki/spaces/DOC/pages/667353175/Creating+your+new+tenant#Creatingyournewtenant-Procedureforcreatinganewtenant. I wasn't able to find anything in the xml file that matched the description in the first red warning box. But was able to change what I needed for the second red box. As near as I can tell, the install went without an issue. I was confused by the second red box but tried it both with and without the changed suggested there.
After restarting my server and CSPACE I am no longer able to log into the core using the above user/password. Also as with the other tenants earlier, I'm getting a standard 404 error when I try to access my new tent.
Per the instructions I do have the file - tenants-bindings/merged.xml. Also here's a tail from my catalina.out file:
Aug 11, 2019 3:31:12 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deployment of web application archive /usr/local/share/apache-tomcat-7.0.64/webapps/cspace-services.war has finished in 88,878 ms
Aug 11, 2019 3:31:12 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /usr/local/share/apache-tomcat-7.0.64/webapps/ROOT
Aug 11, 2019 3:31:16 PM org.apache.catalina.startup.TldConfig execute
INFO: 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.
Aug 11, 2019 3:31:16 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /usr/local/share/apache-tomcat-7.0.64/webapps/ROOT has finished in 3,968 ms
Aug 11, 2019 3:31:16 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /usr/local/share/apache-tomcat-7.0.64/webapps/docs
Aug 11, 2019 3:31:20 PM org.apache.catalina.startup.TldConfig execute
INFO: 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.
Aug 11, 2019 3:31:20 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /usr/local/share/apache-tomcat-7.0.64/webapps/docs has finished in 3,788 ms
Aug 11, 2019 3:31:20 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /usr/local/share/apache-tomcat-7.0.64/webapps/cspace-ui
Aug 11, 2019 3:31:24 PM org.apache.catalina.startup.TldConfig execute
INFO: 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.
Aug 11, 2019 3:31:24 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /usr/local/share/apache-tomcat-7.0.64/webapps/cspace-ui has finished in 4,107 ms
Aug 11, 2019 3:31:24 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /usr/local/share/apache-tomcat-7.0.64/webapps/cspace#core
Aug 11, 2019 3:31:27 PM org.apache.catalina.startup.TldConfig execute
INFO: 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.
Aug 11, 2019 3:31:27 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /usr/local/share/apache-tomcat-7.0.64/webapps/cspace#core has finished in 3,725 ms
Aug 11, 2019 3:31:27 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /usr/local/share/apache-tomcat-7.0.64/webapps/cspace#drawings
Aug 11, 2019 3:31:31 PM org.apache.catalina.startup.TldConfig execute
INFO: 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.
Aug 11, 2019 3:31:31 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /usr/local/share/apache-tomcat-7.0.64/webapps/cspace#drawings has finished in 3,666 ms
Aug 11, 2019 3:31:31 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8180"]
Aug 11, 2019 3:31:31 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Aug 11, 2019 3:31:31 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 108391 ms
Aug 11, 2019 3:34:50 PM org.apache.catalina.loader.WebappClassLoader loadClass
INFO: Illegal access: this web application instance has been stopped already. Could not load org.quartz.DisallowConcurrentExecution. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
java.lang.IllegalStateException
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1750)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1709)
at org.quartz.impl.JobDetailImpl.isConcurrentExectionDisallowed(JobDetailImpl.java:388)
at org.quartz.simpl.RAMJobStore.acquireNextTriggers(RAMJobStore.java:1428)
at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:272)
Exception in thread "Quartz_Scheduler" java.lang.NoClassDefFoundError: org/quartz/DisallowConcurrentExecution
at org.quartz.impl.JobDetailImpl.isConcurrentExectionDisallowed(JobDetailImpl.java:388)
at org.quartz.simpl.RAMJobStore.acquireNextTriggers(RAMJobStore.java:1428)
at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:272)
Caused by: java.lang.ClassNotFoundException: org.quartz.DisallowConcurrentExecution
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1858)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1709)
... 3 more
cspace@bellis:~/collectionspace-source$ ug 11, 2019 3:31:12 PM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
The web application [/cspace-services] created a ThreadLocal with key of type [org.nuxeo.runtime.api.login.LoginConfiguration$1] (value [org.nuxeo.runtime.api.login.LoginConfiguration$1@7aa86e95]) and a value of type [org.nuxeo.runtime.api.login.LoginComponent$1] (value [org.nuxeo.runtime.api.login.LoginComponent$1@318c3297]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
Aug: command not found
cspace@bellis:~/collectionspace-source$ SEVERE: The web application [/cspace-services] created a ThreadLocal with key of type [org.nuxeo.runtime.api.login.LoginConfiguration$1] (value [org.nuxeo.runtime.api.login.LoginConfiguration$1@7aa86e95]) and a value of type [org.nuxeo.runtime.api.login.LoginComponent$1] (value [org.nuxeo.runtime.api.login.LoginComponent$1@318c3297]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
-su: syntax error near unexpected token `('
cspace@bellis:~/collectionspace-source$
Any thoughts would be most helpful. :)
Thanks
-Ben
Hi Ray,
Thanks for the prompt help. Sorry for the delay in getting back to you
but I've been trying a number of different things since your suggestions
didn't work. I ended up loading a clean copy of Ubuntu and starting
over with the directions. I'm not 100% which set I used last time, but
I didn't remember it being 5.2. Sadly 5.2 won't install on my machine.
After the second install I discovered that it can't create the database.
I then went back and reinstalled 5.1 on another dev machine and
confirmed it was working. After installing the new tenant I'm happy to
say everything seems to be working.
I'm hoping that when I tune the database the software will boot faster.
It's taking a good 5 minutes for the web page to load the first time
around on each boot. I haven't seen any mention of it, but I'm assuming
the startup script has to be run each time the machine is booted. Is
there an easy way to automate this that you'd recommend?
Thanks
_Ben
On 8/12/2019 2:38 PM, Ray Lee wrote:
Hi Ben,
Of the built-in tenants, only the core tenant is enabled by default,
so that part is normal.
I recently pushed a couple of bug fixes for tenant creation in 5.1.
Since you couldn't find the XML element referenced in the first
warning, it sounds like you may have installed CollectionSpace before
I made those fixes. To ensure you have the fixes, in the
collectionspace-source/application directory, run the command:
git pull
Then recreate your tenant:
Let me know if that works.
Ray
From: Talk talk-bounces@lists.collectionspace.org on behalf of Ben
Streissguth ben@streissguth.com
Sent: Sunday, August 11, 2019 3:46:37 PM
To: talk@lists.collectionspace.org
Subject: [Talk] Can't log into admin account after adding a new tenant
Hi All,
After installing a fresh copy of Ubuntu 18.04, I then followed the
directions on the webpage Collection Space Current Documentation -
Automated installed for
CollectionSpacehttps://collectionspace.atlassian.net/wiki/spaces/DOC/pages/667353186/Automated+installer+for+CollectionSpace.
Everything installed correctly as best as I can tell. I'm able to
access the core via the standard user / password, but am not able to
access any of the other tenants. Not sure if this is expected or not,
but thought it was worth noting.
I then went and followed the directions for Creating your new
tenanthttps://collectionspace.atlassian.net/wiki/spaces/DOC/pages/667353175/Creating+your+new+tenant#Creatingyournewtenant-Procedureforcreatinganewtenant.
I wasn't able to find anything in the xml file that matched the
description in the first red warning box. But was able to change what
I needed for the second red box. As near as I can tell, the install
went without an issue. I was confused by the second red box but tried
it both with and without the changed suggested there.
After restarting my server and CSPACE I am no longer able to log into
the core using the above user/password. Also as with the other
tenants earlier, I'm getting a standard 404 error when I try to access
my new tent.
Per the instructions I do have the file - tenants-bindings/merged.xml.
Also here's a tail from my catalina.out file:
Aug 11, 2019 3:31:12 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deployment of web application archive
/usr/local/share/apache-tomcat-7.0.64/webapps/cspace-services.war has
finished in 88,878 ms
Aug 11, 2019 3:31:12 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/usr/local/share/apache-tomcat-7.0.64/webapps/ROOT
Aug 11, 2019 3:31:16 PM org.apache.catalina.startup.TldConfig execute
INFO: 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.
Aug 11, 2019 3:31:16 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deployment of web application directory
/usr/local/share/apache-tomcat-7.0.64/webapps/ROOT has finished in
3,968 ms
Aug 11, 2019 3:31:16 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/usr/local/share/apache-tomcat-7.0.64/webapps/docs
Aug 11, 2019 3:31:20 PM org.apache.catalina.startup.TldConfig execute
INFO: 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.
Aug 11, 2019 3:31:20 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deployment of web application directory
/usr/local/share/apache-tomcat-7.0.64/webapps/docs has finished in
3,788 ms
Aug 11, 2019 3:31:20 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/usr/local/share/apache-tomcat-7.0.64/webapps/cspace-ui
Aug 11, 2019 3:31:24 PM org.apache.catalina.startup.TldConfig execute
INFO: 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.
Aug 11, 2019 3:31:24 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deployment of web application directory
/usr/local/share/apache-tomcat-7.0.64/webapps/cspace-ui has finished
in 4,107 ms
Aug 11, 2019 3:31:24 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/usr/local/share/apache-tomcat-7.0.64/webapps/cspace#core
Aug 11, 2019 3:31:27 PM org.apache.catalina.startup.TldConfig execute
INFO: 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.
Aug 11, 2019 3:31:27 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deployment of web application directory
/usr/local/share/apache-tomcat-7.0.64/webapps/cspace#core has finished
in 3,725 ms
Aug 11, 2019 3:31:27 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/usr/local/share/apache-tomcat-7.0.64/webapps/cspace#drawings
Aug 11, 2019 3:31:31 PM org.apache.catalina.startup.TldConfig execute
INFO: 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.
Aug 11, 2019 3:31:31 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deployment of web application directory
/usr/local/share/apache-tomcat-7.0.64/webapps/cspace#drawings has
finished in 3,666 ms
Aug 11, 2019 3:31:31 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8180"]
Aug 11, 2019 3:31:31 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Aug 11, 2019 3:31:31 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 108391 ms
Aug 11, 2019 3:34:50 PM org.apache.catalina.loader.WebappClassLoader
loadClass
INFO: Illegal access: this web application instance has been stopped
already. Could not load org.quartz.DisallowConcurrentExecution. The
eventual following stack trace is caused by an error thrown for
debugging purposes as well as to attempt to terminate the thread which
caused the illegal access, and has no functional impact.
java.lang.IllegalStateException
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1750)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1709)
at
org.quartz.impl.JobDetailImpl.isConcurrentExectionDisallowed(JobDetailImpl.java:388)
at
org.quartz.simpl.RAMJobStore.acquireNextTriggers(RAMJobStore.java:1428)
at
org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:272)
Exception in thread "Quartz_Scheduler" java.lang.NoClassDefFoundError:
org/quartz/DisallowConcurrentExecution
at
org.quartz.impl.JobDetailImpl.isConcurrentExectionDisallowed(JobDetailImpl.java:388)
at
org.quartz.simpl.RAMJobStore.acquireNextTriggers(RAMJobStore.java:1428)
at
org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:272)
Caused by: java.lang.ClassNotFoundException:
org.quartz.DisallowConcurrentExecution
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1858)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1709)
... 3 more
cspace@bellis:~/collectionspace-source$ ug 11, 2019 3:31:12 PM
org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
The web application [/cspace-services] created a ThreadLocal with key
of type [org.nuxeo.runtime.api.login.LoginConfiguration$1] (value
[org.nuxeo.runtime.api.login.LoginConfiguration$1@7aa86e95]) and a
value of type [org.nuxeo.runtime.api.login.LoginComponent$1] (value
[org.nuxeo.runtime.api.login.LoginComponent$1@318c3297]) but failed to
remove it when the web application was stopped. Threads are going to
be renewed over time to try and avoid a probable memory leak.
Aug: command not found
cspace@bellis:~/collectionspace-source$ SEVERE: The web application
[/cspace-services] created a ThreadLocal with key of type
[org.nuxeo.runtime.api.login.LoginConfiguration$1] (value
[org.nuxeo.runtime.api.login.LoginConfiguration$1@7aa86e95]) and a
value of type [org.nuxeo.runtime.api.login.LoginComponent$1] (value
[org.nuxeo.runtime.api.login.LoginComponent$1@318c3297]) but failed to
remove it when the web application was stopped. Threads are going to
be renewed over time to try and avoid a probable memory leak.
-su: syntax error near unexpected token `('
cspace@bellis:~/collectionspace-source$
Any thoughts would be most helpful. :)
Thanks
-Ben