[JBoss JIRA] Created: (JBAS-4413) Incorrect behaviour in TCLFilter
by Poyan (JIRA)
Incorrect behaviour in TCLFilter
--------------------------------
Key: JBAS-4413
URL: http://jira.jboss.com/jira/browse/JBAS-4413
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Logging
Affects Versions: JBossAS-4.0.5.GA
Reporter: Poyan
Assigned To: Scott M Stark
Just one TCLFilter can be added to an appender, decide method return either ACCEPT or DENY.
Should return NEUTRAL is some case.
public int decide(LoggingEvent event)
{
int ok = Filter.DENY;
if( acceptOnMatch == true )
{
ok = Filter.DENY;
if( isMatchingTCL() ){
ok = Filter.ACCEPT;
}
}
else
{
ok = Filter.ACCEPT; // CHANGING THIS ROW TO ok = Filter.NEUTRAL; should do that you check the other filters to.
if( isMatchingTCL() )
ok = Filter.DENY;
}
return ok;
}
Log4j.xml:
<appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p [%t] %c - %m%n"/>
</layout>
<filter class="org.jboss.logging.filter.TCLFilter">
<param name="AcceptOnMatch" value="false"/>
<param name="DeployURL" value="jboss-common-client.jarpoyan"/>
</filter>
<filter class="org.jboss.logging.filter.TCLFilter">
<param name="AcceptOnMatch" value="false"/>
<param name="DeployURL" value="dnsns.jarpoyan"/>
</filter>
</appender>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (EJBTHREE-1701) getTimerService() can no longer be called in @Service start()
by Matt C (JIRA)
getTimerService() can no longer be called in @Service start()
-------------------------------------------------------------
Key: EJBTHREE-1701
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1701
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: trunk
Reporter: Matt C
Calling getTimerService() is no longer allowed from the lifecycle methods of @Service.
Exception java.lang.IllegalStateException: getTimerService() not allowed during injection (EJB3 4.5.2).
This occurs in the start() method of a @Service bean. The effect is to disallow setup of application-wide timers.
This action is erroneously disallowed based on Table 2 in the EJB3 specification, section 4.5.2 (IMHO).
Service lifecycle methods are not dependency injection methods, furthermore @Service beans are outside of the EJB3 specification.
Lifecycle methods of a service should probably be considered business methods, not DI in the context of Table 2. They are in the @Management business interface.
There is no workaround yet for this backwards incompatible change which breaks apps that set up application-wide timers from Services.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month