Ah - logging - one of the hard systems problems. The logging setup even
has it's own logging :-) (for development use only - needs a code tweak
to turn on and off).
Fuseki look for logging setup in this order:
1/ System property "log4j.configuration"
2/ $FUSEKI_BASE/log4j.properties
3/ Resource loading/classpath: "log4j.properties"
4/ Resource loading/classpath: "org/apache/jena/fuseki/log4j.properties"
5/ Internal setup (an internal copy of (4) IIRC).
(4) is default the WAR file will find.
(2) should be what you want.
Andy
On 22/01/15 16:20, Trevor Donaldson wrote:
Thanks Claude. The logging is on for org.apache.jena.fuseki but the
log4j.properties file is inside fuseki.war. I guess I could open fuseki.war
and modify log4j and then rebuild fuseki.war again. That is an option.
On Thu, Jan 22, 2015 at 10:54 AM, Claude Warren <[email protected]> wrote:
We are on the very edge of my knowledge but......
The logging system must be configured somewhere (perhaps via the tomcat
logging configuration)
If you turn the logging on for the fuseki stuff (org.apache.jena.fuseki) it
might work.
Not really sure.
On Thu, Jan 22, 2015 at 3:42 PM, Trevor Donaldson <[email protected]>
wrote:
Hi all,
Is there a way to see the debug messages of fuseki while running in the
application in tomcat?
Thanks
I want the equivalent of ./fuseki-server --debug
--
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren
