How to hide [STDERR] caused by ActiveBPEL?

[cmastrantono]

Hi guys...

I have several hours fighting with this issue, so I decided to post it here to see if someone had the same problem, or could help me to fix it.

At the moment of starting up the server, ActiveBPEL throws several lines to the output, like this one.

2010-11-09 11:46:26,491 ERROR [STDERR] 09-nov-2010 11:46:26 org.activebpel.rt.axis.bpel.web.AeProcessEngineServlet$AeTomcatLogger logInfo

INFO: [someStuff.bpr] Finished ActiveBpel deployment.

I want to hide this kind of output, but just for ActiveBPEL only.

I tried to put a "category" tag inside jboss-log4j.xml but if the "name" attribute of the category is "STDERR", all of the STDERR are hidden in the standar output. And I tried also to change the "name" attribute to "org.activebpel" for example, with no success.

Any suggestions?

Best regards.

Cristian

I have several hours fighting with this issue, so I decided to post it here to see if someone had the same problem, or could help me to fix it.

At the moment of starting up the server, ActiveBPEL throws several lines to the output, like this one.

2010-11-09 11:46:26,491 ERROR [STDERR] 09-nov-2010 11:46:26 org.activebpel.rt.axis.bpel.web.AeProcessEngineServlet$AeTomcatLogger logInfo

INFO: [someStuff.bpr] Finished ActiveBpel deployment.

I want to hide this kind of output, but just for ActiveBPEL only.

I tried to put a "category" tag inside jboss-log4j.xml but if the "name" attribute of the category is "STDERR", all of the STDERR are hidden in the standar output. And I tried also to change the "name" attribute to "org.activebpel" for example, with no success.

Any suggestions?

Best regards.

Cristian

[wdfink]

This is the standard behaviour of JBoss to catch STDERR and route it to the logfile.

I suppose you have to write a log4j output filter to suppress exact this.

See the log4j documentation for this http://logging.apache.org/log4j/1.2/manual.htmlhttp://logging.apache.org/log4j/1.2/manual.html

[cmastrantono]

I think I already did it...

In the log4j.properties file I wrote: log4j.logger.org.activebpel=FATAL

That's a filter for printing only messages of level FATAL or above in the package org.activebpel, right?

By the way, thank you for your answer... I'll keep looking for this thing that is driving me crazy.

Best regards!

I think I already did it...

In the log4j.properties file I wrote: log4j.logger.org.activebpel=FATAL

That's a filter for printing only messages of level FATAL or above in the package org.activebpel, right?

By the way, thank you for your answer... I'll keep looking for this thing that is driving me crazy.

Best regards!

[wdfink]

No,

what you do is to configure category, thats not what I mean.

You must configure the appender like this:

<appender>

....

      <filter class="org.jboss.logging.filter.TCLFilter">

        <param name="AcceptOnMatch" value="false"/>

        <param name="DeployURL" value="opsc-gold_cs.ear"/>

      </filter>

      <filter class="org.jboss.logging.filter.TCLFilter">

        <param name="AcceptOnMatch" value="false"/>

        <param name="DeployURL" value="application.ear"/>

      </filter>

</appender>

What I do here is to supress all output from this EAR.

But this can be a problem for performance because the log output is completely processed and not written final to the file/console..