SteveMissing (JIRA | 24 Jul 12:00 2014
Picon

[JIRA] (CONSPLUG-44) Logback-Beagle doesn't work in Eclipse 4.3 Kepler

SteveMissing commented on CONSPLUG-44

And it does not work in eclipse 4.4 luna,too.
Some people got resolutions?

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
Jeeva (JIRA | 23 Jul 07:55 2014
Picon

[JIRA] (LOGBACK-998) printstacktrace output differs from logback

Jeeva commented on LOGBACK-998

With logback, entire stacktrace is not logged.

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
Jeeva (JIRA | 23 Jul 07:53 2014
Picon

[JIRA] (LOGBACK-998) printstacktrace output differs from logback

Jeeva commented on LOGBACK-998
      • With e.PrintStackTrace got below exception for the same problem ***

1) Error in custom provider, java.lang.RuntimeException: com.google.inject.ProvisionException: Guice provision errors:

1) Error in custom provider, java.lang.RuntimeException: com.google.inject.ProvisionException: Guice provision errors:

1) Error in custom provider, java.lang.RuntimeException: com.google.inject.ProvisionException: Guice provision errors:

1) Error in custom provider, java.lang.RuntimeException: com.google.inject.ProvisionException: Guice provision errors:

1) Error injecting constructor, javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.RuntimeException: Operation failed with status WAITING]
at net.bubbly.messaging.impl.JmsMessageBus.<init>(JmsMessageBus.java:29)

1 error
at net.bubbly.messaging.impl.JmsMessageBus.class(JmsMessageBus.java:22)
while locating net.bubbly.messaging.impl.JmsMessageBus
while locating net.bubbly.messaging.MessageBus
for parameter 2 at net.bubbly.data.impl.LegacyDataManager.<init>(LegacyDataManager.java:52)

1 error
at net.bubbly.data.impl.LegacyDataManager.class(LegacyDataManager.java:40)
while locating net.bubbly.data.impl.LegacyDataManager
while locating net.bubbly.data.DataManager
for parameter 3 at net.bubbly.notifyman.impl.SmsNotifyManager.<init>(SmsNotifyManager.java:51)

1 error
at net.bubbly.notifyman.impl.SmsNotifyManager.class(SmsNotifyManager.java:46)
while locating net.bubbly.notifyman.impl.SmsNotifyManager
while locating net.bubbly.notifyman.NotifyManager
for parameter 3 at net.bubbly.callcontrol.management.impl.AmiTelephonyManager.<init>(AmiTelephonyManager.java:49)

1 error
at net.bubbly.callcontrol.management.impl.AmiTelephonyManager.class(AmiTelephonyManager.java:35)
while locating net.bubbly.callcontrol.management.impl.AmiTelephonyManager
while locating net.bubbly.callcontrol.management.TelephonyManager

1 error
at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:987)
at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1013)
at net.bubbly.appframework.impl.ApplicationTreeNode.createInstances(ApplicationTreeNode.java:181)
at net.bubbly.appframework.impl.ApplicationTreeNode.<init>(ApplicationTreeNode.java:127)
at net.bubbly.appframework.impl.ApplicationTreeNode.createChildApplication(ApplicationTreeNode.java:154)
at net.bubbly.appframework.impl.Server.createChildApplication(Server.java:169)
at net.bubbly.appframework.impl.Server.<init>(Server.java:71)
at net.bubbly.appframework.impl.Server.main(Server.java:274)
Caused by: java.lang.RuntimeException: com.google.inject.ProvisionException: Guice provision errors:

1) Error in custom provider, java.lang.RuntimeException: com.google.inject.ProvisionException: Guice provision errors:

1) Error in custom provider, java.lang.RuntimeException: com.google.inject.ProvisionException: Guice provision errors:

1) Error in custom provider, java.lang.RuntimeException: com.google.inject.ProvisionException: Guice provision errors:

1) Error injecting constructor, javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.RuntimeException: Operation failed with status WAITING]
at net.bubbly.messaging.impl.JmsMessageBus.<init>(JmsMessageBus.java:29)

1 error
at net.bubbly.messaging.impl.JmsMessageBus.class(JmsMessageBus.java:22)
while locating net.bubbly.messaging.impl.JmsMessageBus
while locating net.bubbly.messaging.MessageBus
for parameter 2 at net.bubbly.data.impl.LegacyDataManager.<init>(LegacyDataManager.java:52)

1 error
at net.bubbly.data.impl.LegacyDataManager.class(LegacyDataManager.java:40)
while locating net.bubbly.data.impl.LegacyDataManager
while locating net.bubbly.data.DataManager
for parameter 3 at net.bubbly.notifyman.impl.SmsNotifyManager.<init>(SmsNotifyManager.java:51)

1 error
at net.bubbly.notifyman.impl.SmsNotifyManager.class(SmsNotifyManager.java:46)
while locating net.bubbly.notifyman.impl.SmsNotifyManager
while locating net.bubbly.notifyman.NotifyManager
for parameter 3 at net.bubbly.callcontrol.management.impl.AmiTelephonyManager.<init>(AmiTelephonyManager.java:49)

1 error
at net.bubbly.appframework.impl.TreeObjectPool$1.get(TreeObjectPool.java:80)
at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:54)
at com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1024)
at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974)
... 7 more
Caused by: com.google.inject.ProvisionException: Guice provision errors:

1) Error in custom provider, java.lang.RuntimeException: com.google.inject.ProvisionException: Guice provision errors:

1) Error in custom provider, java.lang.RuntimeException: com.google.inject.ProvisionException: Guice provision errors:

1) Error in custom provider, java.lang.RuntimeException: com.google.inject.ProvisionException: Guice provision errors:

1) Error injecting constructor, javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.RuntimeException: Operation failed with status WAITING]
at net.bubbly.messaging.impl.JmsMessageBus.<init>(JmsMessageBus.java:29)

1 error
at net.bubbly.messaging.impl.JmsMessageBus.class(JmsMessageBus.java:22)
while locating net.bubbly.messaging.impl.JmsMessageBus
while locating net.bubbly.messaging.MessageBus
for parameter 2 at net.bubbly.data.impl.LegacyDataManager.<init>(LegacyDataManager.java:52)

1 error
at net.bubbly.data.impl.LegacyDataManager.class(LegacyDataManager.java:40)
while locating net.bubbly.data.impl.LegacyDataManager
while locating net.bubbly.data.DataManager
for parameter 3 at net.bubbly.notifyman.impl.SmsNotifyManager.<init>(SmsNotifyManager.java:51)

1 error
at net.bubbly.notifyman.impl.SmsNotifyManager.class(SmsNotifyManager.java:46)
while locating net.bubbly.notifyman.impl.SmsNotifyManager
while locating net.bubbly.notifyman.NotifyManager
for parameter 3 at net.bubbly.callcontrol.management.impl.AmiTelephonyManager.<init>(AmiTelephonyManager.java:49)

1 error
at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52)
at net.bubbly.appframework.impl.TreeObjectPool$1.get(TreeObjectPool.java:67)
... 12 more
Caused by: java.lang.RuntimeException: com.google.inject.ProvisionException: Guice provision errors:

1) Error in custom provider, java.lang.RuntimeException: com.google.inject.ProvisionException: Guice provision errors:

1) Error in custom provider, java.lang.RuntimeException: com.google.inject.ProvisionException: Guice provision errors:

1) Error injecting constructor, javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.RuntimeException: Operation failed with status WAITING]
at net.bubbly.messaging.impl.JmsMessageBus.<init>(JmsMessageBus.java:29)

1 error
at net.bubbly.messaging.impl.JmsMessageBus.class(JmsMessageBus.java:22)
while locating net.bubbly.messaging.impl.JmsMessageBus
while locating net.bubbly.messaging.MessageBus
for parameter 2 at net.bubbly.data.impl.LegacyDataManager.<init>(LegacyDataManager.java:52)

1 error
at net.bubbly.data.impl.LegacyDataManager.class(LegacyDataManager.java:40)
while locating net.bubbly.data.impl.LegacyDataManager
while locating net.bubbly.data.DataManager
for parameter 3 at net.bubbly.notifyman.impl.SmsNotifyManager.<init>(SmsNotifyManager.java:51)

1 error
at net.bubbly.appframework.impl.TreeObjectPool$1.get(TreeObjectPool.java:80)
at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:54)
at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:38)
at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:62)
at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:84)
at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
... 13 more
Caused by: com.google.inject.ProvisionException: Guice provision errors:

1) Error in custom provider, java.lang.RuntimeException: com.google.inject.ProvisionException: Guice provision errors:

1) Error in custom provider, java.lang.RuntimeException: com.google.inject.ProvisionException: Guice provision errors:

1) Error injecting constructor, javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.RuntimeException: Operation failed with status WAITING]
at net.bubbly.messaging.impl.JmsMessageBus.<init>(JmsMessageBus.java:29)

1 error
at net.bubbly.messaging.impl.JmsMessageBus.class(JmsMessageBus.java:22)
while locating net.bubbly.messaging.impl.JmsMessageBus
while locating net.bubbly.messaging.MessageBus
for parameter 2 at net.bubbly.data.impl.LegacyDataManager.<init>(LegacyDataManager.java:52)

1 error
at net.bubbly.data.impl.LegacyDataManager.class(LegacyDataManager.java:40)
while locating net.bubbly.data.impl.LegacyDataManager
while locating net.bubbly.data.DataManager
for parameter 3 at net.bubbly.notifyman.impl.SmsNotifyManager.<init>(SmsNotifyManager.java:51)

1 error
at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52)
at net.bubbly.appframework.impl.TreeObjectPool$1.get(TreeObjectPool.java:67)
... 22 more
Caused by: java.lang.RuntimeException: com.google.inject.ProvisionException: Guice provision errors:

1) Error in custom provider, java.lang.RuntimeException: com.google.inject.ProvisionException: Guice provision errors:

1) Error injecting constructor, javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.RuntimeException: Operation failed with status WAITING]
at net.bubbly.messaging.impl.JmsMessageBus.<init>(JmsMessageBus.java:29)

1 error
at net.bubbly.messaging.impl.JmsMessageBus.class(JmsMessageBus.java:22)
while locating net.bubbly.messaging.impl.JmsMessageBus
while locating net.bubbly.messaging.MessageBus
for parameter 2 at net.bubbly.data.impl.LegacyDataManager.<init>(LegacyDataManager.java:52)

1 error
at net.bubbly.appframework.impl.TreeObjectPool$1.get(TreeObjectPool.java:80)
at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:54)
at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:38)
at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:62)
at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:84)
at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
... 23 more
Caused by: com.google.inject.ProvisionException: Guice provision errors:

1) Error in custom provider, java.lang.RuntimeException: com.google.inject.ProvisionException: Guice provision errors:

1) Error injecting constructor, javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.RuntimeException: Operation failed with status WAITING]
at net.bubbly.messaging.impl.JmsMessageBus.<init>(JmsMessageBus.java:29)

1 error
at net.bubbly.messaging.impl.JmsMessageBus.class(JmsMessageBus.java:22)
while locating net.bubbly.messaging.impl.JmsMessageBus
while locating net.bubbly.messaging.MessageBus
for parameter 2 at net.bubbly.data.impl.LegacyDataManager.<init>(LegacyDataManager.java:52)

1 error
at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52)
at net.bubbly.appframework.impl.TreeObjectPool$1.get(TreeObjectPool.java:67)
... 32 more
Caused by: java.lang.RuntimeException: com.google.inject.ProvisionException: Guice provision errors:

1) Error injecting constructor, javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.RuntimeException: Operation failed with status WAITING]
at net.bubbly.messaging.impl.JmsMessageBus.<init>(JmsMessageBus.java:29)

1 error
at net.bubbly.appframework.impl.TreeObjectPool$1.get(TreeObjectPool.java:80)
at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:54)
at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:38)
at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:62)
at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:84)
at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
... 33 more
Caused by: com.google.inject.ProvisionException: Guice provision errors:

1) Error injecting constructor, javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.RuntimeException: Operation failed with status WAITING]
at net.bubbly.messaging.impl.JmsMessageBus.<init>(JmsMessageBus.java:29)

1 error
at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52)
at net.bubbly.appframework.impl.TreeObjectPool$1.get(TreeObjectPool.java:67)
... 42 more
Caused by: javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.RuntimeException: Operation failed with status WAITING]
at org.jboss.naming.remote.client.ClientUtil.namingException(ClientUtil.java:36)
at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:121)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
at javax.naming.InitialContext.init(InitialContext.java:242)
at javax.naming.InitialContext.<init>(InitialContext.java:216)
at net.bubbly.messaging.impl.JmsMessageBus.<init>(JmsMessageBus.java:38)
at net.bubbly.messaging.impl.JmsMessageBus$$FastClassByGuice$$80fb7f22.newInstance(<generated>)
at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:60)
at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
... 43 more
Caused by: java.lang.RuntimeException: Operation failed with status WAITING
at org.jboss.naming.remote.protocol.IoFutureHelper.get(IoFutureHelper.java:89)
at org.jboss.naming.remote.client.NamingStoreCache.getRemoteNamingStore(NamingStoreCache.java:56)
at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:166)
at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:139)
at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:104)

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
Jeeva (JIRA | 23 Jul 07:53 2014
Picon

[JIRA] (LOGBACK-998) printstacktrace output differs from logback

Jeeva commented on LOGBACK-998
      • With logback using logging statements mentioned in the description, got an exception below... ****

1) Error in custom provider, java.lang.RuntimeException: com.google.inject.ProvisionException: Guice provision errors:

1) Error injecting constructor, javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.RuntimeException: Operation failed with status WAITING]
at net.bubbly.messaging.impl.JmsMessageBus.<init>(JmsMessageBus.java:29)

1 error
at net.bubbly.messaging.impl.JmsMessageBus.class(JmsMessageBus.java:22)
while locating net.bubbly.messaging.impl.JmsMessageBus
while locating net.bubbly.messaging.MessageBus
for parameter 2 at net.bubbly.data.impl.LegacyDataManager.<init>(LegacyDataManager.java:52)

1 error
at net.bubbly.data.impl.LegacyDataManager.class(LegacyDataManager.java:40)
while locating net.bubbly.data.impl.LegacyDataManager
while locating net.bubbly.data.DataManager
for parameter 3 at net.bubbly.notifyman.impl.SmsNotifyManager.<init>(SmsNotifyManager.java:51)

1 error
at net.bubbly.notifyman.impl.SmsNotifyManager.class(SmsNotifyManager.java:46)
while locating net.bubbly.notifyman.impl.SmsNotifyManager
while locating net.bubbly.notifyman.NotifyManager
for parameter 3 at net.bubbly.callcontrol.management.impl.AmiTelephonyManager.<init>(AmiTelephonyManager.java:49)

1 error
at net.bubbly.callcontrol.management.impl.AmiTelephonyManager.class(AmiTelephonyManager.java:35)
while locating net.bubbly.callcontrol.management.impl.AmiTelephonyManager
while locating net.bubbly.callcontrol.management.TelephonyManager

1 error

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 (JIRA | 23 Jul 07:41 2014
Picon

[JIRA] (LOGBACK-998) printstacktrace output differs from logback

Tony Trinh commented on LOGBACK-998

I don't understand. What outputs are you comparing? Please provide an example.

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
Jeeva (JIRA | 23 Jul 06:35 2014
Picon

[JIRA] (LOGBACK-998) printstacktrace output differs from logback

Jeeva created LOGBACK-998
Issue Type: Bug
Affects Versions: 1.1.2
Assignee: Logback dev list
Components: logback-classic
Created: 23/Jul/14 6:33 AM
Description:

Found very less information when logging the exception using logback.
Used below statements to log exception.

logger.error("some message",e.toString(),e);
logger.error("some message"+e.getMessage());

Project: logback
Labels: printstacktrace
Priority: Critical
Reporter: Jeeva
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
LEONID ILYEVSKY (JIRA | 23 Jul 00:46 2014
Picon

[JIRA] (LOGBACK-205) rotate at an absolute time every day

I found the simple fix, it works now. The fix is in DefaultTimeBasedFileNamingAndTriggeringPolicy.java.

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
LEONID ILYEVSKY (JIRA | 22 Jul 22:27 2014
Picon

[JIRA] (LOGBACK-205) rotate at an absolute time every day

Guys, I need some help. My second enhancement does not work : it does not use my special time zone for generating the file name. What is the best way of fixing it? I need to set that time zone on the converter responsible for the file name.
Example: today is July 22nd in New York, I am using Tokyo time zone and the roll time 03:00:00 with day shift +1. The rollover happens at proper time, but the old log is renamed using July 22nd (as if using default time zone), instead of expected July 23rd.

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
smaudet (JIRA | 22 Jul 12:24 2014
Picon

[JIRA] (LOGBACK-997) No way to set "N"

Issue Type: Bug
Assignee: Logback dev list
Created: 22/Jul/14 12:22 PM
Description:

In the Logback manual, it is said in the automatic reconfiguration page: http://logback.qos.ch/manual/configuration.html#autoScan

That the configuration will be reloaded every "N" times, and that this is done with a default value of 16.

Looking at the source code for ReconfigureOnChangeFilter, there is no way to set this "N", although the documentation claims otherwise.

This means this functionality is useless for testing, which is my use case, as I must generate a bunch of bogus calls in order to get the filter to trigger the reload.

For testing, there should be a way to turn off this rate limiting reloading entirely, if it is useless and inappropriate, as in my case.

Environment:

Java 7, Tomcat

Project: logback
Priority: Major
Reporter: smaudet
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
LEONID ILYEVSKY (JIRA | 21 Jul 21:04 2014
Picon

[JIRA] (LOGBACK-205) rotate at an absolute time every day

I realized that the number of days to shift will be very useful, even for the daily rollover, so I added it, and submitted to my branch. It should be included in the pull. the new parameter is called "daysOffset", integer type (can be negative).
For daily rollover, this is how I use it myself. If daysOffset is zero (default), then the log before rollTime belongs to yesterday, and today starts after rollover. If I set it to 1, then the log before rollTime is today, and after rollTime it is tomorrow.

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
watchzerg (JIRA | 19 Jul 04:57 2014
Picon

[JIRA] (LOGBACK-996) CyclicBufferTracker.setMaxNumberOfBuffers() was removed but no alternative option found.

Issue Type: Bug
Affects Versions: 1.1.2
Assignee: Logback dev list
Components: logback-core
Created: 19/Jul/14 4:55 AM
Description:

<appender name="ALARM-APPENDER" class="ch.qos.logback.classic.net.SMTPAppender">
...
<cyclicBufferTracker class="ch.qos.logback.core.spi.CyclicBufferTracker">
<maxNumberOfBuffers>256</maxNumberOfBuffers>
</cyclicBufferTracker>
...
</appender>

Configured like above, bug got error messages:
10:00:48,171 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter <at> 82:24 - no applicable action for [maxNumberOfBuffers], current ElementPath is [[configuration][appender][cyclicBufferTracker][maxNumberOfBuffers]]

After checking the source code, I know CyclicBufferTracker has refactored from a interface to a Class.

But after "setMaxNumberOfBuffers" method was removed:
https://github.com/qos-ch/logback/commit/773193a09922ab2a1dd70e4978be8cdf4e050f6e
There is no place to config "maxNumberOfBuffers" attribute.

Actually, the only "maxNumberOfBuffers" String can be found in github repository, is in the logback user manual:
https://github.com/qos-ch/logback/search?q=maxNumberOfBuffers
http://logback.qos.ch/manual/appenders.html#bufferManagement
http://logback.qos.ch/recipes/emailPerTransaction.html

Project: logback
Labels: smtpappender CyclicBufferTracker maxNumberOfBuffers
Priority: Major
Reporter: watchzerg
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

Gmane