You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alberto (JIRA)" <ji...@apache.org> on 2016/10/24 16:45:58 UTC
[jira] [Updated] (QPID-7468) Upgrade logback to 1.1.7
[ https://issues.apache.org/jira/browse/QPID-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alberto updated QPID-7468:
--------------------------
Description:
The current version used in qpid-broker 6.0.4 for logback is 1.1.3. With the version 1.1.7 logback broke backwards compatibility in StatusManager interface (ch.qos.logback.core.status.StatusManager).
After this change, BrokerFileLoggerImpl is failing to add the `BrokerFileLoggerStatusListener` to the loggerContext due to binary incompatibility (See line 210 of BrokerFileLoggerImpl for more info).
{code:java}
@Override
protected Appender<ILoggingEvent> createAppenderInstance(Context loggerContext)
{
SystemConfig<?> systemConfig = (SystemConfig<?>)getParent(Broker.class).getParent(SystemConfig.class);
_logbackStatusListener = new BrokerFileLoggerStatusListener(this, systemConfig);
_statusManager = loggerContext.getStatusManager();
_statusManager.add(_logbackStatusListener);
final RollingFileAppender<ILoggingEvent> appender = new RollingFileAppender<>();
AppenderUtils.configureRollingFileAppender(this, loggerContext, appender);
return appender;
}
{code}
We've noticed this after update spring boot to the latest version 1.4.1.Release which includes logback 1.1.7.
As a workaround, you can still downgrade your version of logback in your project to 1.1.3 but it would be nice to have it upgraded
was:
The current version used in qpid-broker 6.0.4 for logback is 1.1.3. With the version 1.1.7 logback broke backwards compatibility in StatusManager interface (ch.qos.logback.core.status.StatusManager).
After this change, BrokerFileLoggerImpl is failing to add the `BrokerFileLoggerStatusListener` to the loggerContext due to binary incompatibility (See line 210 of BrokerFileLoggerImpl for more info).
```java
@Override
protected Appender<ILoggingEvent> createAppenderInstance(Context loggerContext)
{
SystemConfig<?> systemConfig = (SystemConfig<?>)getParent(Broker.class).getParent(SystemConfig.class);
_logbackStatusListener = new BrokerFileLoggerStatusListener(this, systemConfig);
_statusManager = loggerContext.getStatusManager();
_statusManager.add(_logbackStatusListener);
final RollingFileAppender<ILoggingEvent> appender = new RollingFileAppender<>();
AppenderUtils.configureRollingFileAppender(this, loggerContext, appender);
return appender;
}
```
We've noticed this after update spring boot to the latest version 1.4.1.Release which includes logback 1.1.7.
As a workaround, you can still downgrade your version of logback in your project to 1.1.3 but it would be nice to have it upgraded
> Upgrade logback to 1.1.7
> ------------------------
>
> Key: QPID-7468
> URL: https://issues.apache.org/jira/browse/QPID-7468
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: qpid-java-6.0.4
> Reporter: Alberto
>
> The current version used in qpid-broker 6.0.4 for logback is 1.1.3. With the version 1.1.7 logback broke backwards compatibility in StatusManager interface (ch.qos.logback.core.status.StatusManager).
> After this change, BrokerFileLoggerImpl is failing to add the `BrokerFileLoggerStatusListener` to the loggerContext due to binary incompatibility (See line 210 of BrokerFileLoggerImpl for more info).
> {code:java}
> @Override
> protected Appender<ILoggingEvent> createAppenderInstance(Context loggerContext)
> {
> SystemConfig<?> systemConfig = (SystemConfig<?>)getParent(Broker.class).getParent(SystemConfig.class);
> _logbackStatusListener = new BrokerFileLoggerStatusListener(this, systemConfig);
> _statusManager = loggerContext.getStatusManager();
> _statusManager.add(_logbackStatusListener);
> final RollingFileAppender<ILoggingEvent> appender = new RollingFileAppender<>();
> AppenderUtils.configureRollingFileAppender(this, loggerContext, appender);
> return appender;
> }
> {code}
> We've noticed this after update spring boot to the latest version 1.4.1.Release which includes logback 1.1.7.
> As a workaround, you can still downgrade your version of logback in your project to 1.1.3 but it would be nice to have it upgraded
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org