[jira] [Commented] (LOG4J2-1086) SizeBasedTriggeringPolicy is not working properly
[
https://issues.apache.org/jira/browse/LOG4J2-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16135855#comment-16135855
]
Pierrick HYMBERT commented on LOG4J2-1086:
--
Hi Ralph,
agreed thanks for your feedback, then need another test case to reproduce this
issue if exists.
> SizeBasedTriggeringPolicy is not working properly
> -
>
> Key: LOG4J2-1086
> URL: https://issues.apache.org/jira/browse/LOG4J2-1086
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.3, 2.4.1, 2.8
> Environment: Windows 7 OS Websphere 8.5.5.6
>Reporter: Sharat
>Assignee: Ralph Goers
>Priority: Minor
> Labels: features
> Attachments: LOG4J2-1086.Test.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> {code}
>
>
>
> filePattern="/logs/test-%i.log">
>
> %d %-5p %class{36} (%M:%L)
> -%msg%xEx%n
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LOG4J2-1725) RollingFileAppender's filePattern not reloaded when using monitorInterval
[
https://issues.apache.org/jira/browse/LOG4J2-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076109#comment-16076109
]
Pierrick HYMBERT commented on LOG4J2-1725:
--
Resolved and in git master, thank you.
> RollingFileAppender's filePattern not reloaded when using monitorInterval
> -
>
> Key: LOG4J2-1725
> URL: https://issues.apache.org/jira/browse/LOG4J2-1725
> Project: Log4j 2
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Benjamin Jaton
>
> Using the configuration below:
> {code}
>
>
> fileName="/usr/local/apps/testlogging/logs/app.log"
> filePattern="/usr/local/apps/testlogging/logs/app.log.%i">
>
> %d %p %c{1.} [%t] %m%n
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Updating the filePattern to app.log.%i.zip won't be taken into account
> dynamically.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LOG4J2-1964) Dynamic reconfiguration does not work for filePattern of RollingFile
[
https://issues.apache.org/jira/browse/LOG4J2-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076108#comment-16076108
]
Pierrick HYMBERT commented on LOG4J2-1964:
--
Hi [~garydgregory] , looks good thank you
> Dynamic reconfiguration does not work for filePattern of RollingFile
>
>
> Key: LOG4J2-1964
> URL: https://issues.apache.org/jira/browse/LOG4J2-1964
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.8.2
> Environment: JDK 1.7.80
>Reporter: Xiaoshuang LU
> Fix For: 2.9
>
>
> The initial log4j2.xml file was
> {code}
>
>
>
> ./logs
>
>
> name="RollingFileAppender"
> fileName="${LOG_HOME}/log.log"
> filePattern="${LOG_HOME}/log.log.%d{-MM-dd}.%i">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> And then I changed filePattern to
> {code}
> filePattern="${LOG_HOME}/log.log.%i"
> {code}
> Log file names still contain date.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LOG4J2-1964) dynamic configuration does not work for filePattern of RollingFile
[
https://issues.apache.org/jira/browse/LOG4J2-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072181#comment-16072181
]
Pierrick HYMBERT commented on LOG4J2-1964:
--
Please see submitted PR into LOG4J2-1725, waiting from the team to review and
maybe merge
> dynamic configuration does not work for filePattern of RollingFile
> --
>
> Key: LOG4J2-1964
> URL: https://issues.apache.org/jira/browse/LOG4J2-1964
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.8.2
> Environment: JDK 1.7.80
>Reporter: Xiaoshuang LU
>
> The initial log4j2.xml file was
> {code}
>
>
>
> ./logs
>
>
> name="RollingFileAppender"
> fileName="${LOG_HOME}/log.log"
> filePattern="${LOG_HOME}/log.log.%d{-MM-dd}.%i">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> And then I changed filePattern to
> {code}
> filePattern="${LOG_HOME}/log.log.%i"
> {code}
> Log file names still contain date.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LOG4J2-1950) Docker build broken with log4j-api-java9
[
https://issues.apache.org/jira/browse/LOG4J2-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16066485#comment-16066485
]
Pierrick HYMBERT commented on LOG4J2-1950:
--
The docker VM is configured {{FROM openjdk:7-jdk}}, only log4j-api-java9 module
use the toolchain jdk9.
Confirmed with the following run just after the build:
{code}
RUN java -version && /opt/apache-maven-3.5.0/bin/mvn -version
{code}
That output:
{code}
Step 5/6 : RUN java -version && /opt/apache-maven-3.5.0/bin/mvn -version
---> Running in ec253c24e421
java version "1.7.0_131"
OpenJDK Runtime Environment (IcedTea 2.6.9) (7u131-2.6.9-2~deb8u1)
OpenJDK 64-Bit Server VM (build 24.131-b00, mixed mode)
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-04-03T19:39:06Z)
Maven home: /opt/apache-maven-3.5.0
Java version: 1.7.0_131, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "4.4.52-boot2docker", arch: "amd64", family: "unix"
---> 14c3a4c8a028
{code}
> Docker build broken with log4j-api-java9
>
>
> Key: LOG4J2-1950
> URL: https://issues.apache.org/jira/browse/LOG4J2-1950
> Project: Log4j 2
> Issue Type: Bug
> Environment: Docker
>Reporter: Pierrick HYMBERT
>Priority: Trivial
> Fix For: 2.9
>
>
> Since introduction of jdk9 requirement in the build, docker image cannot be
> built.
> It fails with:
> {code}
> [INFO] --- maven-toolchains-plugin:1.1:toolchain (default) @ log4j-api-java9
> ---
> [INFO] Required toolchain: jdk [ version='9' ]
> [ERROR] No toolchain found for type jdk
> [ERROR] Cannot find matching toolchain definitions for the following
> toolchain types:
> jdk [ version='9' ]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j 2 . SUCCESS [05:27
> min]
> [INFO] Apache Log4j API Java 9 support FAILURE [ 25.103
> s]
> [INFO] Apache Log4j API ... SKIPPED
> [INFO] Apache Log4j Core .. SKIPPED
> [INFO] Apache Log4j Core Integration Tests SKIPPED
> [INFO] Apache Log4j 1.x Compatibility API . SKIPPED
> [INFO] Apache Log4j SLF4J Binding . SKIPPED
> [INFO] Apache Log4j to SLF4J Adapter .. SKIPPED
> [INFO] Apache Log4j Commons Logging Bridge SKIPPED
> [INFO] Apache Log4j Flume Bridge .. SKIPPED
> [INFO] Apache Log4j Web ... SKIPPED
> [INFO] Apache Log4j Tag Library ... SKIPPED
> [INFO] Apache Log4j JMX GUI ... SKIPPED
> [INFO] Apache Log4j Samples ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Common ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Remote ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Embedded . SKIPPED
> [INFO] Apache Log4j Samples: Configuration SKIPPED
> [INFO] Apache Log4j Samples: LoggerProperties . SKIPPED
> [INFO] Apache Log4j Scala 2.11 wrapper for Log4j API .. SKIPPED
> [INFO] Apache Log4j Samples: Scala API SKIPPED
> [INFO] Apache Log4j OSGi .. SKIPPED
> [INFO] Apache Log4j BOM ... SKIPPED
> [INFO] Apache Log4j NoSQL . SKIPPED
> [INFO] Apache Log4J Performance Tests . SKIPPED
> [INFO] Apache Log4j Streaming Interface ... SKIPPED
> [INFO] Apache Log4j JUL Adapter ... SKIPPED
> [INFO] Apache Log4j Liquibase Binding . SKIPPED
> [INFO] Apache Log4j Scala 2.10 wrapper for Log4j API .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 08:47 min
> [INFO] Finished at: 2017-06-22T15:27:35+00:00
> [INFO] Final Memory: 33M/81M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-toolchains-plugin:1.1:toolchain (default) on
> project log4j-api-java9: Cannot find matching toolchain definitions for the
> following toolchain types:
> [ERROR] jdk [ version='9' ]
> [ERROR] Please make sure you define the required toolchains in your
> ~/.m2/toolchains.xml file.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X
[jira] [Updated] (LOG4J2-1086) SizeBasedTriggeringPolicy is not working properly
[
https://issues.apache.org/jira/browse/LOG4J2-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierrick HYMBERT updated LOG4J2-1086:
-
Attachment: LOG4J2-1086.Test.patch
Hello [~ralph.go...@dslextreme.com] and team,
I am not sure this is the correct way to reproduce and what is the acceptable
size overload in log files: one log event ?
With this unit test, more thread you add, bigger files you got at the end, with
32 threads on Windows I got 5248 bytes log instead of 2048.
I have also disabled {{log4j2.enable.direct.encoders}}, because it looks it
didnt call {{RollingFileAppender.append}} method directly but the problem
persist.
I didnt find correct place to fix or move {{RollingFileAppender.checkRollover}}
method, it seems to be called to early.
> SizeBasedTriggeringPolicy is not working properly
> -
>
> Key: LOG4J2-1086
> URL: https://issues.apache.org/jira/browse/LOG4J2-1086
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.3, 2.4.1
> Environment: Windows 7 OS Websphere 8.5.5.6
>Reporter: Sharat
>Assignee: Ralph Goers
>Priority: Minor
> Labels: features
> Attachments: LOG4J2-1086.Test.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> {code}
>
>
>
> filePattern="/logs/test-%i.log">
>
> %d %-5p %class{36} (%M:%L)
> -%msg%xEx%n
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LOG4J2-1699) Configurable Log File Permissions with PosixFilePermission
[ https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16066120#comment-16066120 ] Pierrick HYMBERT commented on LOG4J2-1699: -- OK for me, thank you all! Dear [~ddimatos], please confirm it is ok for you > Configurable Log File Permissions with PosixFilePermission > -- > > Key: LOG4J2-1699 > URL: https://issues.apache.org/jira/browse/LOG4J2-1699 > Project: Log4j 2 > Issue Type: Question > Components: Appenders > Environment: Linux >Reporter: Demetrios Dimatos > Labels: features > Fix For: 2.9 > > Attachments: LOG4J2-1699-2.patch, LOG4J2-1699.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > We would like to hear the communities thoughts on being able to configure the > permissions log files are created with. We don't want to rely on UMASK > because we have managed services who's process should generate logs with a > 644 yet deployed applications by users should default to a 640 because the > logs may contain sensitive information. > We will make the modification and set this in the properties file. Now we are > looking to see what the community position would be on accepting such a > patch, we don't want to be patching our own distribution indefinitely. > I searched all the JIRAs and was not able to find any matching requirements > recently. All I could find was something dated in 2006: > https://bz.apache.org/bugzilla/show_bug.cgi?id=40407 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LOG4J2-1950) Docker build broken with log4j-api-java9
[
https://issues.apache.org/jira/browse/LOG4J2-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063617#comment-16063617
]
Pierrick HYMBERT commented on LOG4J2-1950:
--
Yes Windows docker machine just works fine me.
> Docker build broken with log4j-api-java9
>
>
> Key: LOG4J2-1950
> URL: https://issues.apache.org/jira/browse/LOG4J2-1950
> Project: Log4j 2
> Issue Type: Bug
> Environment: Docker
>Reporter: Pierrick HYMBERT
>Priority: Trivial
> Fix For: 2.9
>
>
> Since introduction of jdk9 requirement in the build, docker image cannot be
> built.
> It fails with:
> {code}
> [INFO] --- maven-toolchains-plugin:1.1:toolchain (default) @ log4j-api-java9
> ---
> [INFO] Required toolchain: jdk [ version='9' ]
> [ERROR] No toolchain found for type jdk
> [ERROR] Cannot find matching toolchain definitions for the following
> toolchain types:
> jdk [ version='9' ]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j 2 . SUCCESS [05:27
> min]
> [INFO] Apache Log4j API Java 9 support FAILURE [ 25.103
> s]
> [INFO] Apache Log4j API ... SKIPPED
> [INFO] Apache Log4j Core .. SKIPPED
> [INFO] Apache Log4j Core Integration Tests SKIPPED
> [INFO] Apache Log4j 1.x Compatibility API . SKIPPED
> [INFO] Apache Log4j SLF4J Binding . SKIPPED
> [INFO] Apache Log4j to SLF4J Adapter .. SKIPPED
> [INFO] Apache Log4j Commons Logging Bridge SKIPPED
> [INFO] Apache Log4j Flume Bridge .. SKIPPED
> [INFO] Apache Log4j Web ... SKIPPED
> [INFO] Apache Log4j Tag Library ... SKIPPED
> [INFO] Apache Log4j JMX GUI ... SKIPPED
> [INFO] Apache Log4j Samples ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Common ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Remote ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Embedded . SKIPPED
> [INFO] Apache Log4j Samples: Configuration SKIPPED
> [INFO] Apache Log4j Samples: LoggerProperties . SKIPPED
> [INFO] Apache Log4j Scala 2.11 wrapper for Log4j API .. SKIPPED
> [INFO] Apache Log4j Samples: Scala API SKIPPED
> [INFO] Apache Log4j OSGi .. SKIPPED
> [INFO] Apache Log4j BOM ... SKIPPED
> [INFO] Apache Log4j NoSQL . SKIPPED
> [INFO] Apache Log4J Performance Tests . SKIPPED
> [INFO] Apache Log4j Streaming Interface ... SKIPPED
> [INFO] Apache Log4j JUL Adapter ... SKIPPED
> [INFO] Apache Log4j Liquibase Binding . SKIPPED
> [INFO] Apache Log4j Scala 2.10 wrapper for Log4j API .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 08:47 min
> [INFO] Finished at: 2017-06-22T15:27:35+00:00
> [INFO] Final Memory: 33M/81M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-toolchains-plugin:1.1:toolchain (default) on
> project log4j-api-java9: Cannot find matching toolchain definitions for the
> following toolchain types:
> [ERROR] jdk [ version='9' ]
> [ERROR] Please make sure you define the required toolchains in your
> ~/.m2/toolchains.xml file.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :log4j-api-java9
> The command '/bin/sh -c set -ex && cd /src &&
> /opt/apache-maven-3.3.9/bin/mvn verify' returned a non-zero code: 1
> {code}
> I have tried to make it working back, but alpine doesnt support openjdk9 till
> now, so I suggest to revert to the debian image (FROM openjdk:7-jdk).
> First run is slow, as usual with packages, but then it works smoothly.
> Please check and confirm.
> Have fun with docker :-)
--
This message was sent by
[jira] [Commented] (LOG4J2-1950) Docker build broken with log4j-api-java9
[
https://issues.apache.org/jira/browse/LOG4J2-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063536#comment-16063536
]
Pierrick HYMBERT commented on LOG4J2-1950:
--
BTW, Log4j 1.x Compatibility API failed in docker env
{code}
[INFO] --- maven-surefire-plugin:2.20:test (default-test) @ log4j-1.2-api ---
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running org.apache.log4j.PriorityTest
[INFO] Running org.apache.log4j.LoggingTest
[INFO] Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.209 s
- in org.apache.log4j.PriorityTest
[INFO] Running org.apache.log4j.config.Log4j1ConfigurationConverterSparkTest
[INFO] Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.642 s
- in org.apache.log4j.config.Log4j1ConfigurationConverterSparkTest
[INFO] Running org.apache.log4j.config.Log4j1ConfigurationConverterHadoopTest
Missing rootCategory or rootLogger in InputStreamWrapper
[description=/src/log4j-1.2-api/src/test/resources/config-1.2/hadoop/hadoop-common-project/hadoop-auth-examples/src/main/resources/lo
Missing rootCategory or rootLogger in InputStreamWrapper
[description=/src/log4j-1.2-api/src/test/resources/config-1.2/hadoop/hadoop-tools/hadoop-sls/src/main/sample-conf/log4j.properties,
i
[INFO] Tests run: 30, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.305 s
- in org.apache.log4j.config.Log4j1ConfigurationConverterHadoopTest
[INFO] Running org.apache.log4j.config.Log4j1ConfigurationFactoryTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.675 s
- in org.apache.log4j.LoggingTest
[INFO] Running org.apache.log4j.LevelTest
[INFO] Tests run: 23, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.106 s
- in org.apache.log4j.LevelTest
[INFO] Running org.apache.log4j.LogWithMDCTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.091 s
- in org.apache.log4j.LogWithMDCTest
[INFO] Running org.apache.log4j.MDCTestCase
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 s
- in org.apache.log4j.MDCTestCase
[INFO] Running org.apache.log4j.CategoryTest
[INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.087 s
- in org.apache.log4j.CategoryTest
[INFO] Running org.apache.log4j.LogWithRouteTest
http://www.w3.org/TR/html4/loose.dtd;>
Headline
Log session start time Mon Jun 26 18:00:22 UTC 2017
Time
Thread
Level
Logger
File:Line
Message
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.093 s
- in org.apache.log4j.LogWithRouteTest
[INFO] Running org.apache.log4j.pattern.Log4j1NdcPatternConverterTest
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.023 s
- in org.apache.log4j.pattern.Log4j1NdcPatternConverterTest
expected: /tmp/hadoop.log Actual: /tmp/hadoop.log
[INFO] Running org.apache.log4j.pattern.Log4j1MdcPatternConverterTest
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 s
- in org.apache.log4j.pattern.Log4j1MdcPatternConverterTest
[INFO] Running org.apache.log4j.VelocityTest
ERROR StatusLogger No log4j2 configuration file found. Using default
configuration: logging only errors to the console. Set system property
'org.apache.logging.log4j.simplelog.StatusLogger.l
[INFO] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.078 s
- in org.apache.log4j.config.Log4j1ConfigurationFactoryTest
[INFO] Running org.apache.log4j.LoggerTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.229 s
- in org.apache.log4j.VelocityTest
[INFO] Running org.apache.log4j.CallerInformationTest
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.06 s -
in org.apache.log4j.CallerInformationTest
[INFO] Running org.apache.log4j.NDCTest
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 s
- in org.apache.log4j.NDCTest
[INFO] Running org.apache.log4j.layout.Log4j1XmlLayoutTest
[ERROR] at
org.apache.log4j.layout.Log4j1XmlLayoutTest.testWithoutThrown(Log4j1XmlLayoutTest.java:49).apache.log4j.layout.Log4j1XmlLayoutTest
[ERROR] testWithoutThrown(org.apache.log4j.layout.Log4j1XmlLayoutTest) Time
elapsed: 0.005 s <<< FAILURE!
[INFO] Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.33 s
- in org.apache.log4j.LoggerTest
[INFO] d:<...>
[INFO] Results:>
[INFO]
[ERROR] Failures: og4j:message>
[ERROR] Log4j1XmlLayoutTest.testWithoutThrown:49
expected:<...>
<[]/log4j:event>="Name" value="John Smith"/>
> but was:<...>
<[log4j:properties>
<]/log4j:event>
>
[INFO]
[ERROR] Tests run: 145, Failures: 1, Errors: 0, Skipped: 0
[INFO]
[INFO]
[jira] [Closed] (LOG4J2-1950) Docker build broken with log4j-api-java9
[
https://issues.apache.org/jira/browse/LOG4J2-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierrick HYMBERT closed LOG4J2-1950.
OK, building. Thanks
> Docker build broken with log4j-api-java9
>
>
> Key: LOG4J2-1950
> URL: https://issues.apache.org/jira/browse/LOG4J2-1950
> Project: Log4j 2
> Issue Type: Bug
> Environment: Docker
>Reporter: Pierrick HYMBERT
>Priority: Trivial
> Fix For: 2.9
>
>
> Since introduction of jdk9 requirement in the build, docker image cannot be
> built.
> It fails with:
> {code}
> [INFO] --- maven-toolchains-plugin:1.1:toolchain (default) @ log4j-api-java9
> ---
> [INFO] Required toolchain: jdk [ version='9' ]
> [ERROR] No toolchain found for type jdk
> [ERROR] Cannot find matching toolchain definitions for the following
> toolchain types:
> jdk [ version='9' ]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j 2 . SUCCESS [05:27
> min]
> [INFO] Apache Log4j API Java 9 support FAILURE [ 25.103
> s]
> [INFO] Apache Log4j API ... SKIPPED
> [INFO] Apache Log4j Core .. SKIPPED
> [INFO] Apache Log4j Core Integration Tests SKIPPED
> [INFO] Apache Log4j 1.x Compatibility API . SKIPPED
> [INFO] Apache Log4j SLF4J Binding . SKIPPED
> [INFO] Apache Log4j to SLF4J Adapter .. SKIPPED
> [INFO] Apache Log4j Commons Logging Bridge SKIPPED
> [INFO] Apache Log4j Flume Bridge .. SKIPPED
> [INFO] Apache Log4j Web ... SKIPPED
> [INFO] Apache Log4j Tag Library ... SKIPPED
> [INFO] Apache Log4j JMX GUI ... SKIPPED
> [INFO] Apache Log4j Samples ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Common ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Remote ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Embedded . SKIPPED
> [INFO] Apache Log4j Samples: Configuration SKIPPED
> [INFO] Apache Log4j Samples: LoggerProperties . SKIPPED
> [INFO] Apache Log4j Scala 2.11 wrapper for Log4j API .. SKIPPED
> [INFO] Apache Log4j Samples: Scala API SKIPPED
> [INFO] Apache Log4j OSGi .. SKIPPED
> [INFO] Apache Log4j BOM ... SKIPPED
> [INFO] Apache Log4j NoSQL . SKIPPED
> [INFO] Apache Log4J Performance Tests . SKIPPED
> [INFO] Apache Log4j Streaming Interface ... SKIPPED
> [INFO] Apache Log4j JUL Adapter ... SKIPPED
> [INFO] Apache Log4j Liquibase Binding . SKIPPED
> [INFO] Apache Log4j Scala 2.10 wrapper for Log4j API .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 08:47 min
> [INFO] Finished at: 2017-06-22T15:27:35+00:00
> [INFO] Final Memory: 33M/81M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-toolchains-plugin:1.1:toolchain (default) on
> project log4j-api-java9: Cannot find matching toolchain definitions for the
> following toolchain types:
> [ERROR] jdk [ version='9' ]
> [ERROR] Please make sure you define the required toolchains in your
> ~/.m2/toolchains.xml file.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :log4j-api-java9
> The command '/bin/sh -c set -ex && cd /src &&
> /opt/apache-maven-3.3.9/bin/mvn verify' returned a non-zero code: 1
> {code}
> I have tried to make it working back, but alpine doesnt support openjdk9 till
> now, so I suggest to revert to the debian image (FROM openjdk:7-jdk).
> First run is slow, as usual with packages, but then it works smoothly.
> Please check and confirm.
> Have fun with docker :-)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LOG4J2-1699) Configurable Log File Permissions with PosixFilePermission
[ https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061825#comment-16061825 ] Pierrick HYMBERT commented on LOG4J2-1699: -- I think the goal is reached with this first version, then we should wait users feedback if it matches requirements. Also before to freeze this new API, I would like to have feedback from the log4j team about following point: # Is XML Configuration tag should be shortenen, filePermissions=>perm, fileOwner=>usr, fileGroup=>grp, PosixViewAttribute=>PosixAttr ? # It is not clear what to do if posix attribute view are defined and the underlying files system does not support it ? # Should we catch UnsupportedOperationException and OperationNotPermitted exception ? # In org.apache.logging.log4j.core.appender.rolling.DirectWriteRolloverStrategy.rollover(RollingFileManager), I apply again file attribute, I think it is wrong because file is the same as the current file name, please confirm # Should we imagine now an entry point for other FileAttributeView types: AclFileAttributeView, DosFileAttributeView ? > Configurable Log File Permissions with PosixFilePermission > -- > > Key: LOG4J2-1699 > URL: https://issues.apache.org/jira/browse/LOG4J2-1699 > Project: Log4j 2 > Issue Type: Question > Components: Appenders > Environment: Linux >Reporter: Demetrios Dimatos >Priority: Critical > Labels: features > Fix For: 2.9 > > Attachments: LOG4J2-1699-2.patch, LOG4J2-1699.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > We would like to hear the communities thoughts on being able to configure the > permissions log files are created with. We don't want to rely on UMASK > because we have managed services who's process should generate logs with a > 644 yet deployed applications by users should default to a 640 because the > logs may contain sensitive information. > We will make the modification and set this in the properties file. Now we are > looking to see what the community position would be on accepting such a > patch, we don't want to be patching our own distribution indefinitely. > I searched all the JIRAs and was not able to find any matching requirements > recently. All I could find was something dated in 2006: > https://bz.apache.org/bugzilla/show_bug.cgi?id=40407 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LOG4J2-1699) Configurable Log File Permissions with PosixFilePermission
[
https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061589#comment-16061589
]
Pierrick HYMBERT commented on LOG4J2-1699:
--
Hello [~garydgregory],
I am not sure, I did it no ? Both {{FileAppender }}, {{RollingFileAppender }},
{{RollingRandomAccessFileAppender}} and even
{{CustomPosixViewAttributeAction}}, can you please confirm what I should add ?
> Configurable Log File Permissions with PosixFilePermission
> --
>
> Key: LOG4J2-1699
> URL: https://issues.apache.org/jira/browse/LOG4J2-1699
> Project: Log4j 2
> Issue Type: Question
> Components: Appenders
> Environment: Linux
>Reporter: Demetrios Dimatos
>Priority: Critical
> Labels: features
> Fix For: 2.9
>
> Attachments: LOG4J2-1699-2.patch, LOG4J2-1699.patch
>
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> We would like to hear the communities thoughts on being able to configure the
> permissions log files are created with. We don't want to rely on UMASK
> because we have managed services who's process should generate logs with a
> 644 yet deployed applications by users should default to a 640 because the
> logs may contain sensitive information.
> We will make the modification and set this in the properties file. Now we are
> looking to see what the community position would be on accepting such a
> patch, we don't want to be patching our own distribution indefinitely.
> I searched all the JIRAs and was not able to find any matching requirements
> recently. All I could find was something dated in 2006:
> https://bz.apache.org/bugzilla/show_bug.cgi?id=40407
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (LOG4J2-1699) Configurable Log File Permissions with PosixFilePermission
[
https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061589#comment-16061589
]
Pierrick HYMBERT edited comment on LOG4J2-1699 at 6/23/17 10:24 PM:
Hello [~garydgregory],
I am not sure, I did it no ? Both {{FileAppender}}, {{RollingFileAppender}},
{{RollingRandomAccessFileAppender}} and even
{{CustomPosixViewAttributeAction}}, can you please confirm what I should add ?
was (Author: phymbert):
Hello [~garydgregory],
I am not sure, I did it no ? Both {{FileAppender }}, {{RollingFileAppender }},
{{RollingRandomAccessFileAppender}} and even
{{CustomPosixViewAttributeAction}}, can you please confirm what I should add ?
> Configurable Log File Permissions with PosixFilePermission
> --
>
> Key: LOG4J2-1699
> URL: https://issues.apache.org/jira/browse/LOG4J2-1699
> Project: Log4j 2
> Issue Type: Question
> Components: Appenders
> Environment: Linux
>Reporter: Demetrios Dimatos
>Priority: Critical
> Labels: features
> Fix For: 2.9
>
> Attachments: LOG4J2-1699-2.patch, LOG4J2-1699.patch
>
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> We would like to hear the communities thoughts on being able to configure the
> permissions log files are created with. We don't want to rely on UMASK
> because we have managed services who's process should generate logs with a
> 644 yet deployed applications by users should default to a 640 because the
> logs may contain sensitive information.
> We will make the modification and set this in the properties file. Now we are
> looking to see what the community position would be on accepting such a
> patch, we don't want to be patching our own distribution indefinitely.
> I searched all the JIRAs and was not able to find any matching requirements
> recently. All I could find was something dated in 2006:
> https://bz.apache.org/bugzilla/show_bug.cgi?id=40407
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LOG4J2-1944) Should suppress message "ERROR No log4j2 configuration file found..." when programmatic API is used to config log4j.
[
https://issues.apache.org/jira/browse/LOG4J2-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061557#comment-16061557
]
Pierrick HYMBERT commented on LOG4J2-1944:
--
Hello [~wdeng], thank you for this snippet, I have no chance to debate status
logger error level.
Although I tried to answer your concern about programmatic API and this error
message that doesnt appears in this case.
But maybe I was wrong, if you required to log error message to console:
{code}
import java.time.Instant;
public class App {
public static void main(String[] args) {
System.err.println(String.format("%s [%s] %s %s - %s", Instant.now(),
Thread.currentThread().getName(), "ERROR", App.class.getName(),
"Hello"));
}
}
{code}
If you do need log4j2, please read [The ConfigurationBuilder
API|https://logging.apache.org/log4j/2.x/manual/customconfig.html], for example:
{code}
import org.apache.logging.log4j.Level;
import org.apache.logging.log4j.Logger;
import org.apache.logging.log4j.core.LoggerContext;
import org.apache.logging.log4j.core.appender.ConsoleAppender;
import org.apache.logging.log4j.core.config.Configurator;
import
org.apache.logging.log4j.core.config.builder.api.AppenderComponentBuilder;
import org.apache.logging.log4j.core.config.builder.api.ConfigurationBuilder;
import
org.apache.logging.log4j.core.config.builder.api.ConfigurationBuilderFactory;
import org.apache.logging.log4j.core.config.builder.impl.BuiltConfiguration;
public class App {
public static void main(String[] args) {
final ConfigurationBuilder builder =
ConfigurationBuilderFactory
.newConfigurationBuilder();
builder.setStatusLevel(Level.ERROR);
builder.setConfigurationName("App");
final AppenderComponentBuilder appenderBuilder =
builder.newAppender("Stdout", "CONSOLE")
.addAttribute("target", ConsoleAppender.Target.SYSTEM_OUT);
appenderBuilder.add(
builder.newLayout("PatternLayout").addAttribute("pattern", "%d
%p %C [%t] %m%n"));
builder.add(appenderBuilder);
builder.add(builder.newRootLogger(Level.ERROR).add(builder.newAppenderRef("Stdout")));
LoggerContext ctx = Configurator.initialize(builder.build());
Logger log = ctx.getLogger(App.class.getName());
log.error("Hello");
}
}
{code}
> Should suppress message "ERROR No log4j2 configuration file found..." when
> programmatic API is used to config log4j.
>
>
> Key: LOG4J2-1944
> URL: https://issues.apache.org/jira/browse/LOG4J2-1944
> Project: Log4j 2
> Issue Type: Bug
> Components: Configurators
>Affects Versions: 2.6.2
>Reporter: Weian Deng
>Priority: Minor
> Attachments: LOG4J2_1944.zip
>
>
> Log4j can be configured through log4j's configuration API. There are cases
> that an organization want to control the log4j configuration through the
> configuration API and discourage the use of config file. The error message
> {code}
> ERROR No log4j2 configuration file found. Using default configuration:
> logging only errors to the console.
> {code}
> is misleading.
> Can this be downgraded to WARN message, or provide a way to suppress it?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LOG4J2-1766) Distinguish between partial and completed .gz archive file
[
https://issues.apache.org/jira/browse/LOG4J2-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierrick HYMBERT updated LOG4J2-1766:
-
Attachment: (was: LOG4J2-1766.patch)
> Distinguish between partial and completed .gz archive file
> --
>
> Key: LOG4J2-1766
> URL: https://issues.apache.org/jira/browse/LOG4J2-1766
> Project: Log4j 2
> Issue Type: New Feature
>Affects Versions: 2.5
>Reporter: Sameer Pradhan
> Labels: features
>
> I have the following log configuration.
> fileName="/usr/test/req.log"
> filePattern="/usr/test/req.log.%d{-MM-dd-HH}.%i.gz"
> immediateFlush="true" append="true">
>
> %d{-MM-dd HH:mm:ss.SSS Z}%m%n
>
>
>
>
>
>
> When the log is rolled over (based on time or size), it is gzipped. Gzipping
> the file takes some time (seconds to minutes depending on load). The problem
> is that the file is gzipped in place, and while it is being gzipped, the
> partially gzipped file is stored in the same folder with the same name as the
> final gzip file. e.g.: /usr/test/req.log.2017-01-03-02.1.gz
> This causes problems for the file's consumer, which attempts to process the
> partial file. I want to be able to distinguish between a partial gzipped file
> and a completed gzipped file. For example, I would like to setup a
> configuration that while the file is being gzipped, it is written with a
> different name e.g.: /usr/test/req.log.2017-01-03-02.1.gz.temp and once it is
> completely gzipped the name is changed to the final name
> /usr/test/req.log.2017-01-03-02.1.gz
> One way to achieve this is to add a new parameter like
> "temporaryCompressedFilePattern" as follows:
> fileName="/usr/test/req.log"
> filePattern="/usr/test/req.log.%d{-MM-dd-HH}.%i.gz"
>
> temporaryCompressedFilePattern="/usr/test/req.log.%d{-MM-dd-HH}.%i.gz.temp"
> Another option is to make such behavior the default behavior without adding a
> new parameter.
>
> This was first discussed at
> http://stackoverflow.com/questions/41457492/partial-gz-file-written-by-log4j2
> Creating this feature request as suggested by @rpopma
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LOG4J2-1699) Configurable Log File Permissions with PosixFilePermission
[ https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060750#comment-16060750 ] Pierrick HYMBERT commented on LOG4J2-1699: -- Hello [~garydgregory], I have tried to update documentation in this [PR #85|https://github.com/apache/logging-log4j2/pull/85], but this is my first attempt please correct any mistake I have done. Thank you! > Configurable Log File Permissions with PosixFilePermission > -- > > Key: LOG4J2-1699 > URL: https://issues.apache.org/jira/browse/LOG4J2-1699 > Project: Log4j 2 > Issue Type: Question > Components: Appenders > Environment: Linux >Reporter: Demetrios Dimatos >Priority: Critical > Labels: features > Fix For: 2.9 > > Attachments: LOG4J2-1699-2.patch, LOG4J2-1699.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > We would like to hear the communities thoughts on being able to configure the > permissions log files are created with. We don't want to rely on UMASK > because we have managed services who's process should generate logs with a > 644 yet deployed applications by users should default to a 640 because the > logs may contain sensitive information. > We will make the modification and set this in the properties file. Now we are > looking to see what the community position would be on accepting such a > patch, we don't want to be patching our own distribution indefinitely. > I searched all the JIRAs and was not able to find any matching requirements > recently. All I could find was something dated in 2006: > https://bz.apache.org/bugzilla/show_bug.cgi?id=40407 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (LOG4J2-1950) Docker build broken with log4j-api-java9
Pierrick HYMBERT created LOG4J2-1950:
Summary: Docker build broken with log4j-api-java9
Key: LOG4J2-1950
URL: https://issues.apache.org/jira/browse/LOG4J2-1950
Project: Log4j 2
Issue Type: Bug
Environment: Docker
Reporter: Pierrick HYMBERT
Priority: Trivial
Since introduction of jdk9 requirement in the build, docker image cannot be
built.
It fails with:
{code}
[INFO] --- maven-toolchains-plugin:1.1:toolchain (default) @ log4j-api-java9 ---
[INFO] Required toolchain: jdk [ version='9' ]
[ERROR] No toolchain found for type jdk
[ERROR] Cannot find matching toolchain definitions for the following toolchain
types:
jdk [ version='9' ]
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Log4j 2 . SUCCESS [05:27 min]
[INFO] Apache Log4j API Java 9 support FAILURE [ 25.103 s]
[INFO] Apache Log4j API ... SKIPPED
[INFO] Apache Log4j Core .. SKIPPED
[INFO] Apache Log4j Core Integration Tests SKIPPED
[INFO] Apache Log4j 1.x Compatibility API . SKIPPED
[INFO] Apache Log4j SLF4J Binding . SKIPPED
[INFO] Apache Log4j to SLF4J Adapter .. SKIPPED
[INFO] Apache Log4j Commons Logging Bridge SKIPPED
[INFO] Apache Log4j Flume Bridge .. SKIPPED
[INFO] Apache Log4j Web ... SKIPPED
[INFO] Apache Log4j Tag Library ... SKIPPED
[INFO] Apache Log4j JMX GUI ... SKIPPED
[INFO] Apache Log4j Samples ... SKIPPED
[INFO] Apache Log4j Samples: Flume - Common ... SKIPPED
[INFO] Apache Log4j Samples: Flume - Remote ... SKIPPED
[INFO] Apache Log4j Samples: Flume - Embedded . SKIPPED
[INFO] Apache Log4j Samples: Configuration SKIPPED
[INFO] Apache Log4j Samples: LoggerProperties . SKIPPED
[INFO] Apache Log4j Scala 2.11 wrapper for Log4j API .. SKIPPED
[INFO] Apache Log4j Samples: Scala API SKIPPED
[INFO] Apache Log4j OSGi .. SKIPPED
[INFO] Apache Log4j BOM ... SKIPPED
[INFO] Apache Log4j NoSQL . SKIPPED
[INFO] Apache Log4J Performance Tests . SKIPPED
[INFO] Apache Log4j Streaming Interface ... SKIPPED
[INFO] Apache Log4j JUL Adapter ... SKIPPED
[INFO] Apache Log4j Liquibase Binding . SKIPPED
[INFO] Apache Log4j Scala 2.10 wrapper for Log4j API .. SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 08:47 min
[INFO] Finished at: 2017-06-22T15:27:35+00:00
[INFO] Final Memory: 33M/81M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-toolchains-plugin:1.1:toolchain (default) on
project log4j-api-java9: Cannot find matching toolchain definitions for the
following toolchain types:
[ERROR] jdk [ version='9' ]
[ERROR] Please make sure you define the required toolchains in your
~/.m2/toolchains.xml file.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :log4j-api-java9
The command '/bin/sh -c set -ex && cd /src &&
/opt/apache-maven-3.3.9/bin/mvn verify' returned a non-zero code: 1
{code}
I have tried to make it working back, but alpine doesnt support openjdk9 till
now, so I suggest to revert to the debian image (FROM openjdk:7-jdk).
First run is slow, as usual with packages, but then it works smoothly.
Please check and confirm.
Have fun with docker :-)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LOG4J2-1699) Configurable Log File Permissions with PosixFilePermission
[ https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16059272#comment-16059272 ] Pierrick HYMBERT commented on LOG4J2-1699: -- Hello, Well :-) I did it this way - Builder - in this new patch, I have tried PR approach on github (see above), hope it is ok for you. Let me know if we are good. > Configurable Log File Permissions with PosixFilePermission > -- > > Key: LOG4J2-1699 > URL: https://issues.apache.org/jira/browse/LOG4J2-1699 > Project: Log4j 2 > Issue Type: Question > Components: Appenders > Environment: Linux >Reporter: Demetrios Dimatos >Priority: Critical > Labels: features > Fix For: 2.9 > > Attachments: LOG4J2-1699-2.patch, LOG4J2-1699.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > We would like to hear the communities thoughts on being able to configure the > permissions log files are created with. We don't want to rely on UMASK > because we have managed services who's process should generate logs with a > 644 yet deployed applications by users should default to a 640 because the > logs may contain sensitive information. > We will make the modification and set this in the properties file. Now we are > looking to see what the community position would be on accepting such a > patch, we don't want to be patching our own distribution indefinitely. > I searched all the JIRAs and was not able to find any matching requirements > recently. All I could find was something dated in 2006: > https://bz.apache.org/bugzilla/show_bug.cgi?id=40407 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LOG4J2-1699) Configurable Log File Permissions with PosixFilePermission
[ https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16057609#comment-16057609 ] Pierrick HYMBERT commented on LOG4J2-1699: -- Thank you for your encouragement [~ralph.go...@dslextreme.com], let's agree this is just a minor enhancement within a big project that make our every day life easier :-) > Configurable Log File Permissions with PosixFilePermission > -- > > Key: LOG4J2-1699 > URL: https://issues.apache.org/jira/browse/LOG4J2-1699 > Project: Log4j 2 > Issue Type: Question > Components: Appenders > Environment: Linux >Reporter: Demetrios Dimatos >Priority: Critical > Labels: features > Fix For: 2.9 > > Attachments: LOG4J2-1699-2.patch, LOG4J2-1699.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > We would like to hear the communities thoughts on being able to configure the > permissions log files are created with. We don't want to rely on UMASK > because we have managed services who's process should generate logs with a > 644 yet deployed applications by users should default to a 640 because the > logs may contain sensitive information. > We will make the modification and set this in the properties file. Now we are > looking to see what the community position would be on accepting such a > patch, we don't want to be patching our own distribution indefinitely. > I searched all the JIRAs and was not able to find any matching requirements > recently. All I could find was something dated in 2006: > https://bz.apache.org/bugzilla/show_bug.cgi?id=40407 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LOG4J2-1699) Configurable Log File Permissions with PosixFilePermission
[ https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierrick HYMBERT updated LOG4J2-1699: - Attachment: LOG4J2-1699.patch > Configurable Log File Permissions with PosixFilePermission > -- > > Key: LOG4J2-1699 > URL: https://issues.apache.org/jira/browse/LOG4J2-1699 > Project: Log4j 2 > Issue Type: Question > Components: Appenders > Environment: Linux >Reporter: Demetrios Dimatos >Priority: Critical > Labels: features > Attachments: LOG4J2-1699.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > We would like to hear the communities thoughts on being able to configure the > permissions log files are created with. We don't want to rely on UMASK > because we have managed services who's process should generate logs with a > 644 yet deployed applications by users should default to a 640 because the > logs may contain sensitive information. > We will make the modification and set this in the properties file. Now we are > looking to see what the community position would be on accepting such a > patch, we don't want to be patching our own distribution indefinitely. > I searched all the JIRAs and was not able to find any matching requirements > recently. All I could find was something dated in 2006: > https://bz.apache.org/bugzilla/show_bug.cgi?id=40407 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LOG4J2-1699) Configurable Log File Permissions with PosixFilePermission
[ https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierrick HYMBERT updated LOG4J2-1699: - Attachment: (was: LOG4J2-1699.patch) > Configurable Log File Permissions with PosixFilePermission > -- > > Key: LOG4J2-1699 > URL: https://issues.apache.org/jira/browse/LOG4J2-1699 > Project: Log4j 2 > Issue Type: Question > Components: Appenders > Environment: Linux >Reporter: Demetrios Dimatos >Priority: Critical > Labels: features > Attachments: LOG4J2-1699.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > We would like to hear the communities thoughts on being able to configure the > permissions log files are created with. We don't want to rely on UMASK > because we have managed services who's process should generate logs with a > 644 yet deployed applications by users should default to a 640 because the > logs may contain sensitive information. > We will make the modification and set this in the properties file. Now we are > looking to see what the community position would be on accepting such a > patch, we don't want to be patching our own distribution indefinitely. > I searched all the JIRAs and was not able to find any matching requirements > recently. All I could find was something dated in 2006: > https://bz.apache.org/bugzilla/show_bug.cgi?id=40407 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LOG4J2-1699) Configurable Log File Permissions with PosixFilePermission
[ https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierrick HYMBERT updated LOG4J2-1699: - Attachment: LOG4J2-1699.patch Hello Team, I have tried to implement posix user, group and permissions in the attached patch within the FileManager hierarchy. Please review and correct me if something wrong. Done a simple test for permissions on posix systems only although I dont know how to unit test user and group. Also I am not sure if FileOutputStream create the file on all jvm implementation, tested on . NB: this feature was also required in a [stackoverflow |https://stackoverflow.com/questions/7893511/permissions-on-log-files-created-by-log4j-rollingfileappender] question > Configurable Log File Permissions with PosixFilePermission > -- > > Key: LOG4J2-1699 > URL: https://issues.apache.org/jira/browse/LOG4J2-1699 > Project: Log4j 2 > Issue Type: Question > Components: Appenders > Environment: Linux >Reporter: Demetrios Dimatos >Priority: Critical > Labels: features > Attachments: LOG4J2-1699.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > We would like to hear the communities thoughts on being able to configure the > permissions log files are created with. We don't want to rely on UMASK > because we have managed services who's process should generate logs with a > 644 yet deployed applications by users should default to a 640 because the > logs may contain sensitive information. > We will make the modification and set this in the properties file. Now we are > looking to see what the community position would be on accepting such a > patch, we don't want to be patching our own distribution indefinitely. > I searched all the JIRAs and was not able to find any matching requirements > recently. All I could find was something dated in 2006: > https://bz.apache.org/bugzilla/show_bug.cgi?id=40407 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LOG4J2-1910) On changing of log4j2.xml, the CustomConfig and Factory are not called and custom loggers are lost
[
https://issues.apache.org/jira/browse/LOG4J2-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055395#comment-16055395
]
Pierrick HYMBERT commented on LOG4J2-1910:
--
You may register a
{{org.apache.logging.log4j.core.config.ConfigurationListener}} in your custom
configuration by calling
{{org.apache.logging.log4j.core.config.AbstractConfiguration.addListener(ConfigurationListener)}}
within doConfigure method, then you will be notified when the file changed and
apply again your programatic configuration.
> On changing of log4j2.xml, the CustomConfig and Factory are not called and
> custom loggers are lost
> ---
>
> Key: LOG4J2-1910
> URL: https://issues.apache.org/jira/browse/LOG4J2-1910
> Project: Log4j 2
> Issue Type: Bug
> Components: Configurators
>Affects Versions: 2.8.2
> Environment: window 2012 server and Java 8
>Reporter: michael peng
>
> We created Custom Configuration(Log4JConfiguration) and Factory by following
> the guide- https://logging.apache.org/log4j/2.x/manual/customconfig.html :
> Initialize Log4j by Combining Configuration File with Programmatic
> Configuration,
> On application initialization, everything works ok and log events are logged
> to custom logger file, but on changing of log4j2.xml file which is set to
> monitorInterval="10", Custom Log4JConfiguration is not called
> 2017-05-17 11:21:33,459 localhost-startStop-1 DEBUG Configuration
> Log4JConfiguration[location=C:\Program
> Files\test\webapp\WEB-INF\classes\log4j2.xml] initialized
> 2017-05-17 11:21:33,474 localhost-startStop-1 DEBUG Starting configuration
> Log4JConfiguration[location=C:\Program
> Files\test\webapp\WEB-INF\classes\log4j2.xml]
> 2017-05-17 11:21:33,474 localhost-startStop-1 DEBUG Log4j2
> ConfigurationScheduler starting 1 threads
> 2017-05-17 11:21:33,474 localhost-startStop-1 DEBUG Started configuration
> Log4JConfiguration[location=C:\Program
> Files\test\webapp\WEB-INF\classes\log4j2.xml] OK.
> 2017-05-17 11:21:33,474 localhost-startStop-1 TRACE Stopping
> Log4JConfiguration[location=C:\Program
> Files\test\webapp\WEB-INF\classes\log4j2.xml]...
> 2017-05-17 11:21:33,474 localhost-startStop-1 TRACE Log4JConfiguration
> notified 6 ReliabilityStrategies that config will be stopped.
> 2017-05-17 11:21:33,490 localhost-startStop-1 TRACE Log4JConfiguration
> stopping 5 LoggerConfigs.
> 2017-05-17 11:21:33,490 localhost-startStop-1 TRACE Log4JConfiguration
> stopping root LoggerConfig.
> 2017-05-17 11:21:33,490 localhost-startStop-1 TRACE Log4JConfiguration
> notifying ReliabilityStrategies that appenders will be stopped.
> 2017-05-17 11:21:33,490 localhost-startStop-1 TRACE Log4JConfiguration
> stopping remaining Appenders.
> 2017-05-17 11:21:33,490 localhost-startStop-1 DEBUG Shutting down
> OutputStreamManager SYSTEM_OUT.false.false
> 2017-05-17 11:21:33,505 localhost-startStop-1 DEBUG Shut down
> OutputStreamManager SYSTEM_OUT.false.false, all resources released: true
> 2017-05-17 11:21:33,505 localhost-startStop-1 DEBUG Appender STDOUT stopped
> with status true
> 2017-05-17 11:21:33,521 localhost-startStop-1 TRACE Log4JConfiguration
> stopped 1 remaining Appenders.
> 2017-05-17 11:21:33,521 localhost-startStop-1 TRACE Log4JConfiguration
> cleaning Appenders from 6 LoggerConfigs.
> 2017-05-17 11:21:33,537 localhost-startStop-1 DEBUG Log4j2
> ConfigurationScheduler shutting down threads in
> java.util.concurrent.ScheduledThreadPoolExecutor@21910699[Running, pool size
> = 1, active threads = 0, queued tasks = 1, completed tasks = 2]
> 2017-05-17 11:21:33,724 localhost-startStop-1 DEBUG Stopped
> Log4JConfiguration[location=C:\Program
> Files\test\webapp\WEB-INF\classes\log4j2.xml] OK
> 2017-05-17 11:21:33,740 localhost-startStop-1 TRACE Reregistering MBeans
> after reconfigure.
> Selector=org.apache.logging.log4j.core.selector.ClassLoaderContextSelector@26c1ae2f
> 2017-05-17 11:21:33,755 localhost-startStop-1 TRACE Reregistering context
> (1/1): '4a7b56ff' org.apache.logging.log4j.core.LoggerContext@6b8e531c
> 2017-05-17 11:21:33,755 localhost-startStop-1 TRACE Unregistering 1 MBeans:
> [org.apache.logging.log4j2:type=4a7b56ff]
> 2017-05-17 11:21:33,755 localhost-startStop-1 TRACE Unregistering 1 MBeans:
> [org.apache.logging.log4j2:type=4a7b56ff,component=StatusLogger]
> 2017-05-17 11:21:33,755 localhost-startStop-1 TRACE Unregistering 1 MBeans:
> [org.apache.logging.log4j2:type=4a7b56ff,component=ContextSelector]
> 2017-05-17 11:21:33,771 localhost-startStop-1 TRACE Unregistering 5 MBeans:
> [org.apache.logging.log4j2:type=4a7b56ff,component=Loggers,name=org.apache.catalina,
> org.apache.logging.log4j2:type=4a7b56ff,component=Loggers,name=,
>
[jira] [Commented] (LOG4J2-1944) Should suppress message "ERROR No log4j2 configuration file found..." when programmatic API is used to config log4j.
[
https://issues.apache.org/jira/browse/LOG4J2-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055313#comment-16055313
]
Pierrick HYMBERT commented on LOG4J2-1944:
--
Can you please describe how your are getting your LoggerContext via
configuration API? Better to attach a simple test case.
If you are calling
{{org.apache.logging.log4j.core.config.Configurator.initialize(org.apache.logging.log4j.core.config.Configuration)}}
and
{{org.apache.logging.log4j.core.config.builder.api.ConfigurationBuilderFactory}}
this message would not appear.
> Should suppress message "ERROR No log4j2 configuration file found..." when
> programmatic API is used to config log4j.
>
>
> Key: LOG4J2-1944
> URL: https://issues.apache.org/jira/browse/LOG4J2-1944
> Project: Log4j 2
> Issue Type: Bug
> Components: Configurators
>Affects Versions: 2.6.2
>Reporter: Weian Deng
>Priority: Minor
>
> Log4j can be configured through log4j's configuration API. There are cases
> that an organization want to control the log4j configuration through the
> configuration API and discourage the use of config file. The error message
> {code}
> ERROR No log4j2 configuration file found. Using default configuration:
> logging only errors to the console.
> {code}
> is misleading.
> Can this be downgraded to WARN message, or provide a way to suppress it?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LOG4J2-1804) Rolling file %i based rolling broken in 2.8
[
https://issues.apache.org/jira/browse/LOG4J2-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15897220#comment-15897220
]
Pierrick HYMBERT commented on LOG4J2-1804:
--
Hello [~ralph.go...@dslextreme.com], it looks great for me, thank you. But I am
not the original creator of this jira.
[~bhmiller] Please check if you are ok with this fix in 2.8.1.
> Rolling file %i based rolling broken in 2.8
> ---
>
> Key: LOG4J2-1804
> URL: https://issues.apache.org/jira/browse/LOG4J2-1804
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.8
>Reporter: Brendan Miller
>Assignee: Ralph Goers
> Fix For: 2.8.1
>
> Attachments: LOG4J2-1804.junit.and.fix.patch, LOG4J2-1804.junit.patch
>
>
> Log files do not seem to be rolling up to the max number of files as
> specified in DefaultRolloverStrategy while utilizing a
> SizeBasedTriggeringPolicy. It is just rolling just to 1 file.
> Simple repro:
> log4j2.xml
> {code}
>
>
>
> fileName="__logs__/rolling.log"
> filePattern="__logs__/rolling.log.%i"
> immediateFlush="true">
>
>
>
>
>
>
>
>
>
>
>
> {code}
> MyApp.scala:
> {code}
> import scala.util.Random
> import org.apache.logging.log4j.LogManager
> object MyApp extends App {
> val log = LogManager.getLogger(this.getClass)
> var counter = 0L
> var bytes = new Array[Byte](1000)
> while (true) {
> Random.nextBytes(bytes)
> log.info(f"Log statement: $counter%08x ${bytes.mkString}")
> counter += 1
> Thread.sleep(5)
> }
> }
> {code}
> If you run that against 2.7, things roll fine. If you run that against 2.8,
> you'll only see rolling.log & rolling.log.1 in the __logs__ folder.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Updated] (LOG4J2-1804) Rolling file %i based rolling broken in 2.8
[
https://issues.apache.org/jira/browse/LOG4J2-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierrick HYMBERT updated LOG4J2-1804:
-
Attachment: LOG4J2-1804.junit.and.fix.patch
Suggested patch, but I think the approach of using an arbitrary file index to
generate a file pattern is wrong.
Maybe [~ralph.go...@dslextreme.com] has a better idea ?
> Rolling file %i based rolling broken in 2.8
> ---
>
> Key: LOG4J2-1804
> URL: https://issues.apache.org/jira/browse/LOG4J2-1804
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.8
>Reporter: Brendan Miller
> Attachments: LOG4J2-1804.junit.and.fix.patch, LOG4J2-1804.junit.patch
>
>
> Log files do not seem to be rolling up to the max number of files as
> specified in DefaultRolloverStrategy while utilizing a
> SizeBasedTriggeringPolicy. It is just rolling just to 1 file.
> Simple repro:
> log4j2.xml
> {code}
>
>
>
> fileName="__logs__/rolling.log"
> filePattern="__logs__/rolling.log.%i"
> immediateFlush="true">
>
>
>
>
>
>
>
>
>
>
>
> {code}
> MyApp.scala:
> {code}
> import scala.util.Random
> import org.apache.logging.log4j.LogManager
> object MyApp extends App {
> val log = LogManager.getLogger(this.getClass)
> var counter = 0L
> var bytes = new Array[Byte](1000)
> while (true) {
> Random.nextBytes(bytes)
> log.info(f"Log statement: $counter%08x ${bytes.mkString}")
> counter += 1
> Thread.sleep(5)
> }
> }
> {code}
> If you run that against 2.7, things roll fine. If you run that against 2.8,
> you'll only see rolling.log & rolling.log.1 in the __logs__ folder.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Updated] (LOG4J2-1804) Rolling file %i based rolling broken in 2.8
[
https://issues.apache.org/jira/browse/LOG4J2-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierrick HYMBERT updated LOG4J2-1804:
-
Attachment: LOG4J2-1804.junit.patch
> Rolling file %i based rolling broken in 2.8
> ---
>
> Key: LOG4J2-1804
> URL: https://issues.apache.org/jira/browse/LOG4J2-1804
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.8
>Reporter: Brendan Miller
> Attachments: LOG4J2-1804.junit.patch
>
>
> Log files do not seem to be rolling up to the max number of files as
> specified in DefaultRolloverStrategy while utilizing a
> SizeBasedTriggeringPolicy. It is just rolling just to 1 file.
> Simple repro:
> log4j2.xml
> {code}
>
>
>
> fileName="__logs__/rolling.log"
> filePattern="__logs__/rolling.log.%i"
> immediateFlush="true">
>
>
>
>
>
>
>
>
>
>
>
> {code}
> MyApp.scala:
> {code}
> import scala.util.Random
> import org.apache.logging.log4j.LogManager
> object MyApp extends App {
> val log = LogManager.getLogger(this.getClass)
> var counter = 0L
> var bytes = new Array[Byte](1000)
> while (true) {
> Random.nextBytes(bytes)
> log.info(f"Log statement: $counter%08x ${bytes.mkString}")
> counter += 1
> Thread.sleep(5)
> }
> }
> {code}
> If you run that against 2.7, things roll fine. If you run that against 2.8,
> you'll only see rolling.log & rolling.log.1 in the __logs__ folder.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Updated] (LOG4J2-1804) Rolling file %i based rolling broken in 2.8
[
https://issues.apache.org/jira/browse/LOG4J2-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierrick HYMBERT updated LOG4J2-1804:
-
Attachment: (was: LOG4J2-1804.junit.patch)
> Rolling file %i based rolling broken in 2.8
> ---
>
> Key: LOG4J2-1804
> URL: https://issues.apache.org/jira/browse/LOG4J2-1804
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.8
>Reporter: Brendan Miller
>
> Log files do not seem to be rolling up to the max number of files as
> specified in DefaultRolloverStrategy while utilizing a
> SizeBasedTriggeringPolicy. It is just rolling just to 1 file.
> Simple repro:
> log4j2.xml
> {code}
>
>
>
> fileName="__logs__/rolling.log"
> filePattern="__logs__/rolling.log.%i"
> immediateFlush="true">
>
>
>
>
>
>
>
>
>
>
>
> {code}
> MyApp.scala:
> {code}
> import scala.util.Random
> import org.apache.logging.log4j.LogManager
> object MyApp extends App {
> val log = LogManager.getLogger(this.getClass)
> var counter = 0L
> var bytes = new Array[Byte](1000)
> while (true) {
> Random.nextBytes(bytes)
> log.info(f"Log statement: $counter%08x ${bytes.mkString}")
> counter += 1
> Thread.sleep(5)
> }
> }
> {code}
> If you run that against 2.7, things roll fine. If you run that against 2.8,
> you'll only see rolling.log & rolling.log.1 in the __logs__ folder.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1804) Rolling file %i based rolling broken in 2.8
[
https://issues.apache.org/jira/browse/LOG4J2-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868278#comment-15868278
]
Pierrick HYMBERT commented on LOG4J2-1804:
--
Temporary solution for 2.8 by configuration is to use such "-" as separator
inside {{filePattern="__logs__/rolling.log-%i"}} instead of dot.
> Rolling file %i based rolling broken in 2.8
> ---
>
> Key: LOG4J2-1804
> URL: https://issues.apache.org/jira/browse/LOG4J2-1804
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.8
>Reporter: Brendan Miller
> Attachments: LOG4J2-1804.junit.patch
>
>
> Log files do not seem to be rolling up to the max number of files as
> specified in DefaultRolloverStrategy while utilizing a
> SizeBasedTriggeringPolicy. It is just rolling just to 1 file.
> Simple repro:
> log4j2.xml
> {code}
>
>
>
> fileName="__logs__/rolling.log"
> filePattern="__logs__/rolling.log.%i"
> immediateFlush="true">
>
>
>
>
>
>
>
>
>
>
>
> {code}
> MyApp.scala:
> {code}
> import scala.util.Random
> import org.apache.logging.log4j.LogManager
> object MyApp extends App {
> val log = LogManager.getLogger(this.getClass)
> var counter = 0L
> var bytes = new Array[Byte](1000)
> while (true) {
> Random.nextBytes(bytes)
> log.info(f"Log statement: $counter%08x ${bytes.mkString}")
> counter += 1
> Thread.sleep(5)
> }
> }
> {code}
> If you run that against 2.7, things roll fine. If you run that against 2.8,
> you'll only see rolling.log & rolling.log.1 in the __logs__ folder.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Comment Edited] (LOG4J2-1804) Rolling file %i based rolling broken in 2.8
[
https://issues.apache.org/jira/browse/LOG4J2-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868278#comment-15868278
]
Pierrick HYMBERT edited comment on LOG4J2-1804 at 2/15/17 6:07 PM:
---
Temporary solution for 2.8 by configuration is to use such "-" as separator
inside {code}filePattern="__logs__/rolling.log-%i"{code} instead of dot.
was (Author: phymbert):
Temporary solution for 2.8 by configuration is to use such "-" as separator
inside {{filePattern="__logs__/rolling.log-%i"}} instead of dot.
> Rolling file %i based rolling broken in 2.8
> ---
>
> Key: LOG4J2-1804
> URL: https://issues.apache.org/jira/browse/LOG4J2-1804
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.8
>Reporter: Brendan Miller
> Attachments: LOG4J2-1804.junit.patch
>
>
> Log files do not seem to be rolling up to the max number of files as
> specified in DefaultRolloverStrategy while utilizing a
> SizeBasedTriggeringPolicy. It is just rolling just to 1 file.
> Simple repro:
> log4j2.xml
> {code}
>
>
>
> fileName="__logs__/rolling.log"
> filePattern="__logs__/rolling.log.%i"
> immediateFlush="true">
>
>
>
>
>
>
>
>
>
>
>
> {code}
> MyApp.scala:
> {code}
> import scala.util.Random
> import org.apache.logging.log4j.LogManager
> object MyApp extends App {
> val log = LogManager.getLogger(this.getClass)
> var counter = 0L
> var bytes = new Array[Byte](1000)
> while (true) {
> Random.nextBytes(bytes)
> log.info(f"Log statement: $counter%08x ${bytes.mkString}")
> counter += 1
> Thread.sleep(5)
> }
> }
> {code}
> If you run that against 2.7, things roll fine. If you run that against 2.8,
> you'll only see rolling.log & rolling.log.1 in the __logs__ folder.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Updated] (LOG4J2-1804) Rolling file %i based rolling broken in 2.8
[
https://issues.apache.org/jira/browse/LOG4J2-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierrick HYMBERT updated LOG4J2-1804:
-
Attachment: LOG4J2-1804.junit.patch
Unit test to reproduce the issue.
> Rolling file %i based rolling broken in 2.8
> ---
>
> Key: LOG4J2-1804
> URL: https://issues.apache.org/jira/browse/LOG4J2-1804
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.8
>Reporter: Brendan Miller
> Attachments: LOG4J2-1804.junit.patch
>
>
> Log files do not seem to be rolling up to the max number of files as
> specified in DefaultRolloverStrategy while utilizing a
> SizeBasedTriggeringPolicy. It is just rolling just to 1 file.
> Simple repro:
> log4j2.xml
> {code}
>
>
>
> fileName="__logs__/rolling.log"
> filePattern="__logs__/rolling.log.%i"
> immediateFlush="true">
>
>
>
>
>
>
>
>
>
>
>
> {code}
> MyApp.scala:
> {code}
> import scala.util.Random
> import org.apache.logging.log4j.LogManager
> object MyApp extends App {
> val log = LogManager.getLogger(this.getClass)
> var counter = 0L
> var bytes = new Array[Byte](1000)
> while (true) {
> Random.nextBytes(bytes)
> log.info(f"Log statement: $counter%08x ${bytes.mkString}")
> counter += 1
> Thread.sleep(5)
> }
> }
> {code}
> If you run that against 2.7, things roll fine. If you run that against 2.8,
> you'll only see rolling.log & rolling.log.1 in the __logs__ folder.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported
[
https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490700#comment-15490700
]
Pierrick HYMBERT commented on LOG4J2-1320:
--
It is OK, thank you, please force close as far as I am not the original opener.
> Custom plugins are not loaded, URL protocol vfs is not supported
>
>
> Key: LOG4J2-1320
> URL: https://issues.apache.org/jira/browse/LOG4J2-1320
> Project: Log4j 2
> Issue Type: Bug
>Affects Versions: 2.5, 2.6.2
>Reporter: Paresh Varke
>Assignee: Gary Gregory
> Fix For: 2.7
>
> Attachments: LOG4J2-1320-2.patch, LOG4J2-1320-3.patch,
> LOG4J2-1320-testcase-cleanFoldersRule.patch, LOG4J2-1320.patch,
> test-jee-plugins-logging-parent.zip
>
>
> The URL protocol "vfs" from using a class loader is not supported; for
> example within JBoss EAP 6.2 and Log4j2 version 2.5. The custom plugin
> {{packages}} attribute fails to be resolve and plugin are not loaded for
> following URLs:
> {code}
> vfs:/C:/jboss/jboss-eap-6.4/standalone/deployments/com.xxx.yyy.application-ear.ear/lib/com.xxx.yyy.logging.jar/com/xxx/yyy/logging/config/
> vfs:/C:/jboss/jboss-eap-6.4/standalone/deployments/test-log4j2-web-standalone.war/WEB-INF/classes/org/hypik/test/jboss/eap7/logging/config/
> vfs:/content/mycustomweb.war/WEB-INF/classes/org/hypik/test/jboss/log4j2/logging/pluginweb/
> vfs:/content/test-log4k2-ear.ear/lib/test-log4j2-jar-plugins.jar/org/hypik/test/jboss/log4j2/pluginjar/
> vfs:/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/
> {code}
> Example of configuration:
> {code:xml}
> packages="com.logging.appender.log4j2">
> {code}
> It results following errors from {{StatusLogger}}:
> {quote}
> Could not search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory).
> {quote}
> And related logs:
> {code}
> 2016-03-10 07:08:41,909 INFO [stdout] (ServerService Thread Pool -- 275)
> INFO Scanning for classes in
> [/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/]
> matching criteria: annotated with @Plugin
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> 2016-03-10 07:08:41,909 ServerService Thread Pool -- 275 ERROR Could not
> search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.open(Native Method)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.(FileInputStream.java:146)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.loadImplementationsInJar(ResolverUtil.java:310)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.findInPackage(ResolverUtil.java:206)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginRegistry.loadFromPackage(PluginRegistry.java:222)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginManager.collectPlugins(PluginManager.java:152)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:180)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:209)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:492)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:246)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:232)
> 2016-03-10 07:08:41,911 INFO [stdout]
[jira] [Commented] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported
[
https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487022#comment-15487022
]
Pierrick HYMBERT commented on LOG4J2-1320:
--
Hi [~garydgregory], sorry to insist but I am afraid you didnt get last comment,
attached patch to clean folders within tests if it is still actual ?
> Custom plugins are not loaded, URL protocol vfs is not supported
>
>
> Key: LOG4J2-1320
> URL: https://issues.apache.org/jira/browse/LOG4J2-1320
> Project: Log4j 2
> Issue Type: Bug
>Affects Versions: 2.5, 2.6.2
>Reporter: Paresh Varke
>Assignee: Gary Gregory
> Fix For: 2.7
>
> Attachments: LOG4J2-1320-2.patch, LOG4J2-1320-3.patch,
> LOG4J2-1320-testcase-cleanFoldersRule.patch, LOG4J2-1320.patch,
> test-jee-plugins-logging-parent.zip
>
>
> The URL protocol "vfs" from using a class loader is not supported; for
> example within JBoss EAP 6.2 and Log4j2 version 2.5. The custom plugin
> {{packages}} attribute fails to be resolve and plugin are not loaded for
> following URLs:
> {code}
> vfs:/C:/jboss/jboss-eap-6.4/standalone/deployments/com.xxx.yyy.application-ear.ear/lib/com.xxx.yyy.logging.jar/com/xxx/yyy/logging/config/
> vfs:/C:/jboss/jboss-eap-6.4/standalone/deployments/test-log4j2-web-standalone.war/WEB-INF/classes/org/hypik/test/jboss/eap7/logging/config/
> vfs:/content/mycustomweb.war/WEB-INF/classes/org/hypik/test/jboss/log4j2/logging/pluginweb/
> vfs:/content/test-log4k2-ear.ear/lib/test-log4j2-jar-plugins.jar/org/hypik/test/jboss/log4j2/pluginjar/
> vfs:/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/
> {code}
> Example of configuration:
> {code:xml}
> packages="com.logging.appender.log4j2">
> {code}
> It results following errors from {{StatusLogger}}:
> {quote}
> Could not search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory).
> {quote}
> And related logs:
> {code}
> 2016-03-10 07:08:41,909 INFO [stdout] (ServerService Thread Pool -- 275)
> INFO Scanning for classes in
> [/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/]
> matching criteria: annotated with @Plugin
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> 2016-03-10 07:08:41,909 ServerService Thread Pool -- 275 ERROR Could not
> search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.open(Native Method)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.(FileInputStream.java:146)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.loadImplementationsInJar(ResolverUtil.java:310)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.findInPackage(ResolverUtil.java:206)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginRegistry.loadFromPackage(PluginRegistry.java:222)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginManager.collectPlugins(PluginManager.java:152)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:180)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:209)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:492)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:246)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
>
[jira] [Commented] (LOG4J2-1548) [CronTriggeringPolicy] ConfigurationScheduler schedules the task infinitely after first fire
[
https://issues.apache.org/jira/browse/LOG4J2-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457911#comment-15457911
]
Pierrick HYMBERT commented on LOG4J2-1548:
--
Hello [~SteffenO],
The fix is to be applied in {{ConfigurationScheduler}} and has been merged to
master:
https://issues.apache.org/jira/secure/attachment/12825255/LOG4J2-1548.patch
Others patch file attached are related to unit tests.
Cheers
> [CronTriggeringPolicy] ConfigurationScheduler schedules the task infinitely
> after first fire
>
>
> Key: LOG4J2-1548
> URL: https://issues.apache.org/jira/browse/LOG4J2-1548
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.6.2
>Reporter: Pierrick HYMBERT
>Priority: Blocker
> Fix For: 2.7
>
> Attachments: LOG4J2-1548-testcase-2.patch,
> LOG4J2-1548-testcase-cleanFoldersRule.patch, LOG4J2-1548-testcase.patch,
> LOG4J2-1548.patch
>
>
> After first fire at fixed time, rename/archive action is sheduled infinitely.
> Example of configuration:
> {code:xml}
> fileName="target/rolling-cron-once-a-day/rollingtest.log"
>
> filePattern="target/rolling-cron-once-a-day/rollingtest-%d{MMdd}_%d{HHmmss}-%i.log.gz"
>immediateFlush="true">
>
>
>
> {code}
> First trigger is scheduled at 13:58:27 then every new log entry generates an
> archive file.
> Test case and suggested fix attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Updated] (LOG4J2-1548) [CronTriggeringPolicy] ConfigurationScheduler schedules the task infinitely after first fire
[
https://issues.apache.org/jira/browse/LOG4J2-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierrick HYMBERT updated LOG4J2-1548:
-
Attachment: LOG4J2-1548-testcase-cleanFoldersRule.patch
[~garydgregory] I have added a small fix in the test to clean working folder
after execution.
> [CronTriggeringPolicy] ConfigurationScheduler schedules the task infinitely
> after first fire
>
>
> Key: LOG4J2-1548
> URL: https://issues.apache.org/jira/browse/LOG4J2-1548
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.6.2
>Reporter: Pierrick HYMBERT
>Priority: Blocker
> Fix For: 2.7
>
> Attachments: LOG4J2-1548-testcase-2.patch,
> LOG4J2-1548-testcase-cleanFoldersRule.patch, LOG4J2-1548-testcase.patch,
> LOG4J2-1548.patch
>
>
> After first fire at fixed time, rename/archive action is sheduled infinitely.
> Example of configuration:
> {code:xml}
> fileName="target/rolling-cron-once-a-day/rollingtest.log"
>
> filePattern="target/rolling-cron-once-a-day/rollingtest-%d{MMdd}_%d{HHmmss}-%i.log.gz"
>immediateFlush="true">
>
>
>
> {code}
> First trigger is scheduled at 13:58:27 then every new log entry generates an
> archive file.
> Test case and suggested fix attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Updated] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported
[
https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierrick HYMBERT updated LOG4J2-1320:
-
Attachment: LOG4J2-1320-testcase-cleanFoldersRule.patch
Hi [~garydgregory],
Attached patch to clean folders between tests of {{ResolverUtil}}.
> Custom plugins are not loaded, URL protocol vfs is not supported
>
>
> Key: LOG4J2-1320
> URL: https://issues.apache.org/jira/browse/LOG4J2-1320
> Project: Log4j 2
> Issue Type: Bug
>Affects Versions: 2.5, 2.6.2
>Reporter: Paresh Varke
> Fix For: 2.7
>
> Attachments: LOG4J2-1320-2.patch, LOG4J2-1320-3.patch,
> LOG4J2-1320-testcase-cleanFoldersRule.patch, LOG4J2-1320.patch,
> test-jee-plugins-logging-parent.zip
>
>
> The URL protocol "vfs" from using a class loader is not supported; for
> example within JBoss EAP 6.2 and Log4j2 version 2.5. The custom plugin
> {{packages}} attribute fails to be resolve and plugin are not loaded for
> following URLs:
> {code}
> vfs:/C:/jboss/jboss-eap-6.4/standalone/deployments/com.xxx.yyy.application-ear.ear/lib/com.xxx.yyy.logging.jar/com/xxx/yyy/logging/config/
> vfs:/C:/jboss/jboss-eap-6.4/standalone/deployments/test-log4j2-web-standalone.war/WEB-INF/classes/org/hypik/test/jboss/eap7/logging/config/
> vfs:/content/mycustomweb.war/WEB-INF/classes/org/hypik/test/jboss/log4j2/logging/pluginweb/
> vfs:/content/test-log4k2-ear.ear/lib/test-log4j2-jar-plugins.jar/org/hypik/test/jboss/log4j2/pluginjar/
> vfs:/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/
> {code}
> Example of configuration:
> {code:xml}
> packages="com.logging.appender.log4j2">
> {code}
> It results following errors from {{StatusLogger}}:
> {quote}
> Could not search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory).
> {quote}
> And related logs:
> {code}
> 2016-03-10 07:08:41,909 INFO [stdout] (ServerService Thread Pool -- 275)
> INFO Scanning for classes in
> [/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/]
> matching criteria: annotated with @Plugin
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> 2016-03-10 07:08:41,909 ServerService Thread Pool -- 275 ERROR Could not
> search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.open(Native Method)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.(FileInputStream.java:146)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.loadImplementationsInJar(ResolverUtil.java:310)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.findInPackage(ResolverUtil.java:206)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginRegistry.loadFromPackage(PluginRegistry.java:222)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginManager.collectPlugins(PluginManager.java:152)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:180)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:209)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:492)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:246)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:232)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService
[jira] [Comment Edited] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported
[
https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15438615#comment-15438615
]
Pierrick HYMBERT edited comment on LOG4J2-1320 at 8/26/16 7:38 AM:
---
_ok) Let's try this (please ammend if necessary)_
URL protocol vfs from class loader is not supported (for example within JBoss
EAP 6.x). Custom plugins {{packages}} attribute failed to be resolved and
plugin are not loaded for following URLs:
{code}
vfs:/C:/jboss/jboss-eap-6.4/standalone/deployments/com.xxx.yyy.application-ear.ear/lib/com.xxx.yyy.logging.jar/com/xxx/yyy/logging/config/
vfs:/C:/jboss/jboss-eap-6.4/standalone/deployments/test-log4j2-web-standalone.war/WEB-INF/classes/org/hypik/test/jboss/eap7/logging/config/
vfs:/content/mycustomweb.war/WEB-INF/classes/org/hypik/test/jboss/log4j2/logging/pluginweb/
vfs:/content/test-log4k2-ear.ear/lib/test-log4j2-jar-plugins.jar/org/hypik/test/jboss/log4j2/pluginjar/
vfs:/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/
{code}
Example of configuration:
{code:xml}
{code}
It results following errors from {{StatusLogger}}:
{quote}
Could not search jar file
'/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
for classes matching criteria: annotated with @Plugin file not found
java.io.FileNotFoundException:
/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
(No such file or directory).
{quote}
And related logs:
{code}
2016-03-10 07:08:41,909 INFO [stdout] (ServerService Thread Pool -- 275) INFO
Scanning for classes in
[/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/]
matching criteria: annotated with @Plugin
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
2016-03-10 07:08:41,909 ServerService Thread Pool -- 275 ERROR Could not search
jar file
'/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
for classes matching criteria: annotated with @Plugin file not found
java.io.FileNotFoundException:
/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
(No such file or directory)
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
at java.io.FileInputStream.open(Native Method)
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
at java.io.FileInputStream.(FileInputStream.java:146)
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.loadImplementationsInJar(ResolverUtil.java:310)
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.findInPackage(ResolverUtil.java:206)
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.plugins.util.PluginRegistry.loadFromPackage(PluginRegistry.java:222)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.plugins.util.PluginManager.collectPlugins(PluginManager.java:152)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:180)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:209)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:492)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:246)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:232)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.Configurator.initialize(Configurator.java:140)
2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.web.Log4jWebInitializerImpl.initializeNonJndi(Log4jWebInitializerImpl.java:168)
2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.web.Log4jWebInitializerImpl.start(Log4jWebInitializerImpl.java:110)
2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.web.Log4jServletContainerInitializer.onStartup(Log4jServletContainerInitializer.java:57)
2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
at
[jira] [Comment Edited] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported
[
https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15438615#comment-15438615
]
Pierrick HYMBERT edited comment on LOG4J2-1320 at 8/26/16 7:37 AM:
---
_ok) Let's try this (please ammend if necessary)_
URL protocol vfs from class loader is not supported (for example within JBoss
EAP 6.x). Custom plugins package attribute failed to be resolved and plugin are
not loaded for following URLs:
{code}
vfs:/C:/jboss/jboss-eap-6.4/standalone/deployments/com.xxx.yyy.application-ear.ear/lib/com.xxx.yyy.logging.jar/com/xxx/yyy/logging/config/
vfs:/C:/jboss/jboss-eap-6.4/standalone/deployments/test-log4j2-web-standalone.war/WEB-INF/classes/org/hypik/test/jboss/eap7/logging/config/
vfs:/content/mycustomweb.war/WEB-INF/classes/org/hypik/test/jboss/log4j2/logging/pluginweb/
vfs:/content/test-log4k2-ear.ear/lib/test-log4j2-jar-plugins.jar/org/hypik/test/jboss/log4j2/pluginjar/
vfs:/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/
{code}
Example of configuration:
{code:xml}
{code}
It results following errors from {{StatusLogger}}:
{quote}
Could not search jar file
'/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
for classes matching criteria: annotated with @Plugin file not found
java.io.FileNotFoundException:
/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
(No such file or directory).
{quote}
And related logs:
{code}
2016-03-10 07:08:41,909 INFO [stdout] (ServerService Thread Pool -- 275) INFO
Scanning for classes in
[/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/]
matching criteria: annotated with @Plugin
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
2016-03-10 07:08:41,909 ServerService Thread Pool -- 275 ERROR Could not search
jar file
'/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
for classes matching criteria: annotated with @Plugin file not found
java.io.FileNotFoundException:
/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
(No such file or directory)
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
at java.io.FileInputStream.open(Native Method)
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
at java.io.FileInputStream.(FileInputStream.java:146)
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.loadImplementationsInJar(ResolverUtil.java:310)
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.findInPackage(ResolverUtil.java:206)
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.plugins.util.PluginRegistry.loadFromPackage(PluginRegistry.java:222)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.plugins.util.PluginManager.collectPlugins(PluginManager.java:152)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:180)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:209)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:492)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:246)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:232)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.Configurator.initialize(Configurator.java:140)
2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.web.Log4jWebInitializerImpl.initializeNonJndi(Log4jWebInitializerImpl.java:168)
2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.web.Log4jWebInitializerImpl.start(Log4jWebInitializerImpl.java:110)
2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.web.Log4jServletContainerInitializer.onStartup(Log4jServletContainerInitializer.java:57)
2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
at
[jira] [Commented] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported
[
https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15438615#comment-15438615
]
Pierrick HYMBERT commented on LOG4J2-1320:
--
_ok) Let's try this (please ammend if necessary)_
URL protocol vfs from class loader is not supported (for example within JBoss
EAP 6.x). Custom plugins package attribute failed to be resolved and plugin are
not loaded for following URLs:
{code}
vfs:/C:/jboss/jboss-eap-6.4/standalone/deployments/com.xxx.yyy.application-ear.ear/lib/com.xxx.yyy.logging.jar/com/xxx/yyy/logging/config/
vfs:/C:/jboss/jboss-eap-6.4/standalone/deployments/test-log4j2-web-standalone.war/WEB-INF/classes/org/hypik/test/jboss/eap7/logging/config/
vfs:/content/mycustomweb.war/WEB-INF/classes/org/hypik/test/jboss/log4j2/logging/pluginweb/
vfs:/content/test-log4k2-ear.ear/lib/test-log4j2-jar-plugins.jar/org/hypik/test/jboss/log4j2/pluginjar/
vfs:/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/
{code}
Example of configuration:
{code:xml}
{code}
It results following errors from {{StatusLogger}}:
{quote}
Could not search jar file
'/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
for classes matching criteria: annotated with @Plugin file not found
java.io.FileNotFoundException:
/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
(No such file or directory).
{quote}
And related logs:
{quote}
2016-03-10 07:08:41,909 INFO [stdout] (ServerService Thread Pool -- 275) INFO
Scanning for classes in
[/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/]
matching criteria: annotated with @Plugin
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
2016-03-10 07:08:41,909 ServerService Thread Pool -- 275 ERROR Could not search
jar file
'/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
for classes matching criteria: annotated with @Plugin file not found
java.io.FileNotFoundException:
/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
(No such file or directory)
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
at java.io.FileInputStream.open(Native Method)
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
at java.io.FileInputStream.(FileInputStream.java:146)
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.loadImplementationsInJar(ResolverUtil.java:310)
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.findInPackage(ResolverUtil.java:206)
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.plugins.util.PluginRegistry.loadFromPackage(PluginRegistry.java:222)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.plugins.util.PluginManager.collectPlugins(PluginManager.java:152)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:180)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:209)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:492)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:246)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:232)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.Configurator.initialize(Configurator.java:140)
2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.web.Log4jWebInitializerImpl.initializeNonJndi(Log4jWebInitializerImpl.java:168)
2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.web.Log4jWebInitializerImpl.start(Log4jWebInitializerImpl.java:110)
2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.web.Log4jServletContainerInitializer.onStartup(Log4jServletContainerInitializer.java:57)
2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
at
[jira] [Comment Edited] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported
[
https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15438615#comment-15438615
]
Pierrick HYMBERT edited comment on LOG4J2-1320 at 8/26/16 7:35 AM:
---
_ok) Let's try this (please ammend if necessary)_
URL protocol vfs from class loader is not supported (for example within JBoss
EAP 6.x). Custom plugins package attribute failed to be resolved and plugin are
not loaded for following URLs:
{code}
vfs:/C:/jboss/jboss-eap-6.4/standalone/deployments/com.xxx.yyy.application-ear.ear/lib/com.xxx.yyy.logging.jar/com/xxx/yyy/logging/config/
vfs:/C:/jboss/jboss-eap-6.4/standalone/deployments/test-log4j2-web-standalone.war/WEB-INF/classes/org/hypik/test/jboss/eap7/logging/config/
vfs:/content/mycustomweb.war/WEB-INF/classes/org/hypik/test/jboss/log4j2/logging/pluginweb/
vfs:/content/test-log4k2-ear.ear/lib/test-log4j2-jar-plugins.jar/org/hypik/test/jboss/log4j2/pluginjar/
vfs:/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/
{code}
Example of configuration:
{code:xml}
{code}
It results following errors from {{StatusLogger}}:
{quote}
Could not search jar file
'/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
for classes matching criteria: annotated with @Plugin file not found
java.io.FileNotFoundException:
/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
(No such file or directory).
{quote}
And related logs:
{quote}
2016-03-10 07:08:41,909 INFO [stdout] (ServerService Thread Pool -- 275) INFO
Scanning for classes in
[/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/]
matching criteria: annotated with @Plugin
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
2016-03-10 07:08:41,909 ServerService Thread Pool -- 275 ERROR Could not search
jar file
'/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
for classes matching criteria: annotated with @Plugin file not found
java.io.FileNotFoundException:
/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
(No such file or directory)
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
at java.io.FileInputStream.open(Native Method)
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
at java.io.FileInputStream.(FileInputStream.java:146)
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.loadImplementationsInJar(ResolverUtil.java:310)
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.findInPackage(ResolverUtil.java:206)
2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.plugins.util.PluginRegistry.loadFromPackage(PluginRegistry.java:222)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.plugins.util.PluginManager.collectPlugins(PluginManager.java:152)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:180)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:209)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:492)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:246)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:232)
2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.core.config.Configurator.initialize(Configurator.java:140)
2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.web.Log4jWebInitializerImpl.initializeNonJndi(Log4jWebInitializerImpl.java:168)
2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.web.Log4jWebInitializerImpl.start(Log4jWebInitializerImpl.java:110)
2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
at
org.apache.logging.log4j.web.Log4jServletContainerInitializer.onStartup(Log4jServletContainerInitializer.java:57)
2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
at
[jira] [Commented] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported
[
https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15438504#comment-15438504
]
Pierrick HYMBERT commented on LOG4J2-1320:
--
Hi [~garydgregory],
Perfect, it will be just fine if some new protocols has to be supported later,
thank you.
This jira was opened by [~paresh.varke], so I cannot change description.
> Custom plugins are not loaded, URL protocol vfs is not supported
>
>
> Key: LOG4J2-1320
> URL: https://issues.apache.org/jira/browse/LOG4J2-1320
> Project: Log4j 2
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Paresh Varke
> Fix For: 2.7
>
> Attachments: LOG4J2-1320-2.patch, LOG4J2-1320-3.patch,
> LOG4J2-1320.patch, test-jee-plugins-logging-parent.zip
>
>
> Hi,
> I am using log4j2 version 2.5 with jboss eap 6.2. When i start application
> server with verbose="true" in log4j2.xml file. I am getting following error:
> {noformat}
> Could not search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory).
> {noformat}
> By debugging i found in method findInPackage of class ResolverUtil, class
> loader prepares enum of url (urls = loader.getResources(packageName)).
> And it gives
> {noformat}
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> {noformat}
> as value of urlPath (which is non existing path).
> I am putting here more logs
> {noformat}
> 2016-03-10 07:08:41,909 INFO [stdout] (ServerService Thread Pool -- 275)
> INFO Scanning for classes in
> [/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/]
> matching criteria: annotated with @Plugin
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> 2016-03-10 07:08:41,909 ServerService Thread Pool -- 275 ERROR Could not
> search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.open(Native Method)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.(FileInputStream.java:146)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.loadImplementationsInJar(ResolverUtil.java:310)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.findInPackage(ResolverUtil.java:206)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginRegistry.loadFromPackage(PluginRegistry.java:222)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginManager.collectPlugins(PluginManager.java:152)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:180)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:209)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:492)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:246)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:232)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.Configurator.initialize(Configurator.java:140)
> 2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.web.Log4jWebInitializerImpl.initializeNonJndi(Log4jWebInitializerImpl.java:168)
> 2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
> at
>
[jira] [Updated] (LOG4J2-1548) [CronTriggeringPolicy] ConfigurationScheduler schedules the task infinitely after first fire
[
https://issues.apache.org/jira/browse/LOG4J2-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierrick HYMBERT updated LOG4J2-1548:
-
Attachment: LOG4J2-1548-testcase-2.patch
Done.
Added a constant {{RollingAppenderCronOnceADayTest.CRON_DELAY}} set to 10
seconds (instead of 45s previously).
Checked that test still failed in this condition with previous revision of
{{ConfigurationScheduler.CronRunnable.run()}}.
Test is run in 18s on my environment and cron rename action is scheduled.
Need to be checked within integration build.
> [CronTriggeringPolicy] ConfigurationScheduler schedules the task infinitely
> after first fire
>
>
> Key: LOG4J2-1548
> URL: https://issues.apache.org/jira/browse/LOG4J2-1548
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.6.2
>Reporter: Pierrick HYMBERT
>Priority: Blocker
> Fix For: 2.7
>
> Attachments: LOG4J2-1548-testcase-2.patch,
> LOG4J2-1548-testcase.patch, LOG4J2-1548.patch
>
>
> After first fire at fixed time, rename/archive action is sheduled infinitely.
> Example of configuration:
> {code:xml}
> fileName="target/rolling-cron-once-a-day/rollingtest.log"
>
> filePattern="target/rolling-cron-once-a-day/rollingtest-%d{MMdd}_%d{HHmmss}-%i.log.gz"
>immediateFlush="true">
>
>
>
> {code}
> First trigger is scheduled at 13:58:27 then every new log entry generates an
> archive file.
> Test case and suggested fix attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Comment Edited] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported
[
https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436576#comment-15436576
]
Pierrick HYMBERT edited comment on LOG4J2-1320 at 8/25/16 9:40 AM:
---
# Added set of unit tests for {{ResolverUtil.findInPackage(Test, String)}} for
custom plugin lookup inside directories or jars
# Extracted all {{@Ignore}} tests from {{ResolverUtilTest}} that require custom
protocol url handler to {{ResolverUtilCustomProtocolTest}} - Maybe the approach
in {{@AfterClass}} to remove the factory is not good, to be checked ?
# Added tests for all diferents known vfs url format
# Changed in tests {{resourcebundle}} to {{bundleresource}} as expected in
{{ResolverUtil.BUNDLE_RESOURCE}}
# Fix ResolverUtil for vfs url inside a directory: previous version was listing
all the root directories regardless package parameter
was (Author: phymbert):
# Added set of unit tests for {{ResolverUtil.findInPackage(Test, String)}} for
custom plugin lookup inside directories or jars
# Extract all {{@Ignore}} tests that require custom protocol url handler to
{{ResolverUtilCustomProtocolTest}} - Maybe the approach in {{@AfterClass}} to
remove the factory is not good, to be checked
# Added tests for all diferents known vfs url format
# Changed in tests {{resourcebundle}} to {{bundleresource}} as expected in
{{ResolverUtil.BUNDLE_RESOURCE}}
# Fix ResolverUtil for vfs url inside a directory: previous version was listing
all the root directories regardless package parameter
> Custom plugins are not loaded, URL protocol vfs is not supported
>
>
> Key: LOG4J2-1320
> URL: https://issues.apache.org/jira/browse/LOG4J2-1320
> Project: Log4j 2
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Paresh Varke
> Fix For: 2.7
>
> Attachments: LOG4J2-1320-2.patch, LOG4J2-1320-3.patch,
> LOG4J2-1320.patch, test-jee-plugins-logging-parent.zip
>
>
> Hi,
> I am using log4j2 version 2.5 with jboss eap 6.2. When i start application
> server with verbose="true" in log4j2.xml file. I am getting following error:
> {noformat}
> Could not search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory).
> {noformat}
> By debugging i found in method findInPackage of class ResolverUtil, class
> loader prepares enum of url (urls = loader.getResources(packageName)).
> And it gives
> {noformat}
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> {noformat}
> as value of urlPath (which is non existing path).
> I am putting here more logs
> {noformat}
> 2016-03-10 07:08:41,909 INFO [stdout] (ServerService Thread Pool -- 275)
> INFO Scanning for classes in
> [/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/]
> matching criteria: annotated with @Plugin
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> 2016-03-10 07:08:41,909 ServerService Thread Pool -- 275 ERROR Could not
> search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.open(Native Method)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.(FileInputStream.java:146)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.loadImplementationsInJar(ResolverUtil.java:310)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.findInPackage(ResolverUtil.java:206)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginRegistry.loadFromPackage(PluginRegistry.java:222)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginManager.collectPlugins(PluginManager.java:152)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:180)
> 2016-03-10 07:08:41,911 INFO
[jira] [Comment Edited] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported
[
https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436576#comment-15436576
]
Pierrick HYMBERT edited comment on LOG4J2-1320 at 8/25/16 9:39 AM:
---
# Added set of unit tests for {{ResolverUtil.findInPackage(Test, String)}} for
custom plugin lookup inside directories or jars
# Extract all {{@Ignore}} tests that require custom protocol url handler to
{{ResolverUtilCustomProtocolTest}} - Maybe the approach in {{@AfterClass}} to
remove the factory is not good, to be checked
# Added tests for all diferents known vfs url format
# Changed in tests {{resourcebundle}} to {{bundleresource}} as expected in
{{ResolverUtil.BUNDLE_RESOURCE}}
# Fix ResolverUtil for vfs url inside a directory: previous version was listing
all the root directories regardless package parameter
was (Author: phymbert):
# Added set of unit tests for
{{org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.findInPackage(Test,
String)}} for custom plugin lookup inside directories or jars
# Extract all {{@Ignore}} tests that require custom protocol url handler to
{{ResolverUtilCustomProtocolTest}} - Maybe the approach in {{@AfterClass}} to
remove the factory is not good, to be checked
# Added tests for all diferents known vfs url format
# Changed in tests {{resourcebundle}} to {{bundleresource}} as expected in
{{ResolverUtil.BUNDLE_RESOURCE}}
# Fix ResolverUtil for vfs url inside a directory: previous version was listing
all the root directories regardless package parameter
> Custom plugins are not loaded, URL protocol vfs is not supported
>
>
> Key: LOG4J2-1320
> URL: https://issues.apache.org/jira/browse/LOG4J2-1320
> Project: Log4j 2
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Paresh Varke
> Fix For: 2.7
>
> Attachments: LOG4J2-1320-2.patch, LOG4J2-1320-3.patch,
> LOG4J2-1320.patch, test-jee-plugins-logging-parent.zip
>
>
> Hi,
> I am using log4j2 version 2.5 with jboss eap 6.2. When i start application
> server with verbose="true" in log4j2.xml file. I am getting following error:
> {noformat}
> Could not search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory).
> {noformat}
> By debugging i found in method findInPackage of class ResolverUtil, class
> loader prepares enum of url (urls = loader.getResources(packageName)).
> And it gives
> {noformat}
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> {noformat}
> as value of urlPath (which is non existing path).
> I am putting here more logs
> {noformat}
> 2016-03-10 07:08:41,909 INFO [stdout] (ServerService Thread Pool -- 275)
> INFO Scanning for classes in
> [/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/]
> matching criteria: annotated with @Plugin
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> 2016-03-10 07:08:41,909 ServerService Thread Pool -- 275 ERROR Could not
> search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.open(Native Method)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.(FileInputStream.java:146)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.loadImplementationsInJar(ResolverUtil.java:310)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.findInPackage(ResolverUtil.java:206)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginRegistry.loadFromPackage(PluginRegistry.java:222)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginManager.collectPlugins(PluginManager.java:152)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:180)
> 2016-03-10
[jira] [Comment Edited] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported
[
https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436576#comment-15436576
]
Pierrick HYMBERT edited comment on LOG4J2-1320 at 8/25/16 9:39 AM:
---
# Added set of unit tests for
{{org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.findInPackage(Test,
String)}} for custom plugin lookup inside directories or jars
# Extract all {{@Ignore}} tests that require custom protocol url handler to
{{ResolverUtilCustomProtocolTest}} - Maybe the approach in {{@AfterClass}} to
remove the factory is not good, to be checked
# Added tests for all diferents known vfs url format
# Changed in tests {{resourcebundle}} to {{bundleresource}} as expected in
{{ResolverUtil.BUNDLE_RESOURCE}}
# Fix ResolverUtil for vfs url inside a directory: previous version was listing
all the root directories regardless package parameter
was (Author: phymbert):
# Added set of unit tests for
{{org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.findInPackage(Test,
String)}} for custom plugin lookup inside directories or jars
# Extract all {{@Ignore}} tests that require custom protocol url handler to
{{ResolverUtilCustomProtocolTest}} - Maybe the approach in {{@AfterClass}} to
remove the factory is not good, to be checked
# Added tests for all diferents known vfs url format
# Changed in tests {{resourcebundle}} to {{bundleresource}} as expected in
{{ResolverUtil.BUNDLE_RESOURCE}}
# Fix ResolverUtil for vfs url inside a directory: previous version was listing
all the root directories regardless package parameter
> Custom plugins are not loaded, URL protocol vfs is not supported
>
>
> Key: LOG4J2-1320
> URL: https://issues.apache.org/jira/browse/LOG4J2-1320
> Project: Log4j 2
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Paresh Varke
> Fix For: 2.7
>
> Attachments: LOG4J2-1320-2.patch, LOG4J2-1320-3.patch,
> LOG4J2-1320.patch, test-jee-plugins-logging-parent.zip
>
>
> Hi,
> I am using log4j2 version 2.5 with jboss eap 6.2. When i start application
> server with verbose="true" in log4j2.xml file. I am getting following error:
> {noformat}
> Could not search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory).
> {noformat}
> By debugging i found in method findInPackage of class ResolverUtil, class
> loader prepares enum of url (urls = loader.getResources(packageName)).
> And it gives
> {noformat}
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> {noformat}
> as value of urlPath (which is non existing path).
> I am putting here more logs
> {noformat}
> 2016-03-10 07:08:41,909 INFO [stdout] (ServerService Thread Pool -- 275)
> INFO Scanning for classes in
> [/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/]
> matching criteria: annotated with @Plugin
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> 2016-03-10 07:08:41,909 ServerService Thread Pool -- 275 ERROR Could not
> search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.open(Native Method)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.(FileInputStream.java:146)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.loadImplementationsInJar(ResolverUtil.java:310)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.findInPackage(ResolverUtil.java:206)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginRegistry.loadFromPackage(PluginRegistry.java:222)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginManager.collectPlugins(PluginManager.java:152)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
>
[jira] [Updated] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported
[
https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierrick HYMBERT updated LOG4J2-1320:
-
Attachment: LOG4J2-1320-3.patch
# Added set of unit tests for
{{org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.findInPackage(Test,
String)}} for custom plugin lookup inside directories or jars
# Extract all {{@Ignore}} tests that require custom protocol url handler to
{{ResolverUtilCustomProtocolTest}} - Maybe the approach in {{@AfterClass}} to
remove the factory is not good, to be checked
# Added tests for all diferents known vfs url format
# Changed in tests {{resourcebundle}} to {{bundleresource}} as expected in
{{ResolverUtil.BUNDLE_RESOURCE}}
# Fix ResolverUtil for vfs url inside a directory: previous version was listing
all the root directories regardless package parameter
> Custom plugins are not loaded, URL protocol vfs is not supported
>
>
> Key: LOG4J2-1320
> URL: https://issues.apache.org/jira/browse/LOG4J2-1320
> Project: Log4j 2
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Paresh Varke
> Fix For: 2.7
>
> Attachments: LOG4J2-1320-2.patch, LOG4J2-1320-3.patch,
> LOG4J2-1320.patch, test-jee-plugins-logging-parent.zip
>
>
> Hi,
> I am using log4j2 version 2.5 with jboss eap 6.2. When i start application
> server with verbose="true" in log4j2.xml file. I am getting following error:
> {noformat}
> Could not search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory).
> {noformat}
> By debugging i found in method findInPackage of class ResolverUtil, class
> loader prepares enum of url (urls = loader.getResources(packageName)).
> And it gives
> {noformat}
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> {noformat}
> as value of urlPath (which is non existing path).
> I am putting here more logs
> {noformat}
> 2016-03-10 07:08:41,909 INFO [stdout] (ServerService Thread Pool -- 275)
> INFO Scanning for classes in
> [/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/]
> matching criteria: annotated with @Plugin
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> 2016-03-10 07:08:41,909 ServerService Thread Pool -- 275 ERROR Could not
> search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.open(Native Method)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.(FileInputStream.java:146)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.loadImplementationsInJar(ResolverUtil.java:310)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.findInPackage(ResolverUtil.java:206)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginRegistry.loadFromPackage(PluginRegistry.java:222)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginManager.collectPlugins(PluginManager.java:152)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:180)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:209)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:492)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:246)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:232)
> 2016-03-10
[jira] [Commented] (LOG4J2-1480) CronTriggeringPolicy timing / file deletion issue
[ https://issues.apache.org/jira/browse/LOG4J2-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434788#comment-15434788 ] Pierrick HYMBERT commented on LOG4J2-1480: -- I accidentally created a cloned jira in LOG4J2-1548. Attached unit test and fix there. > CronTriggeringPolicy timing / file deletion issue > - > > Key: LOG4J2-1480 > URL: https://issues.apache.org/jira/browse/LOG4J2-1480 > Project: Log4j 2 > Issue Type: Bug >Affects Versions: 2.6.2 > Environment: 2013 macbook pro running OSX El Capitan. Log4j2 is > running as a module dependency to a bigger Vertx server project. >Reporter: matthew beckham > > Most of this issue is outlined in this stack overflow post: > http://stackoverflow.com/questions/38514101/log4j2-default-rollover-strategy-deleting-new-log-files > This details my attempt to use the CronTriggeringPolicy to rollover a log > file. My longterm goal was to have it roll over every 15 minutes, but used 1 > minutes intervals for testing (I did also try with 3 and 5 minute intervals > with the same outcome). > The gist of the issue is that after the first triggering of the cron > triggering policy (which happens at the correct time), the rollover mechanism > will disregard the cron schedule in place and attempt to rollover every > second. In addition to this, the log file that is created from a rollover can > be deleted immediately after it is created. The log file appears to not get > deleted if there is a iterator argument (%i) in the file name though. > I don't know if these are two separate issues, or if the file deletion is a > side effect of the cron scheduling getting messed up. > For now I have switched to using TimeBasedTriggeringPolicy and that appears > to be working correctly at the moment. > Logs and sample configuration code can be found in the linked stack overflow > post. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Updated] (LOG4J2-1548) [CronTriggeringPolicy] ConfigurationScheduler schedules the task infinitely after first fire
[
https://issues.apache.org/jira/browse/LOG4J2-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierrick HYMBERT updated LOG4J2-1548:
-
Attachment: LOG4J2-1548.patch
Suggested fix.
> [CronTriggeringPolicy] ConfigurationScheduler schedules the task infinitely
> after first fire
>
>
> Key: LOG4J2-1548
> URL: https://issues.apache.org/jira/browse/LOG4J2-1548
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.6.2
>Reporter: Pierrick HYMBERT
>Priority: Blocker
> Attachments: LOG4J2-1548-testcase.patch, LOG4J2-1548.patch
>
>
> After first fire at fixed time, rename/archive action is sheduled infinitely.
> Example of configuration:
> {code:xml}
> fileName="target/rolling-cron-once-a-day/rollingtest.log"
>
> filePattern="target/rolling-cron-once-a-day/rollingtest-%d{MMdd}_%d{HHmmss}-%i.log.gz"
>immediateFlush="true">
>
>
>
> {code}
> First trigger is scheduled at 13:58:27 then every new log entry generates an
> archive file.
> Test case and suggested fix attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Updated] (LOG4J2-1548) [CronTriggeringPolicy] ConfigurationScheduler schedules the task infinitely after first fire
[
https://issues.apache.org/jira/browse/LOG4J2-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierrick HYMBERT updated LOG4J2-1548:
-
Attachment: LOG4J2-1548-testcase.patch
Test case.
> [CronTriggeringPolicy] ConfigurationScheduler schedules the task infinitely
> after first fire
>
>
> Key: LOG4J2-1548
> URL: https://issues.apache.org/jira/browse/LOG4J2-1548
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.6.2
>Reporter: Pierrick HYMBERT
>Priority: Blocker
> Attachments: LOG4J2-1548-testcase.patch
>
>
> After first fire at fixed time, rename/archive action is sheduled infinitely.
> Example of configuration:
> {code:xml}
> fileName="target/rolling-cron-once-a-day/rollingtest.log"
>
> filePattern="target/rolling-cron-once-a-day/rollingtest-%d{MMdd}_%d{HHmmss}-%i.log.gz"
>immediateFlush="true">
>
>
>
> {code}
> First trigger is scheduled at 13:58:27 then every new log entry generates an
> archive file.
> Test case and suggested fix attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Created] (LOG4J2-1548) [CronTriggeringPolicy] ConfigurationScheduler schedules the task infinitely after first fire
Pierrick HYMBERT created LOG4J2-1548:
Summary: [CronTriggeringPolicy] ConfigurationScheduler schedules
the task infinitely after first fire
Key: LOG4J2-1548
URL: https://issues.apache.org/jira/browse/LOG4J2-1548
Project: Log4j 2
Issue Type: Bug
Components: Core
Affects Versions: 2.6.2
Reporter: Pierrick HYMBERT
Priority: Blocker
After first fire at fixed time, rename/archive action is sheduled infinitely.
Example of configuration:
{code:xml}
{code}
First trigger is scheduled at 13:58:27 then every new log entry generates an
archive file.
Test case and suggested fix attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Updated] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported
[
https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierrick HYMBERT updated LOG4J2-1320:
-
Attachment: LOG4J2-1320-2.patch
test-jee-plugins-logging-parent.zip
It is OK for my case: a jar inside an EAR over vfs protocol.
BUT the original jira description from [~paresh.varke] was about
{{service-app.war/WEB-INF/classes}} :
1) Attached a complementary fix for this case (classes folder over vfs
protocol)
2) I provided sample JEE mvn modules (WAR standalone with plugin in classes
and an EAR with plugins in jar) that I have tested under jboss EAP 6.4 on linux
and windows
Additional URL tested OK:
{code}
vfs:/C:/jboss/jboss-eap-6.4/standalone/deployments/test-log4j2-web-standalone.war/WEB-INF/classes/org/hypik/test/jboss/eap7/logging/config/
vfs:/content/mycustomweb.war/WEB-INF/classes/org/hypik/test/jboss/log4j2/logging/pluginweb/
vfs:/content/test-log4k2-ear.ear/lib/test-log4j2-jar-plugins.jar/org/hypik/test/jboss/log4j2/pluginjar/
{code}
> Custom plugins are not loaded, URL protocol vfs is not supported
>
>
> Key: LOG4J2-1320
> URL: https://issues.apache.org/jira/browse/LOG4J2-1320
> Project: Log4j 2
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Paresh Varke
> Fix For: 2.7
>
> Attachments: LOG4J2-1320-2.patch, LOG4J2-1320.patch,
> test-jee-plugins-logging-parent.zip
>
>
> Hi,
> I am using log4j2 version 2.5 with jboss eap 6.2. When i start application
> server with verbose="true" in log4j2.xml file. I am getting following error:
> {noformat}
> Could not search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory).
> {noformat}
> By debugging i found in method findInPackage of class ResolverUtil, class
> loader prepares enum of url (urls = loader.getResources(packageName)).
> And it gives
> {noformat}
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> {noformat}
> as value of urlPath (which is non existing path).
> I am putting here more logs
> {noformat}
> 2016-03-10 07:08:41,909 INFO [stdout] (ServerService Thread Pool -- 275)
> INFO Scanning for classes in
> [/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/]
> matching criteria: annotated with @Plugin
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> 2016-03-10 07:08:41,909 ServerService Thread Pool -- 275 ERROR Could not
> search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.open(Native Method)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.(FileInputStream.java:146)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.loadImplementationsInJar(ResolverUtil.java:310)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.findInPackage(ResolverUtil.java:206)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginRegistry.loadFromPackage(PluginRegistry.java:222)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginManager.collectPlugins(PluginManager.java:152)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:180)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:209)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:492)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:246)
> 2016-03-10 07:08:41,911 INFO [stdout]
[jira] [Commented] (LOG4J2-1320) Custom plugins are not loaded
[
https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15433100#comment-15433100
]
Pierrick HYMBERT commented on LOG4J2-1320:
--
VFS url looks like:
{code}
vfs:/C:/jboss/jboss-eap-6.4/standalone/deployments/com.xxx.yyy.application-ear.ear/lib/com.xxx.yyy.logging.jar/com/xxx/yyy/logging/config/
{code}
> Custom plugins are not loaded
> -
>
> Key: LOG4J2-1320
> URL: https://issues.apache.org/jira/browse/LOG4J2-1320
> Project: Log4j 2
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Paresh Varke
> Attachments: LOG4J2-1320.patch
>
>
> Hi,
> I am using log4j2 version 2.5 with jboss eap 6.2. When i start application
> server with verbose="true" in log4j2.xml file. I am getting following error:
> {noformat}
> Could not search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory).
> {noformat}
> By debugging i found in method findInPackage of class ResolverUtil, class
> loader prepares enum of url (urls = loader.getResources(packageName)).
> And it gives
> {noformat}
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> {noformat}
> as value of urlPath (which is non existing path).
> I am putting here more logs
> {noformat}
> 2016-03-10 07:08:41,909 INFO [stdout] (ServerService Thread Pool -- 275)
> INFO Scanning for classes in
> [/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/]
> matching criteria: annotated with @Plugin
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> 2016-03-10 07:08:41,909 ServerService Thread Pool -- 275 ERROR Could not
> search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.open(Native Method)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.(FileInputStream.java:146)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.loadImplementationsInJar(ResolverUtil.java:310)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.findInPackage(ResolverUtil.java:206)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginRegistry.loadFromPackage(PluginRegistry.java:222)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginManager.collectPlugins(PluginManager.java:152)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:180)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:209)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:492)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:246)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:232)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.Configurator.initialize(Configurator.java:140)
> 2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.web.Log4jWebInitializerImpl.initializeNonJndi(Log4jWebInitializerImpl.java:168)
> 2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.web.Log4jWebInitializerImpl.start(Log4jWebInitializerImpl.java:110)
> 2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
> at
>
[jira] [Updated] (LOG4J2-1320) Custom plugins are not loaded
[
https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierrick HYMBERT updated LOG4J2-1320:
-
Attachment: LOG4J2-1320.patch
> Custom plugins are not loaded
> -
>
> Key: LOG4J2-1320
> URL: https://issues.apache.org/jira/browse/LOG4J2-1320
> Project: Log4j 2
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Paresh Varke
> Attachments: LOG4J2-1320.patch
>
>
> Hi,
> I am using log4j2 version 2.5 with jboss eap 6.2. When i start application
> server with verbose="true" in log4j2.xml file. I am getting following error:
> {noformat}
> Could not search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory).
> {noformat}
> By debugging i found in method findInPackage of class ResolverUtil, class
> loader prepares enum of url (urls = loader.getResources(packageName)).
> And it gives
> {noformat}
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> {noformat}
> as value of urlPath (which is non existing path).
> I am putting here more logs
> {noformat}
> 2016-03-10 07:08:41,909 INFO [stdout] (ServerService Thread Pool -- 275)
> INFO Scanning for classes in
> [/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/]
> matching criteria: annotated with @Plugin
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> 2016-03-10 07:08:41,909 ServerService Thread Pool -- 275 ERROR Could not
> search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.open(Native Method)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.(FileInputStream.java:146)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.loadImplementationsInJar(ResolverUtil.java:310)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.findInPackage(ResolverUtil.java:206)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginRegistry.loadFromPackage(PluginRegistry.java:222)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginManager.collectPlugins(PluginManager.java:152)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:180)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:209)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:492)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:246)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:232)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.Configurator.initialize(Configurator.java:140)
> 2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.web.Log4jWebInitializerImpl.initializeNonJndi(Log4jWebInitializerImpl.java:168)
> 2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.web.Log4jWebInitializerImpl.start(Log4jWebInitializerImpl.java:110)
> 2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.web.Log4jServletContainerInitializer.onStartup(Log4jServletContainerInitializer.java:57)
> 2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
> at
>
[jira] [Commented] (LOG4J2-1320) Custom plugins are not loaded
[
https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432438#comment-15432438
]
Pierrick HYMBERT commented on LOG4J2-1320:
--
it looks VFS (not VFSZIP) protocol is not handled properly, attached (simple)
fix for JBoss EAP 6.4.
Please review.
> Custom plugins are not loaded
> -
>
> Key: LOG4J2-1320
> URL: https://issues.apache.org/jira/browse/LOG4J2-1320
> Project: Log4j 2
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Paresh Varke
>
> Hi,
> I am using log4j2 version 2.5 with jboss eap 6.2. When i start application
> server with verbose="true" in log4j2.xml file. I am getting following error:
> {noformat}
> Could not search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory).
> {noformat}
> By debugging i found in method findInPackage of class ResolverUtil, class
> loader prepares enum of url (urls = loader.getResources(packageName)).
> And it gives
> {noformat}
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> {noformat}
> as value of urlPath (which is non existing path).
> I am putting here more logs
> {noformat}
> 2016-03-10 07:08:41,909 INFO [stdout] (ServerService Thread Pool -- 275)
> INFO Scanning for classes in
> [/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2/]
> matching criteria: annotated with @Plugin
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> 2016-03-10 07:08:41,909 ServerService Thread Pool -- 275 ERROR Could not
> search jar file
> '/content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2'
> for classes matching criteria: annotated with @Plugin file not found
> java.io.FileNotFoundException:
> /content/myapp.ear/service-app.war/WEB-INF/classes/com/logging/appender/log4j2
> (No such file or directory)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.open(Native Method)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at java.io.FileInputStream.(FileInputStream.java:146)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.loadImplementationsInJar(ResolverUtil.java:310)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.ResolverUtil.findInPackage(ResolverUtil.java:206)
> 2016-03-10 07:08:41,910 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginRegistry.loadFromPackage(PluginRegistry.java:222)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginManager.collectPlugins(PluginManager.java:152)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:180)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:209)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:492)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:246)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:232)
> 2016-03-10 07:08:41,911 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.core.config.Configurator.initialize(Configurator.java:140)
> 2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.web.Log4jWebInitializerImpl.initializeNonJndi(Log4jWebInitializerImpl.java:168)
> 2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.web.Log4jWebInitializerImpl.start(Log4jWebInitializerImpl.java:110)
> 2016-03-10 07:08:41,915 INFO [stdout] (ServerService Thread Pool -- 275)
> at
> org.apache.logging.log4j.web.Log4jServletContainerInitializer.onStartup(Log4jServletContainerInitializer.java:57)
> 2016-03-10 07:08:41,915 INFO [stdout]
