Avoiding JBPM logs from printing on jboss server?

JDK logger by default logs to standard error. And JBoss translates all standard error stream messages as log4j errors. That's why you see that mess Now try to use a different logging framework: anonsvn.jboss.org/repos/jbpm/jbpm4/trunk... I don't have a jbpm 4 at hand, so can't give you an exact answer.

But you should have some logging service defined in jbpm.cfg.xml. Probably something like: service name="logging" factory="org.jbpm.logging.db. Jdk14LogFactory.

JDK logger by default logs to standard error. And JBoss translates all standard error stream messages as log4j errors. That's why you see that mess.

Now try to use a different logging framework: anonsvn.jboss.org/repos/jbpm/jbpm4/trunk... I don't have a jbpm 4 at hand, so can't give you an exact answer. But you should have some logging service defined in jbpm.cfg.xml. Probably something like.

JDK logger by default logs to standard error. And JBoss translates all standard error stream messages as log4j errors. That's why you see that mess.

I don't have a jbpm 4 at hand, so can't give you an exact answer. But you should have some logging service defined in jbpm.cfg.xml.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.

Related Questions