Orbeon Forms community mailing list

Debug log is default ON in latest nightly - 9/9/2009

Classic

List

Threaded

3 messages Options

Hoi Chong

Debug log is default ON in latest nightly - 9/9/2009

Hi,
I am testing the latest Orbeon nightly, orbeon-dev-post-3.7.1.200909090800.

There is a lot of debugging output even though the additional debug configs in the log4j.xml have been commented out.

Cheers.

Alessandro Vernet

Re: Debug log is default ON in latest nightly - 9/9/2009

Administrator

hoichong wrote

I am testing the latest Orbeon nightly, orbeon-dev-post-3.7.1.200909090800.

There is a lot of debugging output even though the additional debug configs in the log4j.xml have been commented out.

We recently made some improvements to the way we do logging. You can now control logging with a much better granularity using the oxf.xforms.logging.debug property. Also you don't have to restart Tomcat as you change your logging setting, as you'll have a less of a need to change you log4j.xml. More on this at:

http://wiki.orbeon.com/forms/doc/developer-guide/xforms-logging

Now, by default, you shouldn't have additional debug logging info in your log. Maybe our default configuration should be changed. Can you tell us more about what you see now which you didn't have before?

Alex

Hoi Chong

Re: Debug log is default ON in latest nightly - 9/9/2009

Hi,
I have got these types of debug logs which should only show up when debug config is enabled.

2009-09-10 00:52:11,929 ERROR XFormsServer - xforms-submit-error - response {status code: "500"}
2009-09-10 00:52:11,961 ERROR XFormsServer - xforms-submit-error - response headers {cache-control: "public", connection: "close", pragma: "", transfer-encoding: "chunked", content-type: "text/html;charset=utf-8", server: "Apache-Coyote/1.1", date: "Wed, 09 Sep 2009 16:52:11 GMT", expires: "Wed, 09 Sep 2009 16:52:11 GMT", last-modified: "Wed, 09 Sep 2009 16:52:11 GMT"}
2009-09-10 00:52:12,382 INFO ProcessorService - /society-common/edit-annual-report - Timing: 1529 - Cache hits for cache.main: 133, fault: 42, adds: 43, expirations: 0, success rate: 76%
2009-09-10 00:52:12,397 ERROR XFormsServer - xforms-submit-error - setting body string {body: "
<!DOCTYPE html
PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link rel="stylesheet" href="/orbeon/config/theme/error.css" type="text/css">
<title>Orbeon Forms - An Error has Occurred</title>
<meta name="generator" content="Orbeon Forms dev-post-3.7.1.200909090800">
<link rel="shortcut icon" href="/orbeon/ops/images/orbeon-icon-16.ico">
<link rel="icon" href="/orbeon/ops/images/orbeon-icon-16.png" type="image/png">
</head>
<body>
<div class="orbeon-error-panel">

Orbeon Forms - An Error has Occurred

<p>
An error has occurred in Orbeon Forms. You may want to try one of the following:

</p>
<ul>
<li>If this error occurred when you followed a link, press your browser's Back button.</li>
<li>
If the above does not work, try reloading the page:

<ul>
<li>
With Firefox and Safari: hold down the <code>shift</code> key and click the Reload button in your browser toolbar.

</li>
<li>
With Internet Explorer: hold down the <code>control</code> key and click the Reload button in your browser toolbar.

</li>
</ul>
</li>
<li>Return home.
</li>
</ul>

Error Message

<p class="orbeon-error-panel-message">Unparseable date: ""</p>
<div id="orbeon-error-panel-details-hidden">
<p>

Show details</p>
</div>

{ lots of log output.................... }
{ near the end... }

<p class="ops-version">Orbeon Forms dev-post-3.7.1.200909090800</p>
</div>
</body><script type="text/javascript"> function hideShowTBody(id) { var tbody = document.getElementById(id); for (var i = 0; tbody.rows.length > i; i++) { var row = tbody.rows[i]; if (row.style.display == 'none') row.style.display = ''; else row.style.display = 'none'; } } function hideShowSection (handlerElement) { var detailsHidden = getElementById("orbeon-error-panel-details-hidden"); var detailsShown = getElementById("orbeon-error-panel-details-shown"); if (handlerElement.className == "orbeon-error-panel-show-details") { detailsHidden.style.display = "none"; detailsShown.style.display = "block"; } else { detailsHidden.style.display = "block"; detailsShown.style.display = "none"; } } function getElementById(controlId) { var result = document.getElementById(controlId); if (result && (result.id != controlId) && document.all) { result = null; documentAll = document.all[controlId]; if (documentAll) { if (documentAll.length) { for (var i = 0; i < documentAll.length; i++) { if (documentAll[i].id == controlId) { result = documentAll[i]; break; } } } else { result = documentAll; } } } return result; } </script></html>"}
2009-09-10 01:03:12,725 ERROR XFormsServer - xforms-submit-error - setting throwable {throwable: "org.orbeon.oxf.xforms.submission.XFormsSubmissionException: (processing submission response): xforms:submission for submission id: edit-submission-ar, error code received when submitting instance: 500
null, line -1, column -1: xforms:submission for submission id: edit-submission-ar, error code received when submitting instance: 500
at org.orbeon.oxf.xforms.submission.XFormsModelSubmission.getReplacer(XFormsModelSubmission.java:599)

I do not have any settings in properties-local.xml and

the XFormsServer debug setting is commented out.

TQ.

Alessandro Vernet wrote

hoichong wrote

I am testing the latest Orbeon nightly, orbeon-dev-post-3.7.1.200909090800.

There is a lot of debugging output even though the additional debug configs in the log4j.xml have been commented out.

We recently made some improvements to the way we do logging. You can now control logging with a much better granularity using the oxf.xforms.logging.debug property. Also you don't have to restart Tomcat as you change your logging setting, as you'll have a less of a need to change you log4j.xml. More on this at:

http://wiki.orbeon.com/forms/doc/developer-guide/xforms-logging

Now, by default, you shouldn't have additional debug logging info in your log. Maybe our default configuration should be changed. Can you tell us more about what you see now which you didn't have before?

Alex