You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "David Crossley (JIRA)" <ji...@apache.org> on 2005/12/01 08:54:29 UTC
[jira] Created: (FOR-750) direct the ehcache log messages to file not stdout, reduce loglevel
direct the ehcache log messages to file not stdout, reduce loglevel
-------------------------------------------------------------------
Key: FOR-750
URL: http://issues.apache.org/jira/browse/FOR-750
Project: Forrest
Type: Bug
Components: Core operations
Versions: 0.8-dev
Reporter: David Crossley
Fix For: 0.8-dev
The messages from the Cocoon cache are coming to the stdout console. They should be going to WEB-INF/logs/ like the rest and should be configurable so not at DEBUG level by default.
Other log messages are handled by logkit.xconf file. These ehcache ones should probably handled by log4j, but our WEB-INF/classes/log4j.properties seems to have no effect.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
upgrading our Cocoon (Was: FOR-750)
Posted by David Crossley <cr...@apache.org>.
I am going ahead to do the upgrade, and together we can
fix the issue.
If someone has a problem with that, then speak up
and i will revert.
-David
David Crossley wrote:
> Yipee, today i upgraded our Cocoon and it fixes those log
> messages.
>
> However, it causes a problem with the Dispatcher seed-v2 site
> (samples/index.html busts) so i have not committed it.
>
> If anyone else wants to try it, follow the instructions
> in etc/cocoon_upgrade/
>
> I needed to keep our fop-*.jar rather than Cocoon's
> and i needed to tweak our WEB-INF/xconf/forrest-core.xconf
> for some changes with the "template" block. This latter
> might be what causes the Dispatcher issue.
Re: [jira] Created: (FOR-750) direct the ehcache log messages to file not stdout, reduce loglevel
Posted by David Crossley <cr...@apache.org>.
Yipee, today i upgraded our Cocoon and it fixes those log
messages.
However, it causes a problem with the Dispatcher seed-v2 site
(samples/index.html busts) so i have not committed it.
If anyone else wants to try it, follow the instructions
in etc/cocoon_upgrade/
I needed to keep our fop-*.jar rather than Cocoon's
and i needed to tweak our WEB-INF/xconf/forrest-core.xconf
for some changes with the "template" block. This latter
might be what causes the Dispatcher issue.
-David
David Crossley (JIRA) wrote:
> direct the ehcache log messages to file not stdout, reduce loglevel
> -------------------------------------------------------------------
>
> Key: FOR-750
> URL: http://issues.apache.org/jira/browse/FOR-750
> Project: Forrest
> Type: Bug
> Components: Core operations
> Versions: 0.8-dev
> Reporter: David Crossley
> Fix For: 0.8-dev
>
>
> The messages from the Cocoon cache are coming to the stdout console. They should be going to WEB-INF/logs/ like the rest and should be configurable so not at DEBUG level by default.
>
> Other log messages are handled by logkit.xconf file. These ehcache ones should probably handled by log4j, but our WEB-INF/classes/log4j.properties seems to have no effect.
>
> --
[jira] Commented: (FOR-750) direct the ehcache log messages to file not stdout, reduce loglevel
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-750?page=comments#action_12359851 ]
David Crossley commented on FOR-750:
------------------------------------
The recent upgrade of our packaged Cocoon at r355366 did stop the ehcache log messages coming to stdout. However, now it seems that the cache debug messages are not logged anywhere.
> direct the ehcache log messages to file not stdout, reduce loglevel
> -------------------------------------------------------------------
>
> Key: FOR-750
> URL: http://issues.apache.org/jira/browse/FOR-750
> Project: Forrest
> Type: Bug
> Components: Core operations
> Versions: 0.8-dev
> Reporter: David Crossley
> Fix For: 0.8-dev
>
> The messages from the Cocoon cache are coming to the stdout console. They should be going to WEB-INF/logs/ like the rest and should be configurable so not at DEBUG level by default.
> Other log messages are handled by logkit.xconf file. These ehcache ones should probably handled by log4j, but our WEB-INF/classes/log4j.properties seems to have no effect.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (FOR-750) direct the ehcache log messages to file not stdout, reduce loglevel
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-750?page=all ]
Ross Gardler updated FOR-750:
-----------------------------
Fix Version: (was: 0.8-dev)
> direct the ehcache log messages to file not stdout, reduce loglevel
> -------------------------------------------------------------------
>
> Key: FOR-750
> URL: http://issues.apache.org/jira/browse/FOR-750
> Project: Forrest
> Type: Bug
> Components: Core operations
> Versions: 0.8-dev
> Reporter: David Crossley
>
> The messages from the Cocoon cache are coming to the stdout console. They should be going to WEB-INF/logs/ like the rest and should be configurable so not at DEBUG level by default.
> Other log messages are handled by logkit.xconf file. These ehcache ones should probably handled by log4j, but our WEB-INF/classes/log4j.properties seems to have no effect.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira