[jira] [Updated] (LOG4J2-3416) Line Number Not getting printed
[
https://issues.apache.org/jira/browse/LOG4J2-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sagar Salal updated LOG4J2-3416:
Summary: Line Number Not getting printed (was: Line Number Not getting
printeed)
> Line Number Not getting printed
> ---
>
> Key: LOG4J2-3416
> URL: https://issues.apache.org/jira/browse/LOG4J2-3416
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.17.0
>Reporter: Sagar Salal
>Priority: Major
> Attachments: log4j2.xml
>
>
> I am not able to print line numbers in logs. I am using 2.17.0 version and
> using pattern
> pattern="%d\{-MM-dd HH:mm:ss,SSS} [%t] %-5p %logger\{36}:%L %X - %m%n" />.
>
> I have tried with multiple patterns but issue still persists. It is basically
> neglecting *%L.* Can anyone please have a look at this?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (LOG4J2-3416) Line Number Not getting printed in log file
[
https://issues.apache.org/jira/browse/LOG4J2-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sagar Salal updated LOG4J2-3416:
Summary: Line Number Not getting printed in log file (was: Line Number Not
getting printed)
> Line Number Not getting printed in log file
> ---
>
> Key: LOG4J2-3416
> URL: https://issues.apache.org/jira/browse/LOG4J2-3416
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.17.0
>Reporter: Sagar Salal
>Priority: Major
> Attachments: log4j2.xml
>
>
> I am not able to print line numbers in logs. I am using 2.17.0 version and
> using pattern
> pattern="%d\{-MM-dd HH:mm:ss,SSS} [%t] %-5p %logger\{36}:%L %X - %m%n" />.
>
> I have tried with multiple patterns but issue still persists. It is basically
> neglecting *%L.* Can anyone please have a look at this?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3416) Line Number Not getting printeed
[
https://issues.apache.org/jira/browse/LOG4J2-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17506006#comment-17506006
]
Sagar Salal commented on LOG4J2-3416:
-
[~vy] Please find attached log4j2.xml. [^log4j2.xml]
I am not able to see line number and method name int the log file. I had also
tried with multiple pattern layout but still not able to see anything in logs.
It was working properly in older version *2.5.* Right now I am using log4j2
version 2.17.
CC : [~rgoers]
> Line Number Not getting printeed
>
>
> Key: LOG4J2-3416
> URL: https://issues.apache.org/jira/browse/LOG4J2-3416
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.17.0
>Reporter: Sagar Salal
>Priority: Major
> Attachments: log4j2.xml
>
>
> I am not able to print line numbers in logs. I am using 2.17.0 version and
> using pattern
> pattern="%d\{-MM-dd HH:mm:ss,SSS} [%t] %-5p %logger\{36}:%L %X - %m%n" />.
>
> I have tried with multiple patterns but issue still persists. It is basically
> neglecting *%L.* Can anyone please have a look at this?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (LOG4J2-3416) Line Number Not getting printeed
[
https://issues.apache.org/jira/browse/LOG4J2-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sagar Salal updated LOG4J2-3416:
Attachment: log4j2.xml
> Line Number Not getting printeed
>
>
> Key: LOG4J2-3416
> URL: https://issues.apache.org/jira/browse/LOG4J2-3416
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.17.0
>Reporter: Sagar Salal
>Priority: Major
> Attachments: log4j2.xml
>
>
> I am not able to print line numbers in logs. I am using 2.17.0 version and
> using pattern
> pattern="%d\{-MM-dd HH:mm:ss,SSS} [%t] %-5p %logger\{36}:%L %X - %m%n" />.
>
> I have tried with multiple patterns but issue still persists. It is basically
> neglecting *%L.* Can anyone please have a look at this?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3432) RollingFileAppender fails after 100 backup cycles if filePattern contains "%04i" .
[
https://issues.apache.org/jira/browse/LOG4J2-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17505921#comment-17505921
]
Gary D. Gregory commented on LOG4J2-3432:
-
Hello [~CarlSmotricz]
Thank you for your report.
Would you check to see if this still happens with 2.17.2?
TY.
> RollingFileAppender fails after 100 backup cycles if filePattern contains
> "%04i" .
> --
>
> Key: LOG4J2-3432
> URL: https://issues.apache.org/jira/browse/LOG4J2-3432
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.17.1
> Environment: * Red Hat Enterprise Linux Server release 6.10 (Santiago)
> * java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
> * 301873 Mar 9 07:53 log4j-api-2.17.1.jar
> 1790452 Mar 9 07:53 log4j-core-2.17.1.jar
>
>Reporter: Carl Smotricz
>Priority: Major
> Attachments: Main.java, log4j2.xml, runit.sh
>
>
> If a {{%i}} formatter in a filePattern includes a width specifier, e.g. "%4i"
> or "%04i", file renaming fails after a certain fixed number of cycles. After
> that, successive backups are renamed to the maximum cycle number and
> overwrite previous files of that same cycle number, regardless of min and max
> settings on the appender. Here are some failure modes I've found by testing:
> * if {{filePattern}} contains {{{}%06i{}}}, cycling breaks after 100.
> * if {{filePattern}} contains {{{}%006i{}}}, it breaks after 100 also.
> * if {{filePattern}} contains {{{}%6i{}}}, it breaks after 10.
> * if {{filePattern}} contains {{%06i}} and
> {{{}DefaultRolloverStrategy.min{}}}=1, {{{}max{}}}=9, it breaks after
> just 1.
> Now, the doc doesn't mention the %i spec supporting width and leading zero
> modifiers in the manner of printf() or String.format() . Yet, those
> variations (which I think other users will also be tempted to try) work -
> until they don't. So apparently width and padding on that spec are
> implemented but buggy.
> The doc for RollingRandomAccessFileAppender explicitly recommends these
> format modifiers:
> {quote}... and/or a %i which represents an integer counter. The integer
> counter allows specifying a padding, like %3i for space-padding the counter
> to 3 digits or (usually more useful) %03i for zero-padding the counter to 3
> digits.
> {quote}
> ...but I haven't verified that the problem occurs with that appender as well.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [logging-log4j2] vy merged pull request #781: Update customconfig.xml
vy merged pull request #781: URL: https://github.com/apache/logging-log4j2/pull/781 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [logging-log4j-scala] vy merged pull request #18: log4j 2.17.2
vy merged pull request #18: URL: https://github.com/apache/logging-log4j-scala/pull/18 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [logging-log4j2] dependabot[bot] commented on pull request #772: Bump logbackVersion from 1.2.3 to 1.2.10
dependabot[bot] commented on pull request #772: URL: https://github.com/apache/logging-log4j2/pull/772#issuecomment-1066170478 Superseded by #793. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [logging-log4j2] dependabot[bot] closed pull request #772: Bump logbackVersion from 1.2.3 to 1.2.10
dependabot[bot] closed pull request #772: URL: https://github.com/apache/logging-log4j2/pull/772 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [logging-log4j2] dependabot[bot] opened a new pull request #793: Bump logbackVersion from 1.2.3 to 1.2.11
dependabot[bot] opened a new pull request #793: URL: https://github.com/apache/logging-log4j2/pull/793 Bumps `logbackVersion` from 1.2.3 to 1.2.11. Updates `logback-core` from 1.2.3 to 1.2.11 Updates `logback-classic` from 1.2.3 to 1.2.11 Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [logging-log4j-scala] vy merged pull request #17: ci: setup-java v3
vy merged pull request #17: URL: https://github.com/apache/logging-log4j-scala/pull/17 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [logging-log4j2] vy merged pull request #776: Bump slf4jVersion from 1.7.35 to 1.7.36
vy merged pull request #776: URL: https://github.com/apache/logging-log4j2/pull/776 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (LOG4J2-3433) Multiple log files need to be generated based on package
[
https://issues.apache.org/jira/browse/LOG4J2-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17505895#comment-17505895
]
Ralph Goers commented on LOG4J2-3433:
-
It would have been helpful to see the log4j 1.x configuration that you say
worked. Based on what you asked for here is the XML configuration (I don't like
working with the properties configuration).
{code:java}
%d{-MM-dd HH:mm:ss.SSS} (%t) %-5level [%logger\{36}.%M:%L]
- %msg%n
%d{-MM-dd HH:mm:ss.SSS} (%t) %-5level [%logger\{36}.%M:%L]
- %msg%n
{code}
Note that with this configuration the second appenderRef could be removed and
additivity set to true.
Also, no Delete action is configured so the disk will eventually fill up.
> Multiple log files need to be generated based on package
>
>
> Key: LOG4J2-3433
> URL: https://issues.apache.org/jira/browse/LOG4J2-3433
> Project: Log4j 2
> Issue Type: Request
> Components: Appenders, Configuration
>Affects Versions: 2.17.2
> Environment: linux OS
>Reporter: Thangadurai Kandhasamy
>Priority: Blocker
> Labels: documentation, features
> Attachments: log4j2.properties
>
>
> Team,
> We are using Apache log4j 1.2.x we are able to generate Multiple log files
> based on package.
> As we planned to upgrade from 1.2.x to 2.17.0 we are not able to generate
> Multiple log files based on package.
> Assume our packages are
> 1.com.application.test.pack1
> 2.com.application.test.pack2
> As per below configuration {+}we could get all the logs into *single log
> file*{+}.
> logger.app.name = com.application.test
> We +expect to log all the logs related+ to *com.application.test.pack1*
> should be *{color:#ff8b00}pack1.log{color};* same way
> *com.application.test.pack2* should be *{color:#ff8b00}pack2.log{color},* We
> tried multiple options and also referred official documentation site
> [https://logging.apache.org/log4j/2.x/manual/appenders.html]. However we
> don't find any reference based on our need.
> Below is the log4j2.properties. Same you can find in the attachment section.
> ___
> status = warn
> appender.console.type = Console
> appender.console.name = LogToConsole
> appender.console.layout.type = PatternLayout
> appender.console.layout.pattern = %d\{-MM-dd HH:mm:ss.SSS} (%t) %-5level
> [%logger\{36}.%M:%L] - %msg%n
> # Rotate log file
> appender.rolling.type = RollingFile
> appender.rolling.name = LogToRollingFile
> appender.rolling.fileName = logs/{*}{color:#ff8b00}app.log{color}{*}
> appender.rolling.filePattern =
> logs/$${date:-MM}/app-%d\{MM-dd-}-%i.log.gz
> appender.rolling.layout.type = PatternLayout
> appender.rolling.layout.pattern = %d\{-MM-dd HH:mm:ss.SSS} (%t) %-5level
> [%logger\{36}.%M:%L] - %msg%n
> appender.rolling.policies.type = Policies
> appender.rolling.policies.time.type = TimeBasedTriggeringPolicy
> appender.rolling.policies.size.type = SizeBasedTriggeringPolicy
> appender.rolling.policies.size.size=10MB
> appender.rolling.strategy.type = DefaultRolloverStrategy
> appender.rolling.strategy.max = 10
> # Log to console and rolling file
> logger.app.name = *com.application.test*
> logger.app.level = debug
> logger.app.additivity = false
> logger.app.appenderRef.rolling.ref = LogToRollingFile
> logger.app.appenderRef.console.ref = LogToConsole
> rootLogger.level = info
> rootLogger.appenderRef.stdout.ref = LogToConsole
> ___
>
> Please advise.
>
> Regards
> Thanga
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed
[
https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory resolved LOG4J2-3423.
-
Resolution: Fixed
> JAR file containing Log4j configuration isn't closed
>
>
> Key: LOG4J2-3423
> URL: https://issues.apache.org/jira/browse/LOG4J2-3423
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.14.0
> Environment: Windows
>Reporter: Radim Tlusty
>Assignee: Gary D. Gregory
>Priority: Major
> Fix For: 2.17.3
>
>
> If the Log4j configuration file is inside of a JAR file, then the JAR file
> (which is backed by the {{JarURLConnection}} retrieved from
> {{{}URL.openConnection{}}}) isn't closed.
> This causes problems on Tomcat running on Windows during undeploying of an
> application, because the opened JAR file can't be deleted.
> The problem was introduced during implementation of LOG4J2-2901 (version
> 2.14.0), where the {{URL.openStream}} was replaced by {{URL.openConnection}}
> in the class {{{}org.apache.logging.log4j.core.config.ConfigurationSource{}}}.
> The proposed solution (https://github.com/apache/logging-log4j2/pull/780) is
> to use the {{URL.openConnection}} only when needed (~ configuration URL has
> HTTPS protocol), otherwise similar code as in previous versions (<= 2.13.3)
> would be used.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
