The fact that I see messages generated by Tomcat that are not formatted according to our Log4J configuration, like:
Jan 26, 2016 8:52:27 AM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler ["ajp-bio-8009"] Jacopo On Mon, Jan 25, 2016 at 7:19 PM, Jacques Le Roux < [email protected]> wrote: > What makes you think "messages go to the standard output instead of the > logging framework" ? > > Jacques > > > Le 20/01/2016 08:58, Jacopo Cappellato a écrit : > >> I think there is also a problem in the way Tomcat is setup to use log4j: >> messages goes to the standard output instead of the logging framework; it >> may be due to a missing jar when the last upgrade of Tomcat was >> implemented >> in OFBiz. >> >> Jacopo >> >> On Wed, Jan 20, 2016 at 6:06 AM, Deepak Dixit < >> [email protected]> wrote: >> >> Hi Hans, >>> >>> Here is the ticket for the same: OFBIZ-6807 >>> <https://issues.apache.org/jira/browse/OFBIZ-6807> >>> This warning generated due to changes done under OFBIZ-6655 >>> <https://issues.apache.org/jira/browse/OFBIZ-6655> >>> >>> Thanks & Regards >>> -- >>> Deepak Dixit >>> www.hotwaxsystems.com >>> >>> On Wed, Jan 20, 2016 at 8:34 AM, Ahmad Ludin <[email protected]> >>> wrote: >>> >>> I see the same messages in the recent trunk build; and "ant start" takes >>>> for ever >>>> >>>> On Tue, Jan 19, 2016 at 9:45 PM, Hans Bakker < >>>> [email protected] >>>> >>>> wrote: >>>> >>>> Anybody is aware of the catalina messages? >>>>> >>>>> example: >>>>> [java] 2016-01-20 08:39:37,037 |catalina-startup-1 |UtilXml >>>>> |W| [UtilXml.LocalResolver.resolveEntity] could not find >>>>> LOCAL >>>>> DTD/Schema with publicId [null] and the file/resource is >>>>> [javaee_web_services_client_1_3.xsd] >>>>> >>>>> >>>>> -- >>>>> >>>>> Regards, >>>>> >>>>> Hans Bakker >>>>> CEO, http://antwebsystems.com >>>>> >>>>> >>>>>
