On 20 July 2014 10:23, Jim Willeke wrote:
> Is there somewhere in your environment you're setting an explicit
> CLASSPATH?
> ->No.
> su -c 'sh /usr/share/tomcat/bin/startup.sh' tomcat
> Using CATALINA_BASE: /usr/share/tomcat
> Using CATALINA_HOME: /usr/share/tomcat
> Using CATALINA_TMPDIR: /u
Is there somewhere in your environment you're setting an explicit
CLASSPATH?
->No.
su -c 'sh /usr/share/tomcat/bin/startup.sh' tomcat
Using CATALINA_BASE: /usr/share/tomcat
Using CATALINA_HOME: /usr/share/tomcat
Using CATALINA_TMPDIR: /usr/share/tomcat/temp
Using JRE_HOME:/usr
Using CLA
On 7/19/14, 4:21 PM, Jim Willeke wrote:
Installed latest Oracle Java. (Was using openJDK)
Cleared work directory.
===
/usr/share/tomcat/work/jspwiki.log (Why would it be here?)
Good question; my all-defaults instal
Latest attempts:
Installed latest Oracle Java. (Was using openJDK)
Cleared work directory.
/usr/share/tomcat/logs/catlina.out
INFO: A valid shutdown command was received via the shutdown port. Stopping
the Server instance.
Jul 19, 2014 11:13:54 PM org.apache.coyote.AbstractProtocol pause
INFO: P
On 7/19/14, 3:23 PM, Jim Willeke wrote:
What is "ldapwiki.war"? Is that a standard JSPWiki.war renamed?
->Yes. Latest version 2.10.1.
If this is a fresh install of Tomcat and JSPWiki, why are there
"persisted sessions" being found?
-> Fresh install of both. May have been stopped and started a co
What is "ldapwiki.war"? Is that a standard JSPWiki.war renamed?
->Yes. Latest version 2.10.1.
If this is a fresh install of Tomcat and JSPWiki, why are there
"persisted sessions" being found?
-> Fresh install of both. May have been stopped and started a couple of
times.
-jim
--
-jim
Jim Willeke
On 7/19/14, 12:49 PM, Jim Willeke wrote:
Latest version of tomcat7 v7.0.54.
When I have tried to setup using a linux distro of tomcat, there is
apparently an expectation that jspwiki should be able to write to some
directories that the linux/Tomcat distro will not permit.
With a download direct
Latest version of tomcat7 v7.0.54.
When I have tried to setup using a linux distro of tomcat, there is
apparently an expectation that jspwiki should be able to write to some
directories that the linux/Tomcat distro will not permit.
With a download direct from Tomcat and write permissions applied
Jim,
you can find the answer here:
https://jspwiki-wiki.apache.org/Wiki.jsp?page=FAQ , the last question.
kind regards,
Harry
Op 19 jul. 2014 19:24 schreef "Jim Willeke" :
> I have no idea where to go at this point.
>
> So from a "stock" Apache tomcat7 installation Apache JSPWIKI no longer will
On 7/19/14, 10:23 AM, Jim Willeke wrote:
I have no idea where to go at this point.
So from a "stock" Apache tomcat7 installation Apache JSPWIKI no longer will
run.
Sorry, I haven't been following this thread particularly closely, but
for grins I just dropped a fresh downloaded JSPWiki.war file
I have no idea where to go at this point.
So from a "stock" Apache tomcat7 installation Apache JSPWIKI no longer will
run.
You mention putting a log4j.properties file in tomcat's
webapps/JSPWiki/WEB-INF/classes directory.
What should be contained in this file?
Thanks for the help.
--
-jim
Jim
I think neither of these two is the case.
The issue here is that you have a (tomcat) environment where you are not
allowed to write to tomcat's lib directory, or you don't want configuration
in that directory because you don't want these configs to apply to other
(JSPWiki) applications running in t
Hi there,
two things come to my mind regarding the "standard" Tomcat coming with a Linux
distribution:
* Is this Tomcat running with a security manager enabled? JSPWiki isn't running
under a security manager (i.e. without further configuration).
* Are advanced security modules like SELinux or A
I have spent way too much time trying to do a "standard" deploy of JSWPWiki
on a "Standard" deploy of Tomcat 7 and linux. (Tried Debian and Ubuntu) .
A big issue is the attempt to write the jspwiki.log to the location that it
should not be trying to write to the CATALINA_HOME for Tomcat instead of
Hi Jim,
from your log, and looking at the code, it seems that the application is
trying to find your policy file (by default, jspwiki.policy, inside the
war's WEB-INF folder), but it's unable to. Have you overriden the
jspwiki.policy.file attribute on your jspwiki-custom.properties file? It's
firs
Thanks for the continued help.
In catalina.out we see:
INFO: Deploying configuration descriptor
/etc/tomcat7/Catalina/localhost/docs.xml
May 03, 2014 8:34:32 PM org.apache.catalina.startup.HostConfig
deployDescriptor
INFO: Deploying configuration descriptor
/etc/tomcat7/Catalina/localhost/manager
Jim,
I dont know what causes the NPE, but there should be a stacktrace in
tomcat's SystemOut, can you check that?
Regards,
Harry
Op 4 mei 2014 02:37 schreef "Jim Willeke" :
> After doing that, I still only get a little further:
>
> 2014-05-03 20:08:24,390 INFO search.LuceneSearchProvider - Luce
After doing that, I still only get a little further:
2014-05-03 20:08:24,390 INFO search.LuceneSearchProvider - Lucene libraries
do not exist - not using Lucene.
2014-05-03 20:34:32,795 INFO wiki.WikiEngine -
***
2014-05-03 20:34:32,796 INFO wiki.WikiEngine
I really appreciate the help, but, this then effects all apps running on
tomcat.
There must be a better way.
I currently running older versions but have 5 wikis running as Virtual
hosts and all their configs are within the context of each host.
But, I wanted to do a clean install of one wiki to s
Jim,
you should put these files in tomcat7/lib, not in
tomcat7/webapps/ldapwiki/WEB-INF/lib.
regards,
Harry
On 3 May 2014 13:25, Jim Willeke wrote:
> Creating a creating a log4j.properties in
> tomcat7/webapps/ldapwiki/WEB-INF/lib
> does not work.
> log4j:WARN No appenders could be found for
Creating a creating a log4j.properties in tomcat7/webapps/ldapwiki/WEB-INF/lib
does not work.
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#
Hi Jim,
although the preferred way is to create a jspwiki-custom.properties file,
another option to enforce the log location would be adding a
"-Dlog4j.appender.FileLog.File=/var/lib/tomcat7/logs/jspwiki.log" parameter
to the tomcat startup script
br,
juan pablo
On Sat, May 3, 2014 at 11:22 AM
Jim,
a vanilla JSPWiki will use the log4j settings from ini/jspwiki.properties,
this file is "hidden" inside the WEB-INF/lib/jspwiki.jar file.
The default location for the logfile is jspwiki.log, which means the
current directory.
What the current directory is, depends on how you startup your tomc
New server on "Debian GNU/Linux 7 (wheezy)"
Apache Tomcat/7.0.28 JDK 1.7.0_25-b30
Deployed JSPWiki.jar from Tomcat Manager.
May 02, 2014 2:13:28 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /var/lib/tomcat7/webapps/mywiki.war
log4j:WARN No appenders
24 matches
Mail list logo
