You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jena.apache.org by Franco Venturi <Fr...@availity.com.INVALID> on 2020/05/19 16:37:25 UTC
Fuseki 3.15.0 logging problems
I just downloaded and started Fuseki 3.15.0, and I am now receiving several error messages related to the logging subsystem when it starts up (timestamps are in UTC):
2020-05-19 15:05:43,040 main ERROR Unrecognized format specifier [d]
2020-05-19 15:05:43,116 main ERROR Unrecognized conversion specifier [d] starting at position 16 in conversion pattern.
2020-05-19 15:05:43,120 main ERROR Unrecognized format specifier [thread]
2020-05-19 15:05:43,121 main ERROR Unrecognized conversion specifier [thread] starting at position 25 in conversion pattern.
2020-05-19 15:05:43,125 main ERROR Unrecognized format specifier [level]
2020-05-19 15:05:43,126 main ERROR Unrecognized conversion specifier [level] starting at position 35 in conversion pattern.
2020-05-19 15:05:43,126 main ERROR Unrecognized format specifier [logger]
2020-05-19 15:05:43,127 main ERROR Unrecognized conversion specifier [logger] starting at position 47 in conversion pattern.
2020-05-19 15:05:43,127 main ERROR Unrecognized format specifier [msg]
2020-05-19 15:05:43,127 main ERROR Unrecognized conversion specifier [msg] starting at position 54 in conversion pattern.
2020-05-19 15:05:43,128 main ERROR Unrecognized format specifier [n]
2020-05-19 15:05:43,128 main ERROR Unrecognized conversion specifier [n] starting at position 56 in conversion pattern.
2020-05-19 15:05:43,157 main ERROR Unrecognized format specifier [d]
2020-05-19 15:05:43,161 main ERROR Unrecognized conversion specifier [d] starting at position 16 in conversion pattern.
2020-05-19 15:05:43,162 main ERROR Unrecognized format specifier [thread]
2020-05-19 15:05:43,163 main ERROR Unrecognized conversion specifier [thread] starting at position 25 in conversion pattern.
2020-05-19 15:05:43,164 main ERROR Unrecognized format specifier [level]
2020-05-19 15:05:43,165 main ERROR Unrecognized conversion specifier [level] starting at position 35 in conversion pattern.
2020-05-19 15:05:43,165 main ERROR Unrecognized format specifier [logger]
2020-05-19 15:05:43,165 main ERROR Unrecognized conversion specifier [logger] starting at position 47 in conversion pattern.
2020-05-19 15:05:43,166 main ERROR Unrecognized format specifier [msg]
2020-05-19 15:05:43,167 main ERROR Unrecognized conversion specifier [msg] starting at position 54 in conversion pattern.
2020-05-19 15:05:43,168 main ERROR Unrecognized format specifier [n]
2020-05-19 15:05:43,168 main ERROR Unrecognized conversion specifier [n] starting at position 56 in conversion pattern.
2020-05-19 15:05:43,547 main ERROR Unable to locate plugin type for Loggers
2020-05-19 15:05:43,547 main ERROR Unable to locate plugin type for Appenders
2020-05-19 15:05:43,548 main ERROR Unable to locate plugin type for ThresholdFilter
2020-05-19 15:05:43,568 main ERROR Unable to locate plugin for Logger
2020-05-19 15:05:43,569 main ERROR Unable to locate plugin for Logger
2020-05-19 15:05:43,577 main ERROR Unable to locate plugin for Logger
2020-05-19 15:05:43,578 main ERROR Unable to locate plugin for Logger
2020-05-19 15:05:43,578 main ERROR Unable to locate plugin for Logger
2020-05-19 15:05:43,579 main ERROR Unable to locate plugin for AppenderRef
2020-05-19 15:05:43,580 main ERROR Unable to locate plugin for Logger
2020-05-19 15:05:43,580 main ERROR Unable to locate plugin for Logger
2020-05-19 15:05:43,580 main ERROR Unable to locate plugin for Logger
2020-05-19 15:05:43,581 main ERROR Unable to locate plugin for Logger
2020-05-19 15:05:43,581 main ERROR Unable to locate plugin for AppenderRef
2020-05-19 15:05:43,582 main ERROR Unable to locate plugin for Root
2020-05-19 15:05:43,582 main ERROR Unable to locate plugin for Loggers
2020-05-19 15:05:43,583 main ERROR Unable to locate plugin for PatternLayout
2020-05-19 15:05:43,583 main ERROR Unable to locate plugin for Console
2020-05-19 15:05:43,584 main ERROR Unable to locate plugin for PatternLayout
2020-05-19 15:05:43,584 main ERROR Unable to locate plugin for Console
2020-05-19 15:05:43,585 main ERROR Unable to locate plugin for Appenders
2020-05-19 15:05:43,585 main ERROR Unable to locate plugin for ThresholdFilter
2020-05-19 15:05:43,586 main ERROR Unrecognized format specifier [d]
2020-05-19 15:05:43,586 main ERROR Unrecognized conversion specifier [d] starting at position 16 in conversion pattern.
2020-05-19 15:05:43,587 main ERROR Unrecognized format specifier [thread]
2020-05-19 15:05:43,587 main ERROR Unrecognized conversion specifier [thread] starting at position 25 in conversion pattern.
2020-05-19 15:05:43,588 main ERROR Unrecognized format specifier [level]
2020-05-19 15:05:43,588 main ERROR Unrecognized conversion specifier [level] starting at position 35 in conversion pattern.
2020-05-19 15:05:43,589 main ERROR Unrecognized format specifier [logger]
2020-05-19 15:05:43,589 main ERROR Unrecognized conversion specifier [logger] starting at position 47 in conversion pattern.
2020-05-19 15:05:43,590 main ERROR Unrecognized format specifier [msg]
2020-05-19 15:05:43,590 main ERROR Unrecognized conversion specifier [msg] starting at position 54 in conversion pattern.
2020-05-19 15:05:43,590 main ERROR Unrecognized format specifier [n]
2020-05-19 15:05:43,591 main ERROR Unrecognized conversion specifier [n] starting at position 56 in conversion pattern.
Since I don’t have any custom log4j/log4j2 property files, I suspect this issue could be due to JENA-1005 (https://issues.apache.org/jira/browse/JENA-1005 - Move off Log4j v1.), which was releasedd in Fuseki 3.15.0.
I am running Fuseki as system service, i.e. with just the ‘fuseki-server.jar’ in the classpath (java -cp /opt/fuseki/fuseki-server.jar org.apache.jena.fuseki.cmd.FusekiCmd).
Also I did some additional research, and I found that someone else was having a possibly similar issue here: https://www.arctype.co/blog/resolve-log4j2-conflicts-in-uberjars; if this is the case, it is due to log4j2 bug LOG4J2-673 (https://issues.apache.org/jira/browse/LOG4J2-673), which apparently won’t be resolved until log4j2 3.0.0.
That blog post also mentions of a couple of possible workarounds (https://github.com/edwgiz/maven-shaded-log4j-transformer and https://github.com/arctype-co/log4j2-plugins-cache).
Regards,
Franco Venturi
----------------------------------------------------------------------
The information contained in this e-mail may be privileged and confidential under applicable law. It is intended solely for the use of the person or firm named above. If the reader of this e-mail is not the intended recipient, please notify us immediately by returning the e-mail to the originating e-mail address. Availity, LLC is not responsible for errors or omissions in this e-mail message. Any personal comments made in this e-mail do not reflect the views of Availity, LLC.
Re: Fuseki 3.15.0 logging problems
Posted by Andy Seaborne <an...@apache.org>.
Franco,
Thank you very much for the report and investigation.
It does indeed impact the shaded jar in the apache-jena-fuseki download.
The war file form works.
The other one shaded jar - jena-fuseki-server AKA "Fuseki main"
also seems to work although I can't see why they are different.
(this form does not have a UI)
Andy
[1]
https://repo1.maven.org/maven2/org/apache/jena/jena-fuseki-server/3.15.0/
PS For running with java 11 (actually Java9 and onwards)
WARNING: sun.reflect.Reflection.getCallerClass is not supported. This
will impact performance.
is emitted - it can be ignored and is something that can be fixed.
On 19/05/2020 17:37, Franco Venturi wrote:
> I just downloaded and started Fuseki 3.15.0, and I am now receiving several error messages related to the logging subsystem when it starts up (timestamps are in UTC):
>
>
> 2020-05-19 15:05:43,040 main ERROR Unrecognized format specifier [d]
>
> 2020-05-19 15:05:43,116 main ERROR Unrecognized conversion specifier [d] starting at position 16 in conversion pattern.
>
> 2020-05-19 15:05:43,120 main ERROR Unrecognized format specifier [thread]
>
> 2020-05-19 15:05:43,121 main ERROR Unrecognized conversion specifier [thread] starting at position 25 in conversion pattern.
>
> 2020-05-19 15:05:43,125 main ERROR Unrecognized format specifier [level]
>
> 2020-05-19 15:05:43,126 main ERROR Unrecognized conversion specifier [level] starting at position 35 in conversion pattern.
>
> 2020-05-19 15:05:43,126 main ERROR Unrecognized format specifier [logger]
>
> 2020-05-19 15:05:43,127 main ERROR Unrecognized conversion specifier [logger] starting at position 47 in conversion pattern.
>
> 2020-05-19 15:05:43,127 main ERROR Unrecognized format specifier [msg]
>
> 2020-05-19 15:05:43,127 main ERROR Unrecognized conversion specifier [msg] starting at position 54 in conversion pattern.
>
> 2020-05-19 15:05:43,128 main ERROR Unrecognized format specifier [n]
>
> 2020-05-19 15:05:43,128 main ERROR Unrecognized conversion specifier [n] starting at position 56 in conversion pattern.
>
> 2020-05-19 15:05:43,157 main ERROR Unrecognized format specifier [d]
>
> 2020-05-19 15:05:43,161 main ERROR Unrecognized conversion specifier [d] starting at position 16 in conversion pattern.
>
> 2020-05-19 15:05:43,162 main ERROR Unrecognized format specifier [thread]
>
> 2020-05-19 15:05:43,163 main ERROR Unrecognized conversion specifier [thread] starting at position 25 in conversion pattern.
>
> 2020-05-19 15:05:43,164 main ERROR Unrecognized format specifier [level]
>
> 2020-05-19 15:05:43,165 main ERROR Unrecognized conversion specifier [level] starting at position 35 in conversion pattern.
>
> 2020-05-19 15:05:43,165 main ERROR Unrecognized format specifier [logger]
>
> 2020-05-19 15:05:43,165 main ERROR Unrecognized conversion specifier [logger] starting at position 47 in conversion pattern.
>
> 2020-05-19 15:05:43,166 main ERROR Unrecognized format specifier [msg]
>
> 2020-05-19 15:05:43,167 main ERROR Unrecognized conversion specifier [msg] starting at position 54 in conversion pattern.
>
> 2020-05-19 15:05:43,168 main ERROR Unrecognized format specifier [n]
>
> 2020-05-19 15:05:43,168 main ERROR Unrecognized conversion specifier [n] starting at position 56 in conversion pattern.
>
> 2020-05-19 15:05:43,547 main ERROR Unable to locate plugin type for Loggers
>
> 2020-05-19 15:05:43,547 main ERROR Unable to locate plugin type for Appenders
>
> 2020-05-19 15:05:43,548 main ERROR Unable to locate plugin type for ThresholdFilter
>
> 2020-05-19 15:05:43,568 main ERROR Unable to locate plugin for Logger
>
> 2020-05-19 15:05:43,569 main ERROR Unable to locate plugin for Logger
>
> 2020-05-19 15:05:43,577 main ERROR Unable to locate plugin for Logger
>
> 2020-05-19 15:05:43,578 main ERROR Unable to locate plugin for Logger
>
> 2020-05-19 15:05:43,578 main ERROR Unable to locate plugin for Logger
>
> 2020-05-19 15:05:43,579 main ERROR Unable to locate plugin for AppenderRef
>
> 2020-05-19 15:05:43,580 main ERROR Unable to locate plugin for Logger
>
> 2020-05-19 15:05:43,580 main ERROR Unable to locate plugin for Logger
>
> 2020-05-19 15:05:43,580 main ERROR Unable to locate plugin for Logger
>
> 2020-05-19 15:05:43,581 main ERROR Unable to locate plugin for Logger
>
> 2020-05-19 15:05:43,581 main ERROR Unable to locate plugin for AppenderRef
>
> 2020-05-19 15:05:43,582 main ERROR Unable to locate plugin for Root
>
> 2020-05-19 15:05:43,582 main ERROR Unable to locate plugin for Loggers
>
> 2020-05-19 15:05:43,583 main ERROR Unable to locate plugin for PatternLayout
>
> 2020-05-19 15:05:43,583 main ERROR Unable to locate plugin for Console
>
> 2020-05-19 15:05:43,584 main ERROR Unable to locate plugin for PatternLayout
>
> 2020-05-19 15:05:43,584 main ERROR Unable to locate plugin for Console
>
> 2020-05-19 15:05:43,585 main ERROR Unable to locate plugin for Appenders
>
> 2020-05-19 15:05:43,585 main ERROR Unable to locate plugin for ThresholdFilter
>
> 2020-05-19 15:05:43,586 main ERROR Unrecognized format specifier [d]
>
> 2020-05-19 15:05:43,586 main ERROR Unrecognized conversion specifier [d] starting at position 16 in conversion pattern.
>
> 2020-05-19 15:05:43,587 main ERROR Unrecognized format specifier [thread]
>
> 2020-05-19 15:05:43,587 main ERROR Unrecognized conversion specifier [thread] starting at position 25 in conversion pattern.
>
> 2020-05-19 15:05:43,588 main ERROR Unrecognized format specifier [level]
>
> 2020-05-19 15:05:43,588 main ERROR Unrecognized conversion specifier [level] starting at position 35 in conversion pattern.
>
> 2020-05-19 15:05:43,589 main ERROR Unrecognized format specifier [logger]
>
> 2020-05-19 15:05:43,589 main ERROR Unrecognized conversion specifier [logger] starting at position 47 in conversion pattern.
>
> 2020-05-19 15:05:43,590 main ERROR Unrecognized format specifier [msg]
>
> 2020-05-19 15:05:43,590 main ERROR Unrecognized conversion specifier [msg] starting at position 54 in conversion pattern.
>
> 2020-05-19 15:05:43,590 main ERROR Unrecognized format specifier [n]
>
> 2020-05-19 15:05:43,591 main ERROR Unrecognized conversion specifier [n] starting at position 56 in conversion pattern.
>
> Since I don’t have any custom log4j/log4j2 property files, I suspect this issue could be due to JENA-1005 (https://issues.apache.org/jira/browse/JENA-1005 - Move off Log4j v1.), which was releasedd in Fuseki 3.15.0.
>
> I am running Fuseki as system service, i.e. with just the ‘fuseki-server.jar’ in the classpath (java -cp /opt/fuseki/fuseki-server.jar org.apache.jena.fuseki.cmd.FusekiCmd).
>
> Also I did some additional research, and I found that someone else was having a possibly similar issue here: https://www.arctype.co/blog/resolve-log4j2-conflicts-in-uberjars; if this is the case, it is due to log4j2 bug LOG4J2-673 (https://issues.apache.org/jira/browse/LOG4J2-673), which apparently won’t be resolved until log4j2 3.0.0.
> That blog post also mentions of a couple of possible workarounds (https://github.com/edwgiz/maven-shaded-log4j-transformer and https://github.com/arctype-co/log4j2-plugins-cache).
>
> Regards,
> Franco Venturi
>
> ----------------------------------------------------------------------
> The information contained in this e-mail may be privileged and confidential under applicable law. It is intended solely for the use of the person or firm named above. If the reader of this e-mail is not the intended recipient, please notify us immediately by returning the e-mail to the originating e-mail address. Availity, LLC is not responsible for errors or omissions in this e-mail message. Any personal comments made in this e-mail do not reflect the views of Availity, LLC.
>
Re: Fwd: Fuseki 3.15.0 logging problems
Posted by Andy Seaborne <an...@apache.org>.
Proposed proper fix
https://github.com/apache/jena/pull/747
and the PR comments explain what the fix is.
In the end, the 3rd party shade transformer [1] wasn't necessary and
because it is quite sensitive to the version of the shade plugin and to
the log4j2 version, seems better to simply exclude the unnecessary
dependency.
This needs a good shake down and testing once it is merged. Then we can
see just how much of a pain the log is to users.
We could release as a 3.15.1 if necessary - it woudl stil be an idea rto
wait to see if other problems arise.
Another possibility is an earlier 3.16.0 with real improvements.
Andy
[1] https://github.com/edwgiz/maven-shaded-log4j-transformer
On 20/05/2020 10:02, Andy Seaborne wrote:
>
>
> On 20/05/2020 09:49, Andy Seaborne wrote:
>> You may have seem there is a problem with Fuseki fulljar - the log4j2
>> setup is broken by shading.
>>
>> The jena-fuseki-server jar works - but that is beginning to look like
>> it is due to chance.
>>
>> Recorded as https://issues.apache.org/jira/browse/JENA-1900
>>
>> Details:
>>
>> https://lists.apache.org/thread.html/r794a7cc390a275f5db85541cbedf58666802fa987ae5b09aed49e61d%40%3Cusers.jena.apache.org%3E
>>
>>
>> I haven't found a workaround that will fix the released system - I was
>> hoping that a suitable log4j2.properties would at least mitigate the
>> problem but it is now looking to be more fundamental than that. A last
>> hope is to fix the jar file with a script.
>
> Monkey patching the jar file works! Replace the offending file -
> Log4j2Plugins.dat - with the one from jena-fuseki-server.
>
> (It is binary so that's tricky to put into a generally safe script)
>
> Andy
>
>>
>> The shade transformer solution does work but that's a rebuild.
>>
>> Andy
>>
>> -------- Forwarded Message --------
>> Subject: Fuseki 3.15.0 logging problems
>> Date: Tue, 19 May 2020 16:37:25 +0000
>> From: Franco Venturi <Fr...@availity.com.INVALID>
>> Reply-To: users@jena.apache.org
>> To: users@jena.apache.org <us...@jena.apache.org>
>>
>> I just downloaded and started Fuseki 3.15.0, and I am now receiving
>> several error messages related to the logging subsystem when it starts
>> up (timestamps are in UTC):
>>
>>
>> 2020-05-19 15:05:43,040 main ERROR Unrecognized format specifier [d]
>>
>> 2020-05-19 15:05:43,116 main ERROR Unrecognized conversion specifier
>> [d] starting at position 16 in conversion pattern.
>>
>> 2020-05-19 15:05:43,120 main ERROR Unrecognized format specifier [thread]
>>
>> 2020-05-19 15:05:43,121 main ERROR Unrecognized conversion specifier
>> [thread] starting at position 25 in conversion pattern.
>>
>> 2020-05-19 15:05:43,125 main ERROR Unrecognized format specifier [level]
>>
>> 2020-05-19 15:05:43,126 main ERROR Unrecognized conversion specifier
>> [level] starting at position 35 in conversion pattern.
>>
>> 2020-05-19 15:05:43,126 main ERROR Unrecognized format specifier [logger]
>>
>> 2020-05-19 15:05:43,127 main ERROR Unrecognized conversion specifier
>> [logger] starting at position 47 in conversion pattern.
>>
>> 2020-05-19 15:05:43,127 main ERROR Unrecognized format specifier [msg]
>>
>> 2020-05-19 15:05:43,127 main ERROR Unrecognized conversion specifier
>> [msg] starting at position 54 in conversion pattern.
>>
>> 2020-05-19 15:05:43,128 main ERROR Unrecognized format specifier [n]
>>
>> 2020-05-19 15:05:43,128 main ERROR Unrecognized conversion specifier
>> [n] starting at position 56 in conversion pattern.
>>
>> 2020-05-19 15:05:43,157 main ERROR Unrecognized format specifier [d]
>>
>> 2020-05-19 15:05:43,161 main ERROR Unrecognized conversion specifier
>> [d] starting at position 16 in conversion pattern.
>>
>> 2020-05-19 15:05:43,162 main ERROR Unrecognized format specifier [thread]
>>
>> 2020-05-19 15:05:43,163 main ERROR Unrecognized conversion specifier
>> [thread] starting at position 25 in conversion pattern.
>>
>> 2020-05-19 15:05:43,164 main ERROR Unrecognized format specifier [level]
>>
>> 2020-05-19 15:05:43,165 main ERROR Unrecognized conversion specifier
>> [level] starting at position 35 in conversion pattern.
>>
>> 2020-05-19 15:05:43,165 main ERROR Unrecognized format specifier [logger]
>>
>> 2020-05-19 15:05:43,165 main ERROR Unrecognized conversion specifier
>> [logger] starting at position 47 in conversion pattern.
>>
>> 2020-05-19 15:05:43,166 main ERROR Unrecognized format specifier [msg]
>>
>> 2020-05-19 15:05:43,167 main ERROR Unrecognized conversion specifier
>> [msg] starting at position 54 in conversion pattern.
>>
>> 2020-05-19 15:05:43,168 main ERROR Unrecognized format specifier [n]
>>
>> 2020-05-19 15:05:43,168 main ERROR Unrecognized conversion specifier
>> [n] starting at position 56 in conversion pattern.
>>
>> 2020-05-19 15:05:43,547 main ERROR Unable to locate plugin type for
>> Loggers
>>
>> 2020-05-19 15:05:43,547 main ERROR Unable to locate plugin type for
>> Appenders
>>
>> 2020-05-19 15:05:43,548 main ERROR Unable to locate plugin type for
>> ThresholdFilter
>>
>> 2020-05-19 15:05:43,568 main ERROR Unable to locate plugin for Logger
>>
>> 2020-05-19 15:05:43,569 main ERROR Unable to locate plugin for Logger
>>
>> 2020-05-19 15:05:43,577 main ERROR Unable to locate plugin for Logger
>>
>> 2020-05-19 15:05:43,578 main ERROR Unable to locate plugin for Logger
>>
>> 2020-05-19 15:05:43,578 main ERROR Unable to locate plugin for Logger
>>
>> 2020-05-19 15:05:43,579 main ERROR Unable to locate plugin for
>> AppenderRef
>>
>> 2020-05-19 15:05:43,580 main ERROR Unable to locate plugin for Logger
>>
>> 2020-05-19 15:05:43,580 main ERROR Unable to locate plugin for Logger
>>
>> 2020-05-19 15:05:43,580 main ERROR Unable to locate plugin for Logger
>>
>> 2020-05-19 15:05:43,581 main ERROR Unable to locate plugin for Logger
>>
>> 2020-05-19 15:05:43,581 main ERROR Unable to locate plugin for
>> AppenderRef
>>
>> 2020-05-19 15:05:43,582 main ERROR Unable to locate plugin for Root
>>
>> 2020-05-19 15:05:43,582 main ERROR Unable to locate plugin for Loggers
>>
>> 2020-05-19 15:05:43,583 main ERROR Unable to locate plugin for
>> PatternLayout
>>
>> 2020-05-19 15:05:43,583 main ERROR Unable to locate plugin for Console
>>
>> 2020-05-19 15:05:43,584 main ERROR Unable to locate plugin for
>> PatternLayout
>>
>> 2020-05-19 15:05:43,584 main ERROR Unable to locate plugin for Console
>>
>> 2020-05-19 15:05:43,585 main ERROR Unable to locate plugin for Appenders
>>
>> 2020-05-19 15:05:43,585 main ERROR Unable to locate plugin for
>> ThresholdFilter
>>
>> 2020-05-19 15:05:43,586 main ERROR Unrecognized format specifier [d]
>>
>> 2020-05-19 15:05:43,586 main ERROR Unrecognized conversion specifier
>> [d] starting at position 16 in conversion pattern.
>>
>> 2020-05-19 15:05:43,587 main ERROR Unrecognized format specifier [thread]
>>
>> 2020-05-19 15:05:43,587 main ERROR Unrecognized conversion specifier
>> [thread] starting at position 25 in conversion pattern.
>>
>> 2020-05-19 15:05:43,588 main ERROR Unrecognized format specifier [level]
>>
>> 2020-05-19 15:05:43,588 main ERROR Unrecognized conversion specifier
>> [level] starting at position 35 in conversion pattern.
>>
>> 2020-05-19 15:05:43,589 main ERROR Unrecognized format specifier [logger]
>>
>> 2020-05-19 15:05:43,589 main ERROR Unrecognized conversion specifier
>> [logger] starting at position 47 in conversion pattern.
>>
>> 2020-05-19 15:05:43,590 main ERROR Unrecognized format specifier [msg]
>>
>> 2020-05-19 15:05:43,590 main ERROR Unrecognized conversion specifier
>> [msg] starting at position 54 in conversion pattern.
>>
>> 2020-05-19 15:05:43,590 main ERROR Unrecognized format specifier [n]
>>
>> 2020-05-19 15:05:43,591 main ERROR Unrecognized conversion specifier
>> [n] starting at position 56 in conversion pattern.
>>
>> Since I don’t have any custom log4j/log4j2 property files, I suspect
>> this issue could be due to JENA-1005
>> (https://issues.apache.org/jira/browse/JENA-1005 - Move off Log4j
>> v1.), which was releasedd in Fuseki 3.15.0.
>>
>> I am running Fuseki as system service, i.e. with just the
>> ‘fuseki-server.jar’ in the classpath (java -cp
>> /opt/fuseki/fuseki-server.jar org.apache.jena.fuseki.cmd.FusekiCmd).
>>
>> Also I did some additional research, and I found that someone else was
>> having a possibly similar issue here:
>> https://www.arctype.co/blog/resolve-log4j2-conflicts-in-uberjars; if
>> this is the case, it is due to log4j2 bug LOG4J2-673
>> (https://issues.apache.org/jira/browse/LOG4J2-673), which apparently
>> won’t be resolved until log4j2 3.0.0.
>> That blog post also mentions of a couple of possible workarounds
>> (https://github.com/edwgiz/maven-shaded-log4j-transformer and
>> https://github.com/arctype-co/log4j2-plugins-cache).
>>
>> Regards,
>> Franco Venturi
>>
>> ----------------------------------------------------------------------
>> The information contained in this e-mail may be privileged and
>> confidential under applicable law. It is intended solely for the use
>> of the person or firm named above. If the reader of this e-mail is not
>> the intended recipient, please notify us immediately by returning the
>> e-mail to the originating e-mail address. Availity, LLC is not
>> responsible for errors or omissions in this e-mail message. Any
>> personal comments made in this e-mail do not reflect the views of
>> Availity, LLC.
Re: Fwd: Fuseki 3.15.0 logging problems
Posted by Andy Seaborne <an...@apache.org>.
On 20/05/2020 09:49, Andy Seaborne wrote:
> You may have seem there is a problem with Fuseki fulljar - the log4j2
> setup is broken by shading.
>
> The jena-fuseki-server jar works - but that is beginning to look like it
> is due to chance.
>
> Recorded as https://issues.apache.org/jira/browse/JENA-1900
>
> Details:
>
> https://lists.apache.org/thread.html/r794a7cc390a275f5db85541cbedf58666802fa987ae5b09aed49e61d%40%3Cusers.jena.apache.org%3E
>
>
> I haven't found a workaround that will fix the released system - I was
> hoping that a suitable log4j2.properties would at least mitigate the
> problem but it is now looking to be more fundamental than that. A last
> hope is to fix the jar file with a script.
Monkey patching the jar file works! Replace the offending file -
Log4j2Plugins.dat - with the one from jena-fuseki-server.
(It is binary so that's tricky to put into a generally safe script)
Andy
>
> The shade transformer solution does work but that's a rebuild.
>
> Andy
>
> -------- Forwarded Message --------
> Subject: Fuseki 3.15.0 logging problems
> Date: Tue, 19 May 2020 16:37:25 +0000
> From: Franco Venturi <Fr...@availity.com.INVALID>
> Reply-To: users@jena.apache.org
> To: users@jena.apache.org <us...@jena.apache.org>
>
> I just downloaded and started Fuseki 3.15.0, and I am now receiving
> several error messages related to the logging subsystem when it starts
> up (timestamps are in UTC):
>
>
> 2020-05-19 15:05:43,040 main ERROR Unrecognized format specifier [d]
>
> 2020-05-19 15:05:43,116 main ERROR Unrecognized conversion specifier [d]
> starting at position 16 in conversion pattern.
>
> 2020-05-19 15:05:43,120 main ERROR Unrecognized format specifier [thread]
>
> 2020-05-19 15:05:43,121 main ERROR Unrecognized conversion specifier
> [thread] starting at position 25 in conversion pattern.
>
> 2020-05-19 15:05:43,125 main ERROR Unrecognized format specifier [level]
>
> 2020-05-19 15:05:43,126 main ERROR Unrecognized conversion specifier
> [level] starting at position 35 in conversion pattern.
>
> 2020-05-19 15:05:43,126 main ERROR Unrecognized format specifier [logger]
>
> 2020-05-19 15:05:43,127 main ERROR Unrecognized conversion specifier
> [logger] starting at position 47 in conversion pattern.
>
> 2020-05-19 15:05:43,127 main ERROR Unrecognized format specifier [msg]
>
> 2020-05-19 15:05:43,127 main ERROR Unrecognized conversion specifier
> [msg] starting at position 54 in conversion pattern.
>
> 2020-05-19 15:05:43,128 main ERROR Unrecognized format specifier [n]
>
> 2020-05-19 15:05:43,128 main ERROR Unrecognized conversion specifier [n]
> starting at position 56 in conversion pattern.
>
> 2020-05-19 15:05:43,157 main ERROR Unrecognized format specifier [d]
>
> 2020-05-19 15:05:43,161 main ERROR Unrecognized conversion specifier [d]
> starting at position 16 in conversion pattern.
>
> 2020-05-19 15:05:43,162 main ERROR Unrecognized format specifier [thread]
>
> 2020-05-19 15:05:43,163 main ERROR Unrecognized conversion specifier
> [thread] starting at position 25 in conversion pattern.
>
> 2020-05-19 15:05:43,164 main ERROR Unrecognized format specifier [level]
>
> 2020-05-19 15:05:43,165 main ERROR Unrecognized conversion specifier
> [level] starting at position 35 in conversion pattern.
>
> 2020-05-19 15:05:43,165 main ERROR Unrecognized format specifier [logger]
>
> 2020-05-19 15:05:43,165 main ERROR Unrecognized conversion specifier
> [logger] starting at position 47 in conversion pattern.
>
> 2020-05-19 15:05:43,166 main ERROR Unrecognized format specifier [msg]
>
> 2020-05-19 15:05:43,167 main ERROR Unrecognized conversion specifier
> [msg] starting at position 54 in conversion pattern.
>
> 2020-05-19 15:05:43,168 main ERROR Unrecognized format specifier [n]
>
> 2020-05-19 15:05:43,168 main ERROR Unrecognized conversion specifier [n]
> starting at position 56 in conversion pattern.
>
> 2020-05-19 15:05:43,547 main ERROR Unable to locate plugin type for Loggers
>
> 2020-05-19 15:05:43,547 main ERROR Unable to locate plugin type for
> Appenders
>
> 2020-05-19 15:05:43,548 main ERROR Unable to locate plugin type for
> ThresholdFilter
>
> 2020-05-19 15:05:43,568 main ERROR Unable to locate plugin for Logger
>
> 2020-05-19 15:05:43,569 main ERROR Unable to locate plugin for Logger
>
> 2020-05-19 15:05:43,577 main ERROR Unable to locate plugin for Logger
>
> 2020-05-19 15:05:43,578 main ERROR Unable to locate plugin for Logger
>
> 2020-05-19 15:05:43,578 main ERROR Unable to locate plugin for Logger
>
> 2020-05-19 15:05:43,579 main ERROR Unable to locate plugin for AppenderRef
>
> 2020-05-19 15:05:43,580 main ERROR Unable to locate plugin for Logger
>
> 2020-05-19 15:05:43,580 main ERROR Unable to locate plugin for Logger
>
> 2020-05-19 15:05:43,580 main ERROR Unable to locate plugin for Logger
>
> 2020-05-19 15:05:43,581 main ERROR Unable to locate plugin for Logger
>
> 2020-05-19 15:05:43,581 main ERROR Unable to locate plugin for AppenderRef
>
> 2020-05-19 15:05:43,582 main ERROR Unable to locate plugin for Root
>
> 2020-05-19 15:05:43,582 main ERROR Unable to locate plugin for Loggers
>
> 2020-05-19 15:05:43,583 main ERROR Unable to locate plugin for
> PatternLayout
>
> 2020-05-19 15:05:43,583 main ERROR Unable to locate plugin for Console
>
> 2020-05-19 15:05:43,584 main ERROR Unable to locate plugin for
> PatternLayout
>
> 2020-05-19 15:05:43,584 main ERROR Unable to locate plugin for Console
>
> 2020-05-19 15:05:43,585 main ERROR Unable to locate plugin for Appenders
>
> 2020-05-19 15:05:43,585 main ERROR Unable to locate plugin for
> ThresholdFilter
>
> 2020-05-19 15:05:43,586 main ERROR Unrecognized format specifier [d]
>
> 2020-05-19 15:05:43,586 main ERROR Unrecognized conversion specifier [d]
> starting at position 16 in conversion pattern.
>
> 2020-05-19 15:05:43,587 main ERROR Unrecognized format specifier [thread]
>
> 2020-05-19 15:05:43,587 main ERROR Unrecognized conversion specifier
> [thread] starting at position 25 in conversion pattern.
>
> 2020-05-19 15:05:43,588 main ERROR Unrecognized format specifier [level]
>
> 2020-05-19 15:05:43,588 main ERROR Unrecognized conversion specifier
> [level] starting at position 35 in conversion pattern.
>
> 2020-05-19 15:05:43,589 main ERROR Unrecognized format specifier [logger]
>
> 2020-05-19 15:05:43,589 main ERROR Unrecognized conversion specifier
> [logger] starting at position 47 in conversion pattern.
>
> 2020-05-19 15:05:43,590 main ERROR Unrecognized format specifier [msg]
>
> 2020-05-19 15:05:43,590 main ERROR Unrecognized conversion specifier
> [msg] starting at position 54 in conversion pattern.
>
> 2020-05-19 15:05:43,590 main ERROR Unrecognized format specifier [n]
>
> 2020-05-19 15:05:43,591 main ERROR Unrecognized conversion specifier [n]
> starting at position 56 in conversion pattern.
>
> Since I don’t have any custom log4j/log4j2 property files, I suspect
> this issue could be due to JENA-1005
> (https://issues.apache.org/jira/browse/JENA-1005 - Move off Log4j v1.),
> which was releasedd in Fuseki 3.15.0.
>
> I am running Fuseki as system service, i.e. with just the
> ‘fuseki-server.jar’ in the classpath (java -cp
> /opt/fuseki/fuseki-server.jar org.apache.jena.fuseki.cmd.FusekiCmd).
>
> Also I did some additional research, and I found that someone else was
> having a possibly similar issue here:
> https://www.arctype.co/blog/resolve-log4j2-conflicts-in-uberjars; if
> this is the case, it is due to log4j2 bug LOG4J2-673
> (https://issues.apache.org/jira/browse/LOG4J2-673), which apparently
> won’t be resolved until log4j2 3.0.0.
> That blog post also mentions of a couple of possible workarounds
> (https://github.com/edwgiz/maven-shaded-log4j-transformer and
> https://github.com/arctype-co/log4j2-plugins-cache).
>
> Regards,
> Franco Venturi
>
> ----------------------------------------------------------------------
> The information contained in this e-mail may be privileged and
> confidential under applicable law. It is intended solely for the use of
> the person or firm named above. If the reader of this e-mail is not the
> intended recipient, please notify us immediately by returning the e-mail
> to the originating e-mail address. Availity, LLC is not responsible for
> errors or omissions in this e-mail message. Any personal comments made
> in this e-mail do not reflect the views of Availity, LLC.
Fwd: Fuseki 3.15.0 logging problems
Posted by Andy Seaborne <an...@apache.org>.
You may have seem there is a problem with Fuseki fulljar - the log4j2
setup is broken by shading.
The jena-fuseki-server jar works - but that is beginning to look like it
is due to chance.
Recorded as https://issues.apache.org/jira/browse/JENA-1900
Details:
https://lists.apache.org/thread.html/r794a7cc390a275f5db85541cbedf58666802fa987ae5b09aed49e61d%40%3Cusers.jena.apache.org%3E
I haven't found a workaround that will fix the released system - I was
hoping that a suitable log4j2.properties would at least mitigate the
problem but it is now looking to be more fundamental than that. A last
hope is to fix the jar file with a script.
The shade transformer solution does work but that's a rebuild.
Andy
-------- Forwarded Message --------
Subject: Fuseki 3.15.0 logging problems
Date: Tue, 19 May 2020 16:37:25 +0000
From: Franco Venturi <Fr...@availity.com.INVALID>
Reply-To: users@jena.apache.org
To: users@jena.apache.org <us...@jena.apache.org>
I just downloaded and started Fuseki 3.15.0, and I am now receiving
several error messages related to the logging subsystem when it starts
up (timestamps are in UTC):
2020-05-19 15:05:43,040 main ERROR Unrecognized format specifier [d]
2020-05-19 15:05:43,116 main ERROR Unrecognized conversion specifier [d]
starting at position 16 in conversion pattern.
2020-05-19 15:05:43,120 main ERROR Unrecognized format specifier [thread]
2020-05-19 15:05:43,121 main ERROR Unrecognized conversion specifier
[thread] starting at position 25 in conversion pattern.
2020-05-19 15:05:43,125 main ERROR Unrecognized format specifier [level]
2020-05-19 15:05:43,126 main ERROR Unrecognized conversion specifier
[level] starting at position 35 in conversion pattern.
2020-05-19 15:05:43,126 main ERROR Unrecognized format specifier [logger]
2020-05-19 15:05:43,127 main ERROR Unrecognized conversion specifier
[logger] starting at position 47 in conversion pattern.
2020-05-19 15:05:43,127 main ERROR Unrecognized format specifier [msg]
2020-05-19 15:05:43,127 main ERROR Unrecognized conversion specifier
[msg] starting at position 54 in conversion pattern.
2020-05-19 15:05:43,128 main ERROR Unrecognized format specifier [n]
2020-05-19 15:05:43,128 main ERROR Unrecognized conversion specifier [n]
starting at position 56 in conversion pattern.
2020-05-19 15:05:43,157 main ERROR Unrecognized format specifier [d]
2020-05-19 15:05:43,161 main ERROR Unrecognized conversion specifier [d]
starting at position 16 in conversion pattern.
2020-05-19 15:05:43,162 main ERROR Unrecognized format specifier [thread]
2020-05-19 15:05:43,163 main ERROR Unrecognized conversion specifier
[thread] starting at position 25 in conversion pattern.
2020-05-19 15:05:43,164 main ERROR Unrecognized format specifier [level]
2020-05-19 15:05:43,165 main ERROR Unrecognized conversion specifier
[level] starting at position 35 in conversion pattern.
2020-05-19 15:05:43,165 main ERROR Unrecognized format specifier [logger]
2020-05-19 15:05:43,165 main ERROR Unrecognized conversion specifier
[logger] starting at position 47 in conversion pattern.
2020-05-19 15:05:43,166 main ERROR Unrecognized format specifier [msg]
2020-05-19 15:05:43,167 main ERROR Unrecognized conversion specifier
[msg] starting at position 54 in conversion pattern.
2020-05-19 15:05:43,168 main ERROR Unrecognized format specifier [n]
2020-05-19 15:05:43,168 main ERROR Unrecognized conversion specifier [n]
starting at position 56 in conversion pattern.
2020-05-19 15:05:43,547 main ERROR Unable to locate plugin type for Loggers
2020-05-19 15:05:43,547 main ERROR Unable to locate plugin type for
Appenders
2020-05-19 15:05:43,548 main ERROR Unable to locate plugin type for
ThresholdFilter
2020-05-19 15:05:43,568 main ERROR Unable to locate plugin for Logger
2020-05-19 15:05:43,569 main ERROR Unable to locate plugin for Logger
2020-05-19 15:05:43,577 main ERROR Unable to locate plugin for Logger
2020-05-19 15:05:43,578 main ERROR Unable to locate plugin for Logger
2020-05-19 15:05:43,578 main ERROR Unable to locate plugin for Logger
2020-05-19 15:05:43,579 main ERROR Unable to locate plugin for AppenderRef
2020-05-19 15:05:43,580 main ERROR Unable to locate plugin for Logger
2020-05-19 15:05:43,580 main ERROR Unable to locate plugin for Logger
2020-05-19 15:05:43,580 main ERROR Unable to locate plugin for Logger
2020-05-19 15:05:43,581 main ERROR Unable to locate plugin for Logger
2020-05-19 15:05:43,581 main ERROR Unable to locate plugin for AppenderRef
2020-05-19 15:05:43,582 main ERROR Unable to locate plugin for Root
2020-05-19 15:05:43,582 main ERROR Unable to locate plugin for Loggers
2020-05-19 15:05:43,583 main ERROR Unable to locate plugin for PatternLayout
2020-05-19 15:05:43,583 main ERROR Unable to locate plugin for Console
2020-05-19 15:05:43,584 main ERROR Unable to locate plugin for PatternLayout
2020-05-19 15:05:43,584 main ERROR Unable to locate plugin for Console
2020-05-19 15:05:43,585 main ERROR Unable to locate plugin for Appenders
2020-05-19 15:05:43,585 main ERROR Unable to locate plugin for
ThresholdFilter
2020-05-19 15:05:43,586 main ERROR Unrecognized format specifier [d]
2020-05-19 15:05:43,586 main ERROR Unrecognized conversion specifier [d]
starting at position 16 in conversion pattern.
2020-05-19 15:05:43,587 main ERROR Unrecognized format specifier [thread]
2020-05-19 15:05:43,587 main ERROR Unrecognized conversion specifier
[thread] starting at position 25 in conversion pattern.
2020-05-19 15:05:43,588 main ERROR Unrecognized format specifier [level]
2020-05-19 15:05:43,588 main ERROR Unrecognized conversion specifier
[level] starting at position 35 in conversion pattern.
2020-05-19 15:05:43,589 main ERROR Unrecognized format specifier [logger]
2020-05-19 15:05:43,589 main ERROR Unrecognized conversion specifier
[logger] starting at position 47 in conversion pattern.
2020-05-19 15:05:43,590 main ERROR Unrecognized format specifier [msg]
2020-05-19 15:05:43,590 main ERROR Unrecognized conversion specifier
[msg] starting at position 54 in conversion pattern.
2020-05-19 15:05:43,590 main ERROR Unrecognized format specifier [n]
2020-05-19 15:05:43,591 main ERROR Unrecognized conversion specifier [n]
starting at position 56 in conversion pattern.
Since I don’t have any custom log4j/log4j2 property files, I suspect
this issue could be due to JENA-1005
(https://issues.apache.org/jira/browse/JENA-1005 - Move off Log4j v1.),
which was releasedd in Fuseki 3.15.0.
I am running Fuseki as system service, i.e. with just the
‘fuseki-server.jar’ in the classpath (java -cp
/opt/fuseki/fuseki-server.jar org.apache.jena.fuseki.cmd.FusekiCmd).
Also I did some additional research, and I found that someone else was
having a possibly similar issue here:
https://www.arctype.co/blog/resolve-log4j2-conflicts-in-uberjars; if
this is the case, it is due to log4j2 bug LOG4J2-673
(https://issues.apache.org/jira/browse/LOG4J2-673), which apparently
won’t be resolved until log4j2 3.0.0.
That blog post also mentions of a couple of possible workarounds
(https://github.com/edwgiz/maven-shaded-log4j-transformer and
https://github.com/arctype-co/log4j2-plugins-cache).
Regards,
Franco Venturi
----------------------------------------------------------------------
The information contained in this e-mail may be privileged and
confidential under applicable law. It is intended solely for the use of
the person or firm named above. If the reader of this e-mail is not the
intended recipient, please notify us immediately by returning the e-mail
to the originating e-mail address. Availity, LLC is not responsible for
errors or omissions in this e-mail message. Any personal comments made
in this e-mail do not reflect the views of Availity, LLC.
Re: Fuseki 3.15.0 logging problems
Posted by Andy Seaborne <an...@apache.org>.
> https://issues.apache.org/jira/browse/JENA-1900
Emergency fix:
https://gist.github.com/afs/a862c0e71b37ce617cd0a592b60609f1
This bash script downloads jena-fuseki-server-3.15.0.jar which does not
have the same problem, extract the "Log4j2Plugins.dat", then replaces
the file in fuseki-server.jar.
An alternative to consider is using jena-fuseki-server as a service. It
doe snot have a UI nor maintain a "run/" area - instead it uses a
command line arguments, including a configuration file argument, each
time it is started
Andy
Re: Fuseki 3.15.0 logging problems
Posted by Andy Seaborne <an...@apache.org>.
Recorded as
https://issues.apache.org/jira/browse/JENA-1900
The extra transformer plugin seems to fix the problem.
The problem is that there are several log4j2 "dat" files (in a manner
similar to ServiceLoader files loading META-INF/services) and shading
without modification will pick one, not combine them.
What is not clear is why the fulljar fails but the main server jar
works. This might be down to random order of combining the log4j2
plugin dat files keeping one that works for the limited use of log4j2 in
Fuseki by default.
Thank you Franco for the report - and the fix!
Andy