[jboss-jira] [JBoss JIRA] (JBLOGGING-70) JBoss LogManager detection is still incorrect
[
https://issues.jboss.org/browse/JBLOGGING-70?page=com.atlassian.jira.plug...
]
Aaron Douglas commented on JBLOGGING-70:
----------------------------------------
I'm stilling seeing this issue with EAP 5 + JBoss Logging 3.1.0.CR1:
{code}Caused by: java.lang.NoSuchMethodError:
org.jboss.logmanager.LogContext.getAttachment(Ljava/lang/String;Lorg/jboss/logmanager/Logger$AttachmentKey;)Ljava/lang/Object;
at
org.jboss.logging.JBossLogManagerProvider.doGetLogger(JBossLogManagerProvider.java:52)
at org.jboss.logging.JBossLogManagerProvider.getLogger(JBossLogManagerProvider.java:47)
at org.jboss.logging.LoggerProviders.find(LoggerProviders.java:37)
at org.jboss.logging.LoggerProviders.<clinit>(LoggerProviders.java:32)
at org.jboss.logging.Logger.getLogger(Logger.java:2163)
at org.jboss.logging.Logger.getMessageLogger(Logger.java:2259)
at org.jboss.logging.Logger.getMessageLogger(Logger.java:2214)
at org.infinispan.util.logging.LogFactory.getLog(LogFactory.java:37)
at
org.hibernate.cache.infinispan.InfinispanRegionFactory.<clinit>(InfinispanRegionFactory.java:51)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.hibernate.cfg.SettingsFactory.createRegionFactory(SettingsFactory.java:409)
at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:280)
at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2863)
at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2859)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1870)
at
org.springframework.orm.hibernate3.LocalSessionFactoryBean.newSessionFactory(LocalSessionFactoryBean.java:860)
at
org.springframework.orm.hibernate3.LocalSessionFactoryBean.buildSessionFactory(LocalSessionFactoryBean.java:779)
at
org.springframework.orm.hibernate3.AbstractSessionFactoryBean.afterPropertiesSet(AbstractSessionFactoryBean.java:211)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1504)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1442)
... 120 more
{code}
JBoss LogManager detection is still incorrect
---------------------------------------------
Key: JBLOGGING-70
URL: https://issues.jboss.org/browse/JBLOGGING-70
Project: JBoss Logging
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.0.0.GA
Reporter: David Lloyd
Assignee: David Lloyd
Fix For: 3.0.1.GA, 3.1.0.Beta1
The detection in LoggerProviders is insufficient because the failure can simply be
deferred, resulting in exceptions like this:
{noformat}
java.lang.NoSuchMethodError:
org.jboss.logmanager.LogContext.getAttachment(Ljava/lang/String;Lorg/jboss/logmanager/Logger$AttachmentKey;)Ljava/lang/Object;
at
org.jboss.logging.JBossLogManagerProvider.doGetLogger(JBossLogManagerProvider.java:52)
at org.jboss.logging.JBossLogManagerProvider.getLogger(JBossLogManagerProvider.java:47)
at org.jboss.logging.Logger.getLogger(Logger.java:2164)
at org.jboss.logging.Logger.getMessageLogger(Logger.java:2263)
at org.jboss.logging.Logger.getMessageLogger(Logger.java:2215)
at org.infinispan.util.logging.LogFactory.getLog(LogFactory.java:41)
[...]
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira