Sandeep Kumar (JIRA | 19 Apr 02:00 2015
Picon

[JIRA] (LOGBACK-992) Rolling File Appender creates .tmp files but never deletes them

Sandeep Kumar commented on LOGBACK-992

Seeing exactly the same issue. Attaching the log below.

00:00:12,100 |-INFO in c.q.l.co.rolling.helper.RenameUtil - Renaming file [logger.log] to [logger.log66868990791295.tmp]
00:00:12,113 |-INFO in ch.qos.logback.core.rolling.helper.SizeAndTimeBasedArchiveRemover <at> 3e3345ef - first clean up after appender initialization
00:00:12,113 |-INFO in ch.qos.logback.core.rolling.helper.SizeAndTimeBasedArchiveRemover <at> 3e3345ef - periodsElapsed = 64
00:00:12,113 |-INFO in ch.qos.logback.core.rolling.helper.Compressor - ZIP compressing [logger.log66868990791295.tmp] as [logger-20150418-0.log.zip]
00:00:12,131 |-INFO in c.q.l.co.rolling.helper.RenameUtil - Renaming file [logger.log] to [logger.log66869021240585.tmp]
00:00:12,133 |-INFO in ch.qos.logback.core.rolling.helper.SizeAndTimeBasedArchiveRemover <at> 7407cec8 - first clean up after appender initialization
00:00:12,133 |-INFO in ch.qos.logback.core.rolling.helper.SizeAndTimeBasedArchiveRemover <at> 7407cec8 - periodsElapsed = 64
00:00:12,134 |-WARN in ch.qos.logback.core.rolling.helper.Compressor - The target compressed file named [logger-20150418-0.log.zip] exist already.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Daan (JIRA | 16 Apr 03:55 2015
Picon

[JIRA] (LOGBACK-1064) wrong log filename

Daan commented on LOGBACK-1064

oops... Change to normal today, but the filename of yesterday is still wrong.

host:expydev

-rw-r----- 1 dev_expy_web app 966586 4月 16 09:49 status-expydev.log -rw-r----- 1 dev_expy_web app 81401 4月 10 00:00 status-expydev.log.2015-04-09.gz -rw-r----- 1 dev_expy_web app 190061 4月 14 10:01 status-expydev.log.2015-04-10.gz -rw-r----- 1 dev_expy_web app 240220 4月 15 00:00 status-expydev.log.2015-04-14.gz -rw-r----- 1 dev_expy_web app 4881417 4月 15 23:59 status-expydev.log51278328382594821.tmp

host:expyweb1

-rw-r----- 1 expy_biz app 271777 4月 16 09:49 status-expyweb1.log -rw-r----- 1 expy_biz app 123 4月 15 06:00 status-expyweb1.log1638971483444302.tmp -rw-r----- 1 expy_biz app 1336126 4月 15 23:59 status-expyweb1.log1639533568312638.tmp -rw-r----- 1 expy_biz app 52134 4月 15 00:00 status-expyweb1.log.2015-04-14.gz
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Daan (JIRA | 15 Apr 07:57 2015
Picon

[JIRA] (LOGBACK-1064) wrong log filename

Daan created LOGBACK-1064
Issue Type: Bug
Affects Versions: 1.1.2
Assignee: Logback dev list
Components: logback-classic
Created: 15/Apr/15 7:57 AM
Description:

Expect filename: "status-expydev.log", but there is "status-expydev.log51278328382594821.tmp"

-rw-r----- 1 dev_expy_web app 81401 4月 10 00:00 status-expydev.log.2015-04-09.gz -rw-r----- 1 dev_expy_web app 190061 4月 14 10:01 status-expydev.log.2015-04-10.gz -rw-r----- 1 dev_expy_web app 240220 4月 15 00:00 status-expydev.log.2015-04-14.gz -rw-r----- 1 dev_expy_web app 2149718 4月 15 13:42 status-expydev.log51278328382594821.tmp

On another server, there are two files end with "tmp"

-rw-r----- 1 expy_biz app 123 4月 15 06:00 status-expyweb1.log1638971483444302.tmp -rw-r----- 1 expy_biz app 561421 4月 15 13:49 status-expyweb1.log1639533568312638.tmp -rw-r----- 1 expy_biz app 52134 4月 15 00:00 status-expyweb1.log.2015-04-14.gz

Why?

pom.xml
<dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> <version>1.7.7</version> </dependency> <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> <version>1.1.2</version> </dependency>
logback.xml
<configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <!-- encoders are assigned the type ch.qos.logback.classic.encoder.PatternLayoutEncoder by default --> <encoder> <pattern>%d{HH:mm:ss} [%thread] \(%file:%line\) - %msg%n</pattern> </encoder> </appender> <appender name="SIFT" class="ch.qos.logback.classic.sift.SiftingAppender"> <!-- in the absence of the class attribute, it is assumed that the desired discriminator type is ch.qos.logback.classic.sift.MDCBasedDiscriminator --> <sift> <appender name="FILE-${hostname}" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>/${USER}/log/status/status-${HOSTNAME}.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <!-- daily rollover --> <fileNamePattern>/${USER}/log/status/status-${HOSTNAME}.log.%d{yyyy-MM-dd}.gz </fileNamePattern> <!-- keep 30 days' worth of history --> <maxHistory>30</maxHistory> </rollingPolicy> <encoder> <pattern>%d{HH:mm:ss} [%thread] - %msg%n</pattern> </encoder> </appender> </sift> </appender> <root level="info"> <appender-ref ref="SIFT" /> </root> </configuration>
Environment:

SUSE Linux Enterprise Server 11 (x86_64)
WebLogic Server version: 10.3.6.0
JDK 1.6.0_32

Project: logback
Labels: filename
Priority: Major
Reporter: Daan
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Tony Trinh | 15 Apr 07:18 2015
Picon

[qos-ch/logback] 467ecc: Fixed timing issue in JettyBasicTest

  Branch: refs/heads/master
  Home:   https://github.com/qos-ch/logback
  Commit: 467ecc7212e903608f56f34a69cc821794c9a3cc
      https://github.com/qos-ch/logback/commit/467ecc7212e903608f56f34a69cc821794c9a3cc
  Author: Alex Panchenko <alex.panchenko@...>
  Date:   2015-04-13 (Mon, 13 Apr 2015)

  Changed paths:
    M logback-access/src/test/java/ch/qos/logback/access/jetty/JettyBasicTest.java
    M logback-access/src/test/java/ch/qos/logback/access/testUtil/NotifyingListAppender.java

  Log Message:
  -----------
  Fixed timing issue in JettyBasicTest

  Commit: d46efd0ebd856924a51b9638cc374687c6f438c8
      https://github.com/qos-ch/logback/commit/d46efd0ebd856924a51b9638cc374687c6f438c8
  Author: Tony Trinh <tony19@...>
  Date:   2015-04-15 (Wed, 15 Apr 2015)

  Changed paths:
    M logback-access/src/test/java/ch/qos/logback/access/jetty/JettyBasicTest.java
    M logback-access/src/test/java/ch/qos/logback/access/testUtil/NotifyingListAppender.java

  Log Message:
  -----------
  Merge pull request #253 from panchenko/jetty-test-timing

Fixed timing issue in JettyBasicTest

Compare: https://github.com/qos-ch/logback/compare/42d1b1cfab40...d46efd0ebd85
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Tony Trinh | 15 Apr 07:18 2015
Picon

[qos-ch/logback] 3d5cf2: Optimization: use Collections.emptyMap() in Loggin...

  Branch: refs/heads/master
  Home:   https://github.com/qos-ch/logback
  Commit: 3d5cf2e0eb4f8d6cdd9ff9b646af5c870c960ba4
      https://github.com/qos-ch/logback/commit/3d5cf2e0eb4f8d6cdd9ff9b646af5c870c960ba4
  Author: Alex Panchenko <alex.panchenko@...>
  Date:   2015-04-13 (Mon, 13 Apr 2015)

  Changed paths:
    M logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggingEvent.java

  Log Message:
  -----------
  Optimization: use Collections.emptyMap() in LoggingEvent

  Commit: 42d1b1cfab40ee1f1303aa34bf0b62b81f49d40c
      https://github.com/qos-ch/logback/commit/42d1b1cfab40ee1f1303aa34bf0b62b81f49d40c
  Author: Tony Trinh <tony19@...>
  Date:   2015-04-15 (Wed, 15 Apr 2015)

  Changed paths:
    M logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggingEvent.java

  Log Message:
  -----------
  Merge pull request #252 from panchenko/emptyMap

Optimization: use Collections.emptyMap() in LoggingEvent

Compare: https://github.com/qos-ch/logback/compare/985257ffc78f...42d1b1cfab40
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Sergio Pintos | 13 Apr 17:17 2015

Setting the logger level through JMX not working (duplicated context)

Hi,

While setting the logger level through the JConsole (via jmx), the JConsole applies the operation successfully but nothing happens on the actual logger implementation.

Apparently, there are two LoggerContext instances on the classloader. I don't know if this is normal or not. I'm debugging logack and I'm seeing that the Logger's object instance the JConsole is using is different than the instance used by my application.

I have some screenshots so you can get a better understanding  of this:

This is while setting the logger lvl through the JConsole:


This is while trying to log from my application:

You can also see the logger's context on these images.

The id's that eclipse is showing are different on each case, thus we have two object instances of the Logger and Logger Context.

I really appreciate if you guys could help me out since I've been working on this several days and I'm stuck.

Thanks,
Sergio.


 
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Pavel (JIRA | 10 Apr 10:09 2015
Picon

[JIRA] (LOGBACK-1061) jvm process not exiting when using logback 1.0.11+

Pavel commented on LOGBACK-1061

I think the problem is gone after using <shutdownHook/> (loggingContext.stop most probably would work as well). I didn't have any AsyncAppenders but obviously something still would not finish unless logging context is gracefully closed

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Tony Trinh | 9 Apr 04:01 2015
Picon

[qos-ch/logback] 667fa0: fixes viewAsGroovy Link for configurations with st...

  Branch: refs/heads/master
  Home:   https://github.com/qos-ch/logback
  Commit: 667fa0160dfae08c4d73601103f1d2c3bac82755
      https://github.com/qos-ch/logback/commit/667fa0160dfae08c4d73601103f1d2c3bac82755
  Author: Klaus Bayrhammer <bayrhammer.klaus@...>
  Date:   2015-04-08 (Wed, 08 Apr 2015)

  Changed paths:
    M logback-site/src/site/pages/js/dsl.js

  Log Message:
  -----------
  fixes viewAsGroovy Link for configurations with styling

* modifies ignore-regex in order to ignore <span> tags correctly

  Commit: 985257ffc78f0c0076792e10f4fcc858c264ef75
      https://github.com/qos-ch/logback/commit/985257ffc78f0c0076792e10f4fcc858c264ef75
  Author: Tony Trinh <tony19@...>
  Date:   2015-04-08 (Wed, 08 Apr 2015)

  Changed paths:
    M logback-site/src/site/pages/js/dsl.js

  Log Message:
  -----------
  Merge pull request #251 from klausbayrhammer/fixViewAsGroovyLink

fixes viewAsGroovy Link for configurations with styling

Compare: https://github.com/qos-ch/logback/compare/efa0cafa97c5...985257ffc78f
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Heiko Kundlacz (JIRA | 8 Apr 11:05 2015
Picon

[JIRA] (LOGBACK-880) AccessControlException when logback tries to execute PackagingDataCalculator.populateFrames(..)

We also have the problem that in our application server for every startup we get this exception output. For us it is not possible to change the java policy file. Any news on this?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Travis CI | 8 Apr 09:57 2015

Fixed: qos-ch/logback#127 (master - efa0caf)

qos-ch / logback (master)
Build #127 was fixed.
1 minute and 48 seconds
Tony Trinh efa0caf Changeset →
  Fix unit test errors related to missing packaging data

The following unit tests were failing because they were expecting the
logger context to have package data enabled by default, but the default
had been changed to false in 8141f88edb95567c2b42bbc73aa81e9eeb399169.

* ExtendedThrowableProxyConverterTest.integration
* RootCauseFirstThrowableProxyConverterTest.integration

This patch explicitly enables packaging data for the test's logger context.

Travis CI supports Rails Girls Summer of Code 2015

Please join us in helping to get more women into Open Source. Read more ...

Want to know about upcoming build environment updates?

Would you like to stay up-to-date with the upcoming Travis CI build environment updates? We set up a mailing list for you! Sign up here.

Would you like to test your private code?

Travis Pro could be your new best friend!

_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Tony Trinh | 8 Apr 09:54 2015
Picon

[qos-ch/logback] efa0ca: Fix unit test errors related to missing packaging ...

  Branch: refs/heads/master
  Home:   https://github.com/qos-ch/logback
  Commit: efa0cafa97c5615780d1048f2fcf1f95da01d57a
      https://github.com/qos-ch/logback/commit/efa0cafa97c5615780d1048f2fcf1f95da01d57a
  Author: Tony Trinh <tony19@...>
  Date:   2015-04-08 (Wed, 08 Apr 2015)

  Changed paths:
    M logback-classic/src/test/java/ch/qos/logback/classic/pattern/ExtendedThrowableProxyConverterTest.java
    M logback-classic/src/test/java/ch/qos/logback/classic/pattern/RootCauseFirstThrowableProxyConverterTest.java

  Log Message:
  -----------
  Fix unit test errors related to missing packaging data

The following unit tests were failing because they were expecting the
logger context to have package data enabled by default, but the default
had been changed to false in 8141f88edb95567c2b42bbc73aa81e9eeb399169.

 * ExtendedThrowableProxyConverterTest.integration
 * RootCauseFirstThrowableProxyConverterTest.integration

This patch explicitly enables packaging data for the test's logger context.

_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev

Gmane