You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Rolf Kulemann <ro...@apache.org> on 2004/06/06 22:17:13 UTC
Starting problems using cocoon2.1.5
I did a fresh checkout of lenya and compiled it against cocoon2.1.5 and
get the following warnings after I started lenya: (Any ideas?)
Main Class: org.mortbay.jetty.Server
22:10:07.628 EVENT Checking Resource aliases
22:10:08.157 EVENT Starting Jetty/4.2.19
22:10:08.585 EVENT Started
WebApplicationContext[/,./build/lenya/webapp]
22:10:08.754 WARN!! Delete existing temp dir /tmp/Jetty__8888__ for
WebApplicationContext[/,./build/lenya/webapp]
0 2004-06-06 22:10:11,733 [main] WARN
org.apache.jcs.config.OptionConverter.instantiateByKey():151 - Could
not find value for key jcs.default.elementattributes
13 2004-06-06 22:10:11,746 [main] WARN
org.apache.jcs.engine.control.CompositeCacheConfigurator.parseElementAttributes():337 - Could not instantiate eAttr named 'jcs.default.elementattributes', using defaults.
33 2004-06-06 22:10:11,766 [main] WARN
org.apache.jcs.config.OptionConverter.instantiateByKey():151 - Could
not find value for key jcs.system.groupIdCache.elementattributes
34 2004-06-06 22:10:11,767 [main] WARN
org.apache.jcs.engine.control.CompositeCacheConfigurator.parseElementAttributes():337 - Could not instantiate eAttr named 'jcs.system.groupIdCache.elementattributes', using defaults.
509 2004-06-06 22:10:12,242 [main] WARN
org.apache.jcs.config.OptionConverter.instantiateByKey():151 - Could
not find value for key jcs.region.main.elementattributes
515 2004-06-06 22:10:12,248 [main] WARN
org.apache.jcs.engine.control.CompositeCacheConfigurator.parseElementAttributes():337 - Could not instantiate eAttr named 'jcs.region.main.elementattributes', using defaults.
server.properties not found, using command line or default properties
Opening database:
/home/roku/src/lenya-release/test/incubating-lenya-1.2-bin/build/lenya/webapp/WEB-INF/db/cocoondb
I also started cocoon 2.1.5 itself and get quite the same errors:
Main Class: org.mortbay.jetty.Server
22:14:12.380 EVENT Checking Resource aliases
22:14:13.174 EVENT Starting Jetty/4.2.19
22:14:14.289 EVENT Started WebApplicationContext[/,./build/webapp]
22:14:14.499 WARN!! Delete existing temp dir /tmp/Jetty__8888__ for
WebApplicationContext[/,./build/webapp]
INFO [main] (CompositeCacheConfigurator.java:120) - setting defaults to
DC
INFO [main] (CompositeCacheConfigurator.java:130) - setting
defaultCompositeCacheAttributes to [ useLateral = true, useRemote =
true, useDisk = true, maxObjs = 100, maxSpoolPerRun = -1 ]
WARN [main] (OptionConverter.java:151) - Could not find value for key
jcs.default.elementattributes
WARN [main] (CompositeCacheConfigurator.java:337) - Could not
instantiate eAttr named 'jcs.default.elementattributes', using defaults.
INFO [main] (CompositeCacheConfigurator.java:140) - setting
defaultElementAttributes to [ IS_LATERAL = false, IS_SPOOL = false,
IS_REMOTE = false, IS_ETERNAL = true, MaxLifeSeconds = -1, IdleTime =
-1, CreateTime = 1086552857529, LastAccessTime = 1086552857529,
getTimeToLiveSeconds() = -1000, createTime = 1086552857529 ]
WARN [main] (OptionConverter.java:151) - Could not find value for key
jcs.system.groupIdCache.elementattributes
WARN [main] (CompositeCacheConfigurator.java:337) - Could not
instantiate eAttr named 'jcs.system.groupIdCache.elementattributes',
using defaults.
INFO [main] (LRUMemoryCache.java:68) - initialized LRUMemoryCache for
groupIdCache
INFO [main] (CompositeCache.java:140) - Constructed cache with name:
groupIdCache
INFO [main] (IndexedDiskCache.java:90) - Cache file root directory:
/tmp/Jetty__8888__/cocoon-files/cache-dir
WARN [main] (OptionConverter.java:151) - Could not find value for key
jcs.region.main.elementattributes
WARN [main] (CompositeCacheConfigurator.java:337) - Could not
instantiate eAttr named 'jcs.region.main.elementattributes', using
defaults.
INFO [main] (LRUMemoryCache.java:68) - initialized LRUMemoryCache for
main
INFO [main] (CompositeCache.java:140) - Constructed cache with name:
main
INFO [main] (IndexedDiskCache.java:90) - Cache file root directory:
/tmp/Jetty__8888__/cocoon-files/cache-dir
server.properties not found, using command line or default properties
Opening database:
/home/roku/src/lenya-release/cocoon-2.1.5/build/webapp/WEB-INF/db/cocoondb
HSQLDB server 1.7.1 is running
Use SHUTDOWN to close normally. Use [Ctrl]+[C] to abort abruptly
--
Rolf Kulemann
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
Re: Starting problems using cocoon2.1.5
Posted by Mario Curcija <cu...@bison-soft.de>.
Rolf Kulemann wrote:
>I did a fresh checkout of lenya and compiled it against cocoon2.1.5 and
>get the following warnings after I started lenya: (Any ideas?)
>
>Main Class: org.mortbay.jetty.Server
>22:10:07.628 EVENT Checking Resource aliases
>22:10:08.157 EVENT Starting Jetty/4.2.19
>22:10:08.585 EVENT Started
>WebApplicationContext[/,./build/lenya/webapp]
>22:10:08.754 WARN!! Delete existing temp dir /tmp/Jetty__8888__ for
>WebApplicationContext[/,./build/lenya/webapp]
>0 2004-06-06 22:10:11,733 [main] WARN
>org.apache.jcs.config.OptionConverter.instantiateByKey():151 - Could
>not find value for key jcs.default.elementattributes
>13 2004-06-06 22:10:11,746 [main] WARN
>org.apache.jcs.engine.control.CompositeCacheConfigurator.parseElementAttributes():337 - Could not instantiate eAttr named 'jcs.default.elementattributes', using defaults.
>33 2004-06-06 22:10:11,766 [main] WARN
>org.apache.jcs.config.OptionConverter.instantiateByKey():151 - Could
>not find value for key jcs.system.groupIdCache.elementattributes
>34 2004-06-06 22:10:11,767 [main] WARN
>org.apache.jcs.engine.control.CompositeCacheConfigurator.parseElementAttributes():337 - Could not instantiate eAttr named 'jcs.system.groupIdCache.elementattributes', using defaults.
>509 2004-06-06 22:10:12,242 [main] WARN
>org.apache.jcs.config.OptionConverter.instantiateByKey():151 - Could
>not find value for key jcs.region.main.elementattributes
>515 2004-06-06 22:10:12,248 [main] WARN
>org.apache.jcs.engine.control.CompositeCacheConfigurator.parseElementAttributes():337 - Could not instantiate eAttr named 'jcs.region.main.elementattributes', using defaults.
>server.properties not found, using command line or default properties
>Opening database:
>/home/roku/src/lenya-release/test/incubating-lenya-1.2-bin/build/lenya/webapp/WEB-INF/db/cocoondb
>
>
>
>I also started cocoon 2.1.5 itself and get quite the same errors:
>
>
>
>Main Class: org.mortbay.jetty.Server
>22:14:12.380 EVENT Checking Resource aliases
>22:14:13.174 EVENT Starting Jetty/4.2.19
>22:14:14.289 EVENT Started WebApplicationContext[/,./build/webapp]
>22:14:14.499 WARN!! Delete existing temp dir /tmp/Jetty__8888__ for
>WebApplicationContext[/,./build/webapp]
> INFO [main] (CompositeCacheConfigurator.java:120) - setting defaults to
>DC
> INFO [main] (CompositeCacheConfigurator.java:130) - setting
>defaultCompositeCacheAttributes to [ useLateral = true, useRemote =
>true, useDisk = true, maxObjs = 100, maxSpoolPerRun = -1 ]
> WARN [main] (OptionConverter.java:151) - Could not find value for key
>jcs.default.elementattributes
> WARN [main] (CompositeCacheConfigurator.java:337) - Could not
>instantiate eAttr named 'jcs.default.elementattributes', using defaults.
> INFO [main] (CompositeCacheConfigurator.java:140) - setting
>defaultElementAttributes to [ IS_LATERAL = false, IS_SPOOL = false,
>IS_REMOTE = false, IS_ETERNAL = true, MaxLifeSeconds = -1, IdleTime =
>-1, CreateTime = 1086552857529, LastAccessTime = 1086552857529,
>getTimeToLiveSeconds() = -1000, createTime = 1086552857529 ]
> WARN [main] (OptionConverter.java:151) - Could not find value for key
>jcs.system.groupIdCache.elementattributes
> WARN [main] (CompositeCacheConfigurator.java:337) - Could not
>instantiate eAttr named 'jcs.system.groupIdCache.elementattributes',
>using defaults.
> INFO [main] (LRUMemoryCache.java:68) - initialized LRUMemoryCache for
>groupIdCache
> INFO [main] (CompositeCache.java:140) - Constructed cache with name:
>groupIdCache
> INFO [main] (IndexedDiskCache.java:90) - Cache file root directory:
>/tmp/Jetty__8888__/cocoon-files/cache-dir
> WARN [main] (OptionConverter.java:151) - Could not find value for key
>jcs.region.main.elementattributes
> WARN [main] (CompositeCacheConfigurator.java:337) - Could not
>instantiate eAttr named 'jcs.region.main.elementattributes', using
>defaults.
> INFO [main] (LRUMemoryCache.java:68) - initialized LRUMemoryCache for
>main
> INFO [main] (CompositeCache.java:140) - Constructed cache with name:
>main
> INFO [main] (IndexedDiskCache.java:90) - Cache file root directory:
>/tmp/Jetty__8888__/cocoon-files/cache-dir
>server.properties not found, using command line or default properties
>Opening database:
>/home/roku/src/lenya-release/cocoon-2.1.5/build/webapp/WEB-INF/db/cocoondb
>HSQLDB server 1.7.1 is running
>Use SHUTDOWN to close normally. Use [Ctrl]+[C] to abort abruptly
>
>
>
All of these [WARN]'s above are connected with JCS (as of ver 2.1.5,
Cocoon uses JCS instead of Jisp).
Please read:
http://cocoon.apache.org/2.1/changes.html#2.1.5
Configuration file for jcs caching sistem: cache.ccf is missing (or
maybe not if one is satisfied with defaults).
I assume that those few [WARN]'s are acceptable since Cocoon 2.1.5 is
distributed without specific *.ccf files as well.
Best Regards,
Mario Curcija
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
Re: Starting problems using cocoon2.1.5
Posted by Antonio Gallardo <ag...@agssa.net>.
Andreas Kuckartz dijo:
> I also can reproduce this bug for Cocoon 2.1.5 but I did not find a
> Bugzilla
> entry for it.
>
> I think that Cocoon should NOT issue these irritating jcs-warnings. (They
> have
> already been irritating Lenya-developers.)
:-) Agreed.
Perhaps we can request to Apache JCS project to use commons-logging
instead of log4j. That way we will be able to use LogKit that aims to
servlets logging needs. Something than we can do with Log4j, but rather as
a workaround instead of an elegant solution as is in LogKit.
The problem with log4j is that we need to define an absolute path. With
LogKit we simply don't care about that.
I found some solutions in Tomcat mail lists, but no one is too elegant as
we have with LogKit.
Best Regards,
Antonio Gallardo
Re: Starting problems using cocoon2.1.5
Posted by Andreas Kuckartz <A....@ping.de>.
I also can reproduce this bug for Cocoon 2.1.5 but I did not find a Bugzilla
entry for it.
I think that Cocoon should NOT issue these irritating jcs-warnings. (They have
already been irritating Lenya-developers.)
Andreas
----- Original Message -----
From: "Rolf Kulemann" <ro...@apache.org>
To: <de...@cocoon.apache.org>
Sent: Monday, June 07, 2004 3:46 PM
Subject: Re: Starting problems using cocoon2.1.5
> On Mon, 2004-06-07 at 13:34, Rolf Kulemann wrote:
> > On Mon, 2004-06-07 at 11:45, Stefano Mazzocchi wrote:
> > > Rolf Kulemann wrote:
> > >
> > > > I did a fresh checkout of lenya and compiled it against cocoon2.1.5 and
> > > > get the following warnings after I started lenya: (Any ideas?)
> > > >
> > > > Main Class: org.mortbay.jetty.Server
> > > > 22:10:07.628 EVENT Checking Resource aliases
> > > > 22:10:08.157 EVENT Starting Jetty/4.2.19
> > > > 22:10:08.585 EVENT Started
> > > > WebApplicationContext[/,./build/lenya/webapp]
> > > > 22:10:08.754 WARN!! Delete existing temp dir /tmp/Jetty__8888__ for
> > > > WebApplicationContext[/,./build/lenya/webapp]
> > >
> > > Try cleaning up the "tmp/Jetty_8888_" folder.
> >
> > Thats it. Thanks. I tried before to delete tmp/Jetty_8888_/* , but that
> > didn't help.
>
> Ah, ok, the warning (delete /tmp/Jetty) is gone now, but I still get the
> following warnings on lenya/cocoon start. Is that a problem or can I
> just ignore it? I download Cocoon.tar.gz from the cocoon website. I'm
> not using cocoon cvs here.
>
>
> Main Class: org.mortbay.jetty.Server
> 15:43:10.852 EVENT Checking Resource aliases
> 15:43:11.381 EVENT Starting Jetty/4.2.19
> 15:43:11.819 EVENT Started
> WebApplicationContext[/,./build/lenya/webapp]
> 0 2004-06-07 15:43:14,672 [main] WARN
> org.apache.jcs.config.OptionConverter.instantiateByKey():151 - Could
> not find value for key jcs.default.elementattributes
> 13 2004-06-07 15:43:14,685 [main] WARN
>
org.apache.jcs.engine.control.CompositeCacheConfigurator.parseElementAttributes(
):337 - Could not instantiate eAttr named 'jcs.default.elementattributes',
using defaults.
> 37 2004-06-07 15:43:14,709 [main] WARN
> org.apache.jcs.config.OptionConverter.instantiateByKey():151 - Could
> not find value for key jcs.system.groupIdCache.elementattributes
> 62 2004-06-07 15:43:14,734 [main] WARN
>
org.apache.jcs.engine.control.CompositeCacheConfigurator.parseElementAttributes(
):337 - Could not instantiate eAttr named
'jcs.system.groupIdCache.elementattributes', using defaults.
> 349 2004-06-07 15:43:15,021 [main] WARN
> org.apache.jcs.config.OptionConverter.instantiateByKey():151 - Could
> not find value for key jcs.region.main.elementattributes
> 354 2004-06-07 15:43:15,026 [main] WARN
>
org.apache.jcs.engine.control.CompositeCacheConfigurator.parseElementAttributes(
):337 - Could not instantiate eAttr named 'jcs.region.main.elementattributes',
using defaults.
> server.properties not found, using command line or default properties
> Opening database:
>
/home/roku/src/lenya-release/cocoon-lenya/build/lenya/webapp/WEB-INF/db/cocoondb
> HSQLDB server 1.7.1 is running
> Use SHUTDOWN to close normally. Use [Ctrl]+[C] to abort abruptly
> Mon Jun 07 15:43:15 CEST 2004 Listening for connections ...
> 2080 2004-06-07 15:43:16,752 [main] WARN scheduler.warn():186 - Quartz
> scheduler 'DefaultQuartzScheduler' initialized from default resource
> file in Quartz package: 'quartz.properties'
> 15:43:16.906 EVENT Started SocketListener on 0.0.0.0:8888
> 15:43:16.907 EVENT Started org.mortbay.jetty.Server@fe64b9
> --
> Rolf Kulemann
>
>
Re: Starting problems using cocoon2.1.5
Posted by Andreas Kuckartz <A....@ping.de>.
I also can reproduce this bug for Cocoon 2.1.5 but I did not find a Bugzilla
entry for it.
I think that Cocoon should NOT issue these irritating jcs-warnings. (They have
already been irritating Lenya-developers.)
Andreas
----- Original Message -----
From: "Rolf Kulemann" <ro...@apache.org>
To: <de...@cocoon.apache.org>
Sent: Monday, June 07, 2004 3:46 PM
Subject: Re: Starting problems using cocoon2.1.5
> On Mon, 2004-06-07 at 13:34, Rolf Kulemann wrote:
> > On Mon, 2004-06-07 at 11:45, Stefano Mazzocchi wrote:
> > > Rolf Kulemann wrote:
> > >
> > > > I did a fresh checkout of lenya and compiled it against cocoon2.1.5 and
> > > > get the following warnings after I started lenya: (Any ideas?)
> > > >
> > > > Main Class: org.mortbay.jetty.Server
> > > > 22:10:07.628 EVENT Checking Resource aliases
> > > > 22:10:08.157 EVENT Starting Jetty/4.2.19
> > > > 22:10:08.585 EVENT Started
> > > > WebApplicationContext[/,./build/lenya/webapp]
> > > > 22:10:08.754 WARN!! Delete existing temp dir /tmp/Jetty__8888__ for
> > > > WebApplicationContext[/,./build/lenya/webapp]
> > >
> > > Try cleaning up the "tmp/Jetty_8888_" folder.
> >
> > Thats it. Thanks. I tried before to delete tmp/Jetty_8888_/* , but that
> > didn't help.
>
> Ah, ok, the warning (delete /tmp/Jetty) is gone now, but I still get the
> following warnings on lenya/cocoon start. Is that a problem or can I
> just ignore it? I download Cocoon.tar.gz from the cocoon website. I'm
> not using cocoon cvs here.
>
>
> Main Class: org.mortbay.jetty.Server
> 15:43:10.852 EVENT Checking Resource aliases
> 15:43:11.381 EVENT Starting Jetty/4.2.19
> 15:43:11.819 EVENT Started
> WebApplicationContext[/,./build/lenya/webapp]
> 0 2004-06-07 15:43:14,672 [main] WARN
> org.apache.jcs.config.OptionConverter.instantiateByKey():151 - Could
> not find value for key jcs.default.elementattributes
> 13 2004-06-07 15:43:14,685 [main] WARN
>
org.apache.jcs.engine.control.CompositeCacheConfigurator.parseElementAttributes(
):337 - Could not instantiate eAttr named 'jcs.default.elementattributes',
using defaults.
> 37 2004-06-07 15:43:14,709 [main] WARN
> org.apache.jcs.config.OptionConverter.instantiateByKey():151 - Could
> not find value for key jcs.system.groupIdCache.elementattributes
> 62 2004-06-07 15:43:14,734 [main] WARN
>
org.apache.jcs.engine.control.CompositeCacheConfigurator.parseElementAttributes(
):337 - Could not instantiate eAttr named
'jcs.system.groupIdCache.elementattributes', using defaults.
> 349 2004-06-07 15:43:15,021 [main] WARN
> org.apache.jcs.config.OptionConverter.instantiateByKey():151 - Could
> not find value for key jcs.region.main.elementattributes
> 354 2004-06-07 15:43:15,026 [main] WARN
>
org.apache.jcs.engine.control.CompositeCacheConfigurator.parseElementAttributes(
):337 - Could not instantiate eAttr named 'jcs.region.main.elementattributes',
using defaults.
> server.properties not found, using command line or default properties
> Opening database:
>
/home/roku/src/lenya-release/cocoon-lenya/build/lenya/webapp/WEB-INF/db/cocoondb
> HSQLDB server 1.7.1 is running
> Use SHUTDOWN to close normally. Use [Ctrl]+[C] to abort abruptly
> Mon Jun 07 15:43:15 CEST 2004 Listening for connections ...
> 2080 2004-06-07 15:43:16,752 [main] WARN scheduler.warn():186 - Quartz
> scheduler 'DefaultQuartzScheduler' initialized from default resource
> file in Quartz package: 'quartz.properties'
> 15:43:16.906 EVENT Started SocketListener on 0.0.0.0:8888
> 15:43:16.907 EVENT Started org.mortbay.jetty.Server@fe64b9
> --
> Rolf Kulemann
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
Re: Starting problems using cocoon2.1.5
Posted by Rolf Kulemann <ma...@rolf-kulemann.com>.
On Mon, 2004-06-07 at 15:47, Antonio Gallardo wrote:
> Hi Rolf:
>
> You can ignore the jcs warnings, they does not affect the normal behavior.
>
> If you want to get rid the logs from the consore, then you need to
> configure log4j, ie: in WEB-INF/classes create a file called
> log4j.properties and place inside the file:
>
> #**********************************************************************
> # Apache JCS cache
> log4j.category.org.apache.jcs = INFO, jcs
> log4j.appender.jcs = org.apache.log4j.FileAppender
> log4j.appender.jcs.File = <PUT-HERE-THE-LOGGING-FILENAME>
> log4j.appender.jcs.layout = org.apache.log4j.PatternLayout
> log4j.appender.jcs.layout.ConversionPattern = %-5r %-5p [%t] %c{2} - %m%n
> log4j.appender.jcs.Append = false
> #**********************************************************************
>
> Next replace the tag: <PUT-HERE-THE-LOGGING-FILENAME> with the full name
> (including path) of the file where you want to log.
>
> Hope this helps,
Yes, excellent, thanks.
--
Rolf Kulemann
Re: Starting problems using cocoon2.1.5
Posted by Juan Jose Pablos <ch...@che-che.com>.
There is more information here:
http://logging.apache.org/log4j/docs/manual.html
Antonio Gallardo escribió:
> Hi Rolf:
>
> You can ignore the jcs warnings, they does not affect the normal behavior.
>
> If you want to get rid the logs from the consore, then you need to
> configure log4j, ie: in WEB-INF/classes create a file called
> log4j.properties and place inside the file:
>
> #**********************************************************************
> # Apache JCS cache
> log4j.category.org.apache.jcs = INFO, jcs
> log4j.appender.jcs = org.apache.log4j.FileAppender
> log4j.appender.jcs.File = <PUT-HERE-THE-LOGGING-FILENAME>
> log4j.appender.jcs.layout = org.apache.log4j.PatternLayout
> log4j.appender.jcs.layout.ConversionPattern = %-5r %-5p [%t] %c{2} - %m%n
> log4j.appender.jcs.Append = false
> #**********************************************************************
>
> Next replace the tag: <PUT-HERE-THE-LOGGING-FILENAME> with the full name
> (including path) of the file where you want to log.
>
> Hope this helps,
>
> Best Regards,
>
> Antonio Gallardo
>
> Rolf Kulemann dijo:
>
>>On Mon, 2004-06-07 at 13:34, Rolf Kulemann wrote:
>>
>>>On Mon, 2004-06-07 at 11:45, Stefano Mazzocchi wrote:
>>>
>>>>Rolf Kulemann wrote:
>>>>
>>>>
>>>>>I did a fresh checkout of lenya and compiled it against cocoon2.1.5
>>>
>>>and
>>>
>>>>>get the following warnings after I started lenya: (Any ideas?)
>>>>>
>>>>>Main Class: org.mortbay.jetty.Server
>>>>>22:10:07.628 EVENT Checking Resource aliases
>>>>>22:10:08.157 EVENT Starting Jetty/4.2.19
>>>>>22:10:08.585 EVENT Started
>>>>>WebApplicationContext[/,./build/lenya/webapp]
>>>>>22:10:08.754 WARN!! Delete existing temp dir /tmp/Jetty__8888__ for
>>>>>WebApplicationContext[/,./build/lenya/webapp]
>>>>
>>>>Try cleaning up the "tmp/Jetty_8888_" folder.
>>>
>>>Thats it. Thanks. I tried before to delete tmp/Jetty_8888_/* , but that
>>>didn't help.
>>
>>Ah, ok, the warning (delete /tmp/Jetty) is gone now, but I still get the
>>following warnings on lenya/cocoon start. Is that a problem or can I
>>just ignore it? I download Cocoon.tar.gz from the cocoon website. I'm
>>not using cocoon cvs here.
>>
>>
>>Main Class: org.mortbay.jetty.Server
>>15:43:10.852 EVENT Checking Resource aliases
>>15:43:11.381 EVENT Starting Jetty/4.2.19
>>15:43:11.819 EVENT Started
>>WebApplicationContext[/,./build/lenya/webapp]
>>0 2004-06-07 15:43:14,672 [main] WARN
>>org.apache.jcs.config.OptionConverter.instantiateByKey():151 - Could
>>not find value for key jcs.default.elementattributes
>>13 2004-06-07 15:43:14,685 [main] WARN
>>org.apache.jcs.engine.control.CompositeCacheConfigurator.parseElementAttributes():337
>> - Could not instantiate eAttr named 'jcs.default.elementattributes',
>>using defaults.
>>37 2004-06-07 15:43:14,709 [main] WARN
>>org.apache.jcs.config.OptionConverter.instantiateByKey():151 - Could
>>not find value for key jcs.system.groupIdCache.elementattributes
>>62 2004-06-07 15:43:14,734 [main] WARN
>>org.apache.jcs.engine.control.CompositeCacheConfigurator.parseElementAttributes():337
>> - Could not instantiate eAttr named
>>'jcs.system.groupIdCache.elementattributes', using defaults.
>>349 2004-06-07 15:43:15,021 [main] WARN
>>org.apache.jcs.config.OptionConverter.instantiateByKey():151 - Could
>>not find value for key jcs.region.main.elementattributes
>>354 2004-06-07 15:43:15,026 [main] WARN
>>org.apache.jcs.engine.control.CompositeCacheConfigurator.parseElementAttributes():337
>> - Could not instantiate eAttr named 'jcs.region.main.elementattributes',
>>using defaults.
>>server.properties not found, using command line or default properties
>>Opening database:
>>/home/roku/src/lenya-release/cocoon-lenya/build/lenya/webapp/WEB-INF/db/cocoondb
>>HSQLDB server 1.7.1 is running
>>Use SHUTDOWN to close normally. Use [Ctrl]+[C] to abort abruptly
>>Mon Jun 07 15:43:15 CEST 2004 Listening for connections ...
>>2080 2004-06-07 15:43:16,752 [main] WARN scheduler.warn():186 - Quartz
>>scheduler 'DefaultQuartzScheduler' initialized from default resource
>>file in Quartz package: 'quartz.properties'
>>15:43:16.906 EVENT Started SocketListener on 0.0.0.0:8888
>>15:43:16.907 EVENT Started org.mortbay.jetty.Server@fe64b9
>>--
>>Rolf Kulemann
>>
Re: Starting problems using cocoon2.1.5
Posted by Antonio Gallardo <ag...@agssa.net>.
Hi Rolf:
You can ignore the jcs warnings, they does not affect the normal behavior.
If you want to get rid the logs from the consore, then you need to
configure log4j, ie: in WEB-INF/classes create a file called
log4j.properties and place inside the file:
#**********************************************************************
# Apache JCS cache
log4j.category.org.apache.jcs = INFO, jcs
log4j.appender.jcs = org.apache.log4j.FileAppender
log4j.appender.jcs.File = <PUT-HERE-THE-LOGGING-FILENAME>
log4j.appender.jcs.layout = org.apache.log4j.PatternLayout
log4j.appender.jcs.layout.ConversionPattern = %-5r %-5p [%t] %c{2} - %m%n
log4j.appender.jcs.Append = false
#**********************************************************************
Next replace the tag: <PUT-HERE-THE-LOGGING-FILENAME> with the full name
(including path) of the file where you want to log.
Hope this helps,
Best Regards,
Antonio Gallardo
Rolf Kulemann dijo:
> On Mon, 2004-06-07 at 13:34, Rolf Kulemann wrote:
>> On Mon, 2004-06-07 at 11:45, Stefano Mazzocchi wrote:
>> > Rolf Kulemann wrote:
>> >
>> > > I did a fresh checkout of lenya and compiled it against cocoon2.1.5
>> and
>> > > get the following warnings after I started lenya: (Any ideas?)
>> > >
>> > > Main Class: org.mortbay.jetty.Server
>> > > 22:10:07.628 EVENT Checking Resource aliases
>> > > 22:10:08.157 EVENT Starting Jetty/4.2.19
>> > > 22:10:08.585 EVENT Started
>> > > WebApplicationContext[/,./build/lenya/webapp]
>> > > 22:10:08.754 WARN!! Delete existing temp dir /tmp/Jetty__8888__ for
>> > > WebApplicationContext[/,./build/lenya/webapp]
>> >
>> > Try cleaning up the "tmp/Jetty_8888_" folder.
>>
>> Thats it. Thanks. I tried before to delete tmp/Jetty_8888_/* , but that
>> didn't help.
>
> Ah, ok, the warning (delete /tmp/Jetty) is gone now, but I still get the
> following warnings on lenya/cocoon start. Is that a problem or can I
> just ignore it? I download Cocoon.tar.gz from the cocoon website. I'm
> not using cocoon cvs here.
>
>
> Main Class: org.mortbay.jetty.Server
> 15:43:10.852 EVENT Checking Resource aliases
> 15:43:11.381 EVENT Starting Jetty/4.2.19
> 15:43:11.819 EVENT Started
> WebApplicationContext[/,./build/lenya/webapp]
> 0 2004-06-07 15:43:14,672 [main] WARN
> org.apache.jcs.config.OptionConverter.instantiateByKey():151 - Could
> not find value for key jcs.default.elementattributes
> 13 2004-06-07 15:43:14,685 [main] WARN
> org.apache.jcs.engine.control.CompositeCacheConfigurator.parseElementAttributes():337
> - Could not instantiate eAttr named 'jcs.default.elementattributes',
> using defaults.
> 37 2004-06-07 15:43:14,709 [main] WARN
> org.apache.jcs.config.OptionConverter.instantiateByKey():151 - Could
> not find value for key jcs.system.groupIdCache.elementattributes
> 62 2004-06-07 15:43:14,734 [main] WARN
> org.apache.jcs.engine.control.CompositeCacheConfigurator.parseElementAttributes():337
> - Could not instantiate eAttr named
> 'jcs.system.groupIdCache.elementattributes', using defaults.
> 349 2004-06-07 15:43:15,021 [main] WARN
> org.apache.jcs.config.OptionConverter.instantiateByKey():151 - Could
> not find value for key jcs.region.main.elementattributes
> 354 2004-06-07 15:43:15,026 [main] WARN
> org.apache.jcs.engine.control.CompositeCacheConfigurator.parseElementAttributes():337
> - Could not instantiate eAttr named 'jcs.region.main.elementattributes',
> using defaults.
> server.properties not found, using command line or default properties
> Opening database:
> /home/roku/src/lenya-release/cocoon-lenya/build/lenya/webapp/WEB-INF/db/cocoondb
> HSQLDB server 1.7.1 is running
> Use SHUTDOWN to close normally. Use [Ctrl]+[C] to abort abruptly
> Mon Jun 07 15:43:15 CEST 2004 Listening for connections ...
> 2080 2004-06-07 15:43:16,752 [main] WARN scheduler.warn():186 - Quartz
> scheduler 'DefaultQuartzScheduler' initialized from default resource
> file in Quartz package: 'quartz.properties'
> 15:43:16.906 EVENT Started SocketListener on 0.0.0.0:8888
> 15:43:16.907 EVENT Started org.mortbay.jetty.Server@fe64b9
> --
> Rolf Kulemann
>
Re: Starting problems using cocoon2.1.5
Posted by Rolf Kulemann <ro...@apache.org>.
On Mon, 2004-06-07 at 13:34, Rolf Kulemann wrote:
> On Mon, 2004-06-07 at 11:45, Stefano Mazzocchi wrote:
> > Rolf Kulemann wrote:
> >
> > > I did a fresh checkout of lenya and compiled it against cocoon2.1.5 and
> > > get the following warnings after I started lenya: (Any ideas?)
> > >
> > > Main Class: org.mortbay.jetty.Server
> > > 22:10:07.628 EVENT Checking Resource aliases
> > > 22:10:08.157 EVENT Starting Jetty/4.2.19
> > > 22:10:08.585 EVENT Started
> > > WebApplicationContext[/,./build/lenya/webapp]
> > > 22:10:08.754 WARN!! Delete existing temp dir /tmp/Jetty__8888__ for
> > > WebApplicationContext[/,./build/lenya/webapp]
> >
> > Try cleaning up the "tmp/Jetty_8888_" folder.
>
> Thats it. Thanks. I tried before to delete tmp/Jetty_8888_/* , but that
> didn't help.
Ah, ok, the warning (delete /tmp/Jetty) is gone now, but I still get the
following warnings on lenya/cocoon start. Is that a problem or can I
just ignore it? I download Cocoon.tar.gz from the cocoon website. I'm
not using cocoon cvs here.
Main Class: org.mortbay.jetty.Server
15:43:10.852 EVENT Checking Resource aliases
15:43:11.381 EVENT Starting Jetty/4.2.19
15:43:11.819 EVENT Started
WebApplicationContext[/,./build/lenya/webapp]
0 2004-06-07 15:43:14,672 [main] WARN
org.apache.jcs.config.OptionConverter.instantiateByKey():151 - Could
not find value for key jcs.default.elementattributes
13 2004-06-07 15:43:14,685 [main] WARN
org.apache.jcs.engine.control.CompositeCacheConfigurator.parseElementAttributes():337 - Could not instantiate eAttr named 'jcs.default.elementattributes', using defaults.
37 2004-06-07 15:43:14,709 [main] WARN
org.apache.jcs.config.OptionConverter.instantiateByKey():151 - Could
not find value for key jcs.system.groupIdCache.elementattributes
62 2004-06-07 15:43:14,734 [main] WARN
org.apache.jcs.engine.control.CompositeCacheConfigurator.parseElementAttributes():337 - Could not instantiate eAttr named 'jcs.system.groupIdCache.elementattributes', using defaults.
349 2004-06-07 15:43:15,021 [main] WARN
org.apache.jcs.config.OptionConverter.instantiateByKey():151 - Could
not find value for key jcs.region.main.elementattributes
354 2004-06-07 15:43:15,026 [main] WARN
org.apache.jcs.engine.control.CompositeCacheConfigurator.parseElementAttributes():337 - Could not instantiate eAttr named 'jcs.region.main.elementattributes', using defaults.
server.properties not found, using command line or default properties
Opening database:
/home/roku/src/lenya-release/cocoon-lenya/build/lenya/webapp/WEB-INF/db/cocoondb
HSQLDB server 1.7.1 is running
Use SHUTDOWN to close normally. Use [Ctrl]+[C] to abort abruptly
Mon Jun 07 15:43:15 CEST 2004 Listening for connections ...
2080 2004-06-07 15:43:16,752 [main] WARN scheduler.warn():186 - Quartz
scheduler 'DefaultQuartzScheduler' initialized from default resource
file in Quartz package: 'quartz.properties'
15:43:16.906 EVENT Started SocketListener on 0.0.0.0:8888
15:43:16.907 EVENT Started org.mortbay.jetty.Server@fe64b9
--
Rolf Kulemann
Re: Starting problems using cocoon2.1.5
Posted by Rolf Kulemann <ro...@apache.org>.
On Mon, 2004-06-07 at 11:45, Stefano Mazzocchi wrote:
> Rolf Kulemann wrote:
>
> > I did a fresh checkout of lenya and compiled it against cocoon2.1.5 and
> > get the following warnings after I started lenya: (Any ideas?)
> >
> > Main Class: org.mortbay.jetty.Server
> > 22:10:07.628 EVENT Checking Resource aliases
> > 22:10:08.157 EVENT Starting Jetty/4.2.19
> > 22:10:08.585 EVENT Started
> > WebApplicationContext[/,./build/lenya/webapp]
> > 22:10:08.754 WARN!! Delete existing temp dir /tmp/Jetty__8888__ for
> > WebApplicationContext[/,./build/lenya/webapp]
>
> Try cleaning up the "tmp/Jetty_8888_" folder.
Thats it. Thanks. I tried before to delete tmp/Jetty_8888_/* , but that
didn't help.
--
Rolf Kulemann
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
Re: Starting problems using cocoon2.1.5
Posted by Stefano Mazzocchi <st...@apache.org>.
Rolf Kulemann wrote:
> I did a fresh checkout of lenya and compiled it against cocoon2.1.5 and
> get the following warnings after I started lenya: (Any ideas?)
>
> Main Class: org.mortbay.jetty.Server
> 22:10:07.628 EVENT Checking Resource aliases
> 22:10:08.157 EVENT Starting Jetty/4.2.19
> 22:10:08.585 EVENT Started
> WebApplicationContext[/,./build/lenya/webapp]
> 22:10:08.754 WARN!! Delete existing temp dir /tmp/Jetty__8888__ for
> WebApplicationContext[/,./build/lenya/webapp]
Try cleaning up the "tmp/Jetty_8888_" folder.
--
Stefano.