jspwiki-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Willeke <...@willeke.com>
Subject Re: JSPWiki will not Start
Date Sat, 19 Jul 2014 17:23:11 GMT
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 Willeke


On Sun, May 18, 2014 at 12:58 PM, Harry Metske <harry.metske@gmail.com>
wrote:

> 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 the same tomcat.
> When you startup a vanilla JSPWiki it will try to log to jspwiki.log in the
> current directory, so depending on from where you start it, you will get
> the logfile or not. If the logfile cannot be created however, JSPWiki will
> still work (though you get an ugly stacktrace to stdout from log4j).
>
> Maybe there is one option left in this case, and that is putting a
> log4j.properties file in tomcat's webapps/JSPWiki/WEB-INF/classes
> directory.
>
> regards,
> Harry
>
>
>
> On 18 May 2014 17:42, Florian Holeczek <florian@holeczek.de> wrote:
>
> > 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 AppArmor enabled in these
> > environments? If so, it may be that the Tomcat instance needs some
> further
> > configuration, especially regarding access to additional files like
> > jspwiki.log.
> >
> > Regards
> >  Florian
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message