-
1. Re: Catching a CMT Rollback exception, don't want to log it in wildfly 8.1
jaysensharma Nov 18, 2014 11:08 AM (in response to dmouch)Hello,
One option to suppress, will be to use the "filter-spec" configuration something like following inside your WildFly profile :
Example:
<console-handler name="CONSOLE"> <filter-spec value="not(any(match("JBAS014134.*"),match("JBAS014585.*")))"/> <level name="INFO"/> <formatter> <named-formatter name="COLOR-PATTERN"/> </formatter> </console-handler> <periodic-rotating-file-handler name="FILE" autoflush="true"> <filter-spec value="not(any(match("JBAS014134.*"),match("JBAS014585.*")))"/> <formatter> <named-formatter name="PATTERN"/> </formatter> <file relative-to="jboss.server.log.dir" path="server.log"/> <suffix value=".yyyy-MM-dd"/> <append value="true"/> </periodic-rotating-file-handler>
Notice:
<filter-spec value="not(any(match("JBAS014134.*"),match("JBAS014585.*")))"/>
Above filter configuration in the logging subsystem should cause suppressing the Error messages containing the error code JBAS014134 and JBAS014585
-
2. Re: Catching a CMT Rollback exception, don't want to log it in wildfly 8.1
jaikiran Nov 26, 2014 1:11 AM (in response to dmouch)FWIW - there's a JIRA request to make EJB exception logging (which is mandated by spec) configurable [WFLY-4125] javax.ejb.NoSuchEJBException should not print a stacktrace on the server console - JBoss Issue Tracker