[jboss-jira] [JBoss JIRA] Updated: (JBAS-9446) Setting up of application specific logging context still does not work

[Leonid Kosmylev (JIRA)]

     [ https://issues.jboss.org/browse/JBAS-9446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leonid Kosmylev updated JBAS-9446:
----------------------------------

        Description: 
I have cloned JBAS-9407 (https://issues.jboss.org/browse/JBAS-9407) because the fix does not work.

Yes, the "java.lang.RuntimeException: Error configuring property:" is fixed.

But the functionality still does not work. The logging goes to server.log anyway. Reason: the proposed workaround was used as a fix. The workaround is not complete.

That mode="On Demand" must be removed so that the configuration looks like

{code:xml}
<!-- Workaround for JBoss Logging bug http://community.jboss.org/message/587287#587287 -->
<bean name="JBossLogManagerContextSelectorService" class="org.jboss.logmanager.ClassLoaderLogContextSelector"/>

   <bean name="OnDemandJBossLogManagerContextSelectorService" class="org.jboss.logmanager.LogContextSelectorService">
      <property name="selector">
         <inject bean="JBossLogManagerClassLoaderContextSelectorService"/>
      </property>
   </bean>
{code}


But this is not enough. There is also an NPE when the application is undeployed.
{code}
14:33:50,546 ERROR [org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer] Error during undeploy: Logging:REGISTRATION:MyAppLogContext:Anonymous-5: java.lang.NullPointerException
	at org.jboss.logging.metadata.GetClassLoaderBeanMetaData.setClassLoader(GetClassLoaderBeanMetaData.java:52)
	at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.undeploy(BeanMetaDataDeployer.java:237)
	at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.undeploy(BeanMetaDataDeployer.java:58)
{code}

Unfortunately there is no workaround.

I have created a patch that fixes this NPE and correctly (or so I think) configures per-application logging. This time it is really lazy.

  was:
I have cloned JBAS-9407 (https://issues.jboss.org/browse/JBAS-9407) because the fix does not work.

Yes, the "java.lang.RuntimeException: Error configuring property:" is fixed.

But the functionality still does not work. The logging goes to server.log anyway. Reason: the proposed workaround was used as a fix. The workaround is not complete.

That mode="On Demand" must be removed so that the configuration looks like

{code:xml}
<!-- Workaround for JBoss Logging bug http://community.jboss.org/message/587287#587287 -->
<bean name="JBossLogManagerContextSelectorService" class="org.jboss.logmanager.ClassLoaderLogContextSelector"/>

   <bean name="OnDemandJBossLogManagerContextSelectorService" class="org.jboss.logmanager.LogContextSelectorService">
      <property name="selector">
         <inject bean="JBossLogManagerClassLoaderContextSelectorService"/>
      </property>
   </bean>
{code}


But this is not enough. There is also an NPE when the application is undeployed.
{code}
14:33:50,546 ERROR [org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer] Error during undeploy: Logging:REGISTRATION:MyAppLogContext:Anonymous-5: java.lang.NullPointerException
	at org.jboss.logging.metadata.GetClassLoaderBeanMetaData.setClassLoader(GetClassLoaderBeanMetaData.java:52)
	at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.undeploy(BeanMetaDataDeployer.java:237)
	at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.undeploy(BeanMetaDataDeployer.java:58)
{code}

Unfortunately there is no workaround.

    Forum Reference: http://community.jboss.org/message/587287#587287, http://community.jboss.org/message/584720#584720  (was: http://community.jboss.org/message/587287#587287, http://community.jboss.org/message/584720#584720)


> Setting up of application specific logging context still does not work
> ----------------------------------------------------------------------
>
>                 Key: JBAS-9446
>                 URL: https://issues.jboss.org/browse/JBAS-9446
>             Project: Legacy JBoss Application Server 6 
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>    Affects Versions: 6.1.0
>         Environment: JBoss AS 6.1.0.Final
>            Reporter: Leonid Kosmylev
>            Assignee: jaikiran pai
>         Attachments: patch_JBAS-9446.zip
>
>
> I have cloned JBAS-9407 (https://issues.jboss.org/browse/JBAS-9407) because the fix does not work.
> Yes, the "java.lang.RuntimeException: Error configuring property:" is fixed.
> But the functionality still does not work. The logging goes to server.log anyway. Reason: the proposed workaround was used as a fix. The workaround is not complete.
> That mode="On Demand" must be removed so that the configuration looks like
> {code:xml}
> <!-- Workaround for JBoss Logging bug http://community.jboss.org/message/587287#587287 -->
> <bean name="JBossLogManagerContextSelectorService" class="org.jboss.logmanager.ClassLoaderLogContextSelector"/>
>    <bean name="OnDemandJBossLogManagerContextSelectorService" class="org.jboss.logmanager.LogContextSelectorService">
>       <property name="selector">
>          <inject bean="JBossLogManagerClassLoaderContextSelectorService"/>
>       </property>
>    </bean>
> {code}
> But this is not enough. There is also an NPE when the application is undeployed.
> {code}
> 14:33:50,546 ERROR [org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer] Error during undeploy: Logging:REGISTRATION:MyAppLogContext:Anonymous-5: java.lang.NullPointerException
> 	at org.jboss.logging.metadata.GetClassLoaderBeanMetaData.setClassLoader(GetClassLoaderBeanMetaData.java:52)
> 	at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.undeploy(BeanMetaDataDeployer.java:237)
> 	at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.undeploy(BeanMetaDataDeployer.java:58)
> {code}
> Unfortunately there is no workaround.
> I have created a patch that fixes this NPE and correctly (or so I think) configures per-application logging. This time it is really lazy.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira