You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Juan Jose Pablos <ch...@che-che.com> on 2004/06/03 20:54:10 UTC

Upgrade to cocoon 2.1.5

Hi,
I am nearly there, I have got a couple of issues, both related to JCS:

First, there is a lot of output like this one:
=====

[INFO] CompositeCacheConfigurator - -setting defaults to DC
[INFO] CompositeCacheConfigurator - -setting 
defaultCompositeCacheAttributes to [ useLateral = true, useRemote = 
true, useDisk = true, maxObjs = 1
00, maxSpoolPerRun = -1 ]

How can I remove These info messages?

Second,
=======

There is an error, but I am not sure if this is in my configuration, 
forrest, cocoon or JCS problem (seems the later):

[ERROR] IndexedDiskCache - -Failure updating element, cacheName: main, 
key: 
PK_G-file-cocoon://samples/index.xml?pipelinehash=5540375540376331998 
<java.lang.InterruptedException>java.lang.InterruptedException
         at java.lang.Object.wait(Native Method)
         at 
org.apache.jcs.utils.locking.ReadWriteLock.writeLock(ReadWriteLock.java:127)
         at 
org.apache.jcs.auxiliary.disk.indexed.IndexedDiskCache.doUpdate(IndexedDiskCache.java:252)
         at 
org.apache.jcs.auxiliary.disk.AbstractDiskCache$MyCacheListener.handlePut(AbstractDiskCache.java:417)
         at 
org.apache.jcs.engine.CacheEventQueue$PutEvent.doRun(CacheEventQueue.java:440)
         at 
org.apache.jcs.engine.CacheEventQueue$AbstractCacheEvent.run(CacheEventQueue.java:358)
         at 
org.apache.jcs.engine.CacheEventQueue$QProcessor.run(CacheEventQueue.java:327)


WDYT?

Cheers,
Cheche

Re: Upgrade to cocoon 2.1.5

Posted by Ugo Cei <ug...@apache.org>.
Il giorno 04/giu/04, alle 09:07, Ugo Cei ha scritto:

> I think it depends on log4j not being configured. We should ship with 
> a proper log4j config, as all those messages from JCS and other 
> libraries that use log4j, like Quartz, are really bothersome.

I tried to fix this by providing a default log4j.properties file, but 
there is one thing that is bothering me. In the file I have put:

log4j.appender.file.File=build/webapp/WEB-INF/logs/log4j.log

but this only works as long as you are running under the bundled Jetty 
(i.e. "cocoon servlet").

Is there a way to specify a path relative to the webapp context dir 
that works across all containers?

	Ugo

-- 
Ugo Cei - http://beblogging.com/


Re: Upgrade to cocoon 2.1.5

Posted by Ugo Cei <u....@cbim.it>.
Nicola Ken Barozzi wrote:
> 
> Over at Forrest, an upgrade to Cocoon 2.1.5 has brought us with these 
> issues... ideas?
> 
> Juan Jose Pablos wrote:
> 
>> Hi,
>> I am nearly there, I have got a couple of issues, both related to JCS:
>>
>> First, there is a lot of output like this one:
>> =====
>>
>> [INFO] CompositeCacheConfigurator - -setting defaults to DC
>> [INFO] CompositeCacheConfigurator - -setting 
>> defaultCompositeCacheAttributes to [ useLateral = true, useRemote = 
>> true, useDisk = true, maxObjs = 1
>> 00, maxSpoolPerRun = -1 ]
>>
>> How can I remove These info messages?

I think it depends on log4j not being configured. We should ship with a 
proper log4j config, as all those messages from JCS and other libraries 
that use log4j, like Quartz, are really bothersome.

I don't have any hint rearding the second problem.

	Ugo

Re: Upgrade to cocoon 2.1.5

Posted by Ugo Cei <u....@cbim.it>.
Nicola Ken Barozzi wrote:
> 
> Over at Forrest, an upgrade to Cocoon 2.1.5 has brought us with these 
> issues... ideas?
> 
> Juan Jose Pablos wrote:
> 
>> Hi,
>> I am nearly there, I have got a couple of issues, both related to JCS:
>>
>> First, there is a lot of output like this one:
>> =====
>>
>> [INFO] CompositeCacheConfigurator - -setting defaults to DC
>> [INFO] CompositeCacheConfigurator - -setting 
>> defaultCompositeCacheAttributes to [ useLateral = true, useRemote = 
>> true, useDisk = true, maxObjs = 1
>> 00, maxSpoolPerRun = -1 ]
>>
>> How can I remove These info messages?

I think it depends on log4j not being configured. We should ship with a 
proper log4j config, as all those messages from JCS and other libraries 
that use log4j, like Quartz, are really bothersome.

I don't have any hint rearding the second problem.

	Ugo

Re: Upgrade to cocoon 2.1.5

Posted by David Crossley <cr...@apache.org>.
Nicola Ken Barozzi wrote:
> Over at Forrest, an upgrade to Cocoon 2.1.5 has brought us with these 
> issues... ideas?

It looks like the Gmane Cc bug again. Your note did not
make it to cocoon-dev.

-_David


Re: Upgrade to cocoon 2.1.5

Posted by Nicola Ken Barozzi <ni...@apache.org>.
Over at Forrest, an upgrade to Cocoon 2.1.5 has brought us with these 
issues... ideas?

Juan Jose Pablos wrote:
> Hi,
> I am nearly there, I have got a couple of issues, both related to JCS:
> 
> First, there is a lot of output like this one:
> =====
> 
> [INFO] CompositeCacheConfigurator - -setting defaults to DC
> [INFO] CompositeCacheConfigurator - -setting 
> defaultCompositeCacheAttributes to [ useLateral = true, useRemote = 
> true, useDisk = true, maxObjs = 1
> 00, maxSpoolPerRun = -1 ]
> 
> How can I remove These info messages?
> 
> Second,
> =======
> 
> There is an error, but I am not sure if this is in my configuration, 
> forrest, cocoon or JCS problem (seems the later):
> 
> [ERROR] IndexedDiskCache - -Failure updating element, cacheName: main, 
> key: 
> PK_G-file-cocoon://samples/index.xml?pipelinehash=5540375540376331998 
> <java.lang.InterruptedException>java.lang.InterruptedException
>         at java.lang.Object.wait(Native Method)
>         at 
> org.apache.jcs.utils.locking.ReadWriteLock.writeLock(ReadWriteLock.java:127) 
> 
>         at 
> org.apache.jcs.auxiliary.disk.indexed.IndexedDiskCache.doUpdate(IndexedDiskCache.java:252) 
> 
>         at 
> org.apache.jcs.auxiliary.disk.AbstractDiskCache$MyCacheListener.handlePut(AbstractDiskCache.java:417) 
> 
>         at 
> org.apache.jcs.engine.CacheEventQueue$PutEvent.doRun(CacheEventQueue.java:440) 
> 
>         at 
> org.apache.jcs.engine.CacheEventQueue$AbstractCacheEvent.run(CacheEventQueue.java:358) 
> 
>         at 
> org.apache.jcs.engine.CacheEventQueue$QProcessor.run(CacheEventQueue.java:327) 


-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------