headers
Alfred Nathaniel | 1 May 14:12
Picon
Favicon

Re: Excessive file handles on cocoon.xconf

On Wed, 2008-04-30 at 01:04 +0100, Andy Stevens wrote:
> Okay, I admit this is more a user query, but since it's a bit more
> technical that some I thought I'd ask where more of the developers
> hang out.
> 
> We've just migrated some 2.1.x-based sites from Websphere 5 on Solaris
> and Windows (where they were running quite happily) to Websphere 6 on
> Linux.  And now, from time to time, we keep getting occassional
> FileNotFound exceptions stating "Too many open files", leading to the
> pages returning 500s.  This isn't even under heavy load.  The sites
> could have been sitting there untouched for a couple of hours (they're
> not live yet), but subsequently opening up all the home pages you'd
> get a significant proportion of them producing the error.  A few
> minutes later you refresh those pages that gave an error and they come
> up fine...
> 
> We've worked around it by using ulimit to increase the no. of
> available handles (per process, if I read the docs correctly) from the
> default 1024 to 8000, and haven't seen it happen again.  So it looks
> like it is simply that from time to time we hit the limit on
> simultaneously open files, and by the time we try again a few minutes
> later some of the handles have been freed up again.  The interesting
> thing (and the reason for my mail) is that at the time we're seeing
> the error, doing an lsof on that particular app server's process ID
> reveals hundreds of open file handles on cocoon.xconf
> 
> So, my question is this - can anyone suggest why this configuration
> file keeps getting opened so much?  It's almost as if every time a
> configurable sitemap component is called, it's opening the file again
> to check the default configuration, and not releasing the handle again
(Continue reading)

Permalink | Reply | 0 comments |
headers
Lukas.Lechner | 1 May 14:14

Lukas Lechner ist außer Haus.


Ich werde ab  01.05.2008 nicht im Büro sein. Ich kehre zurück am
04.05.2008.

Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.

This e-mail may contain confidential and privileged information.
If you are not the intended recipient, please notify the sender and delete
this e-mail immediately.
Permalink | Reply | 0 comments |
headers
Steven Dolg (JIRA | 2 May 12:36
Picon
Favicon

[jira] Created: (COCOON-2205) Provide an asynchronous caching mechanism.

Provide an asynchronous caching mechanism.
------------------------------------------

                 Key: COCOON-2205
                 URL: https://issues.apache.org/jira/browse/COCOON-2205
             Project: Cocoon
          Issue Type: New Feature
          Components: Corona (experimental)
            Reporter: Steven Dolg

Provide a caching mechanism that performs cache updates asynchronously, if the cached value is no longer
valid, and uses the previously cached result until the updated result is available.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Permalink | Reply | 3 comments |
headers
Steven Dolg (JIRA | 2 May 12:38
Picon
Favicon

[jira] Updated: (COCOON-2205) Provide an asynchronous caching mechanism.


     [
https://issues.apache.org/jira/browse/COCOON-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Dolg updated COCOON-2205:
--------------------------------

    Attachment: async-caching.txt

A patch that introduces a new pipeline type that implements the mechanism described above.

> Provide an asynchronous caching mechanism.
> ------------------------------------------
>
>                 Key: COCOON-2205
>                 URL: https://issues.apache.org/jira/browse/COCOON-2205
>             Project: Cocoon
>          Issue Type: New Feature
>          Components: Corona (experimental)
>            Reporter: Steven Dolg
>         Attachments: async-caching.txt
>
>
> Provide a caching mechanism that performs cache updates asynchronously, if the cached value is no longer
valid, and uses the previously cached result until the updated result is available.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Reinhard Poetz (JIRA | 2 May 19:16
Picon
Favicon

[jira] Assigned: (COCOON-2205) Provide an asynchronous caching mechanism.


     [
https://issues.apache.org/jira/browse/COCOON-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Reinhard Poetz reassigned COCOON-2205:
--------------------------------------

    Assignee: Reinhard Poetz

> Provide an asynchronous caching mechanism.
> ------------------------------------------
>
>                 Key: COCOON-2205
>                 URL: https://issues.apache.org/jira/browse/COCOON-2205
>             Project: Cocoon
>          Issue Type: New Feature
>          Components: Corona (experimental)
>            Reporter: Steven Dolg
>            Assignee: Reinhard Poetz
>         Attachments: async-caching.txt
>
>
> Provide a caching mechanism that performs cache updates asynchronously, if the cached value is no longer
valid, and uses the previously cached result until the updated result is available.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ralph Goers | 5 May 09:08
Favicon

Re: Java 1.5 [was svn commit: r579132 - in /cocoon/trunk/core/cocoon-core/src/test/java/org/apache/cocoon/transfo rmation:I18NTransformerTestCase.java I18NTransformerTestCase.java.disabled]

I sure am glad we decided to go with Java 1.4 for 2.2. See the nice 
bulletin at http://java.sun.com/j2se/1.4.2/download.html. At least now 
I'm certain we won't be supporting 1.4 until 2010.

Ralph Goers wrote:
> Carsten Ziegeler said:
>
>   
>> Although I guess everyone understood what I meant above, just a
>> clarification: of course I meant that it only makes sense to stick with
>> 1.4 if the people working on and using 2.2 *with jdk 1.4* is a critical
>> mass. There is no doubt that currently there are many people
>> using/develeoping 2.2 in general.
>>     
>
> We just switched our Cocoon deployment in production from IBM 1.4 to Sun
> 1.5 and got at least a 25% performance improvement. Java 1.6 is out.  It
> seems nuts to me to continue to target 1.4 on an as yet unreleased new
> version of Cocoon.  However, if you view this as a code change then the
> voting rules state that a single -1 vetoes the proposal, and we got that
> before.  Unless the -1 is rescinded I fear we will be stuck at 1.4 until
> 2010.
>
> Ralph
>
>
Permalink | Reply | 3 comments |
headers
Vadim Gritsenko | 5 May 14:50

Re: Java 1.5 [was svn commit: r579132 - in /cocoon/trunk/core/cocoon-core/src/test/java/org/apache/cocoon/transfo rmation:I18NTransformerTestCase.java I18NTransformerTestCase.java.disabled]

On May 5, 2008, at 3:08 AM, Ralph Goers wrote:

> I sure am glad we decided to go with Java 1.4 for 2.2. See the nice  
> bulletin at http://java.sun.com/j2se/1.4.2/download.html. At least  
> now I'm certain we won't be supporting 1.4 until 2010.
>
> Ralph Goers wrote:
>> Carsten Ziegeler said:
>>
>>
>>> Although I guess everyone understood what I meant above, just a
>>> clarification: of course I meant that it only makes sense to stick  
>>> with
>>> 1.4 if the people working on and using 2.2 *with jdk 1.4* is a  
>>> critical
>>> mass. There is no doubt that currently there are many people
>>> using/develeoping 2.2 in general.
>>>
>>
>> We just switched our Cocoon deployment in production from IBM 1.4  
>> to Sun
>> 1.5 and got at least a 25% performance improvement. Java 1.6 is  
>> out.  It
>> seems nuts to me to continue to target 1.4 on an as yet unreleased  
>> new
>> version of Cocoon.  However, if you view this as a code change then  
>> the
>> voting rules state that a single -1 vetoes the proposal, and we got  
>> that
>> before.  Unless the -1 is rescinded I fear we will be stuck at 1.4
(Continue reading)

Permalink | Reply | 0 comments |
headers
Reinhard Poetz (JIRA | 5 May 22:31
Picon
Favicon

[jira] Closed: (COCOON-2205) Provide an asynchronous caching mechanism.


     [
https://issues.apache.org/jira/browse/COCOON-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Reinhard Poetz closed COCOON-2205.
----------------------------------

    Resolution: Fixed

patch applied, thanks Steven!

> Provide an asynchronous caching mechanism.
> ------------------------------------------
>
>                 Key: COCOON-2205
>                 URL: https://issues.apache.org/jira/browse/COCOON-2205
>             Project: Cocoon
>          Issue Type: New Feature
>          Components: Corona (experimental)
>            Reporter: Steven Dolg
>            Assignee: Reinhard Poetz
>         Attachments: async-caching.txt
>
>
> Provide a caching mechanism that performs cache updates asynchronously, if the cached value is no longer
valid, and uses the previously cached result until the updated result is available.

--

-- 
This message is automatically generated by JIRA.
-
(Continue reading)

Permalink | Reply | 0 comments |
headers
av@alessandro.vincelli.name | 7 May 12:19

[2.2] cocoon-22-archetype-block version 1.0.0

I created a block project with the version 1.0.0 of
cocoon-22-archetype-block.

mvn archetype:create -DarchetypeGroupId=org.apache.cocoon
-DarchetypeArtifactId=cocoon-22-archetype-block
-DarchetypeVersion=1.0.0 -DgroupId=my.company
-DartifactId=myFirstBlock

I receive this error when I invoke:

mvn eclipse:eclipse

[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix:
'eclipse'.
[INFO]
------------------------------------------------------------------------
[INFO] Building dealsRepo
[INFO]    task-segment: [eclipse:eclipse]
[INFO]
------------------------------------------------------------------------
[INFO] Preparing eclipse:eclipse
[INFO] No goals needed for project - skipping
[WARNING] POM for
'org.eclipse.core:resources:pom:3.3.0-v20070604:runtime' is
invalid. It will be ignored for artifact resolution. Reason:
Not a v4.0.0 POM. for project org.eclipse.core:resources at
/Users/alessandro/.m2/repository/org/eclipse/core/resources/3.3.0-v20070604/resources-3.3.0-v20070604.pom
[INFO] [eclipse:eclipse]
[INFO]
(Continue reading)

Permalink | Reply | 1 comment |
headers
jira | 7 May 19:40
Picon
Favicon

[jira] Subscription: COCOON-open-with-patch

Issue Subscription
Filter: COCOON-open-with-patch (106 issues)
Subscriber: cocoon

Key         Summary
COCOON-2197 Making the cocoon-auth-block acegi-security-sample work
            https://issues.apache.org/jira/browse/COCOON-2197
COCOON-2177 ImageOp with requested height & width both zero should be a no-op, instead it throws an exception
            https://issues.apache.org/jira/browse/COCOON-2177
COCOON-2173 AbstractCachingProcessingPipeline: Two requests can deadlock each other
            https://issues.apache.org/jira/browse/COCOON-2173
COCOON-2162 [PATCH] Fix for Paginator when accessing out of bounds Pagination page
            https://issues.apache.org/jira/browse/COCOON-2162
COCOON-2137 XSD Schemas for CForms Development
            https://issues.apache.org/jira/browse/COCOON-2137
COCOON-2114 fix sorting in TraversableGenerator
            https://issues.apache.org/jira/browse/COCOON-2114
COCOON-2108 xmodule:flow-attr Does not accept document objects
            https://issues.apache.org/jira/browse/COCOON-2108
COCOON-2104 [PATCH] Add base URI fixup support to XIncludeTransformer
            https://issues.apache.org/jira/browse/COCOON-2104
COCOON-2100 Retrieving mimeType returned by pipeline executed from Flow
            https://issues.apache.org/jira/browse/COCOON-2100
COCOON-2071 Option to turn off pooling for components (probably faster on new JVMs and simpler debugging)
            https://issues.apache.org/jira/browse/COCOON-2071
COCOON-2063 NekoHTMLTransformer needs to set the default-encoding of the current system to work
properly with UTF-8
            https://issues.apache.org/jira/browse/COCOON-2063
COCOON-2041 WebDAV Returns improper status on PUT
            https://issues.apache.org/jira/browse/COCOON-2041
(Continue reading)

Permalink | Reply | 0 comments |

Gmane