This is indeed annoying because we have not it in the log files. We have
related information though, so it's not a big deal.
[java] 2016-01-24 13:17:50,371 |0.0.0.0-startStop-1 |ServiceContainer
|I| Created new dispatcher: ical
[java] 2016-01-24 13:17:50,424 |main |CatalinaContainer |I| Connector AJP/1.3 @ 8009 - not-secure [org.apache.coyote.ajp.AjpProtocol]
started.
[java] 2016-01-24 13:17:50,424 |main |CatalinaContainer |I| Connector HTTP/1.1 @ 8080 - not-secure
[org.apache.coyote.http11.Http11Protocol] started.
[java] Jan 24, 2016 1:17:50 PM org.apache.coyote.AbstractProtocol start
[java] INFO: Starting ProtocolHandler ["ajp-bio-8009"]
[java] 2016-01-24 13:17:50,424 |main |CatalinaContainer |I| Connector HTTP/1.1 @ 8443 - secure [org.apache.coyote.http11.Http11Protocol]
started.
[java] Jan 24, 2016 1:17:50 PM org.apache.coyote.AbstractProtocol start
[java] INFO: Starting ProtocolHandler ["http-bio-8080"]
[java] 2016-01-24 13:17:50,424 |main |CatalinaContainer |I|
Started Apache Tomcat/7.0.65
[java] Jan 24, 2016 1:17:50 PM org.apache.coyote.AbstractProtocol start
[java] INFO: Starting ProtocolHandler ["http-bio-8443"]
[java] 2016-01-24 13:17:50,424 |main |ContainerLoader |I|
Started container catalina-container
I checked, I did not miss any files when updating at r1717760.
I then also updated this page
https://cwiki.apache.org/confluence/display/OFBIZ/How+to+upgrade+the+embedded+Tomcat
and it's safe from your previous version
https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=27848153&selectedPageVersions=15&selectedPageVersions=13
Maybe a new file is missing, or could it be because this is done another way in
Tomcat (not using log4j2, sfl4j, or what not?)?
Jacques
Le 26/01/2016 08:55, Jacopo Cappellato a écrit :
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 <
jacques.le.r...@les7arts.com> 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 <
deepak.di...@hotwaxsystems.com> 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 <ahmad.lu...@gmail.com>
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 <
h.bak...@antwebsystems.com
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