headers
Joerg Heinicke | 1 Feb 01:42
Picon
Picon

Re: [2.2] Weird NPE when concurrency

On 31.01.2008 16:35, Thorsten Scherler wrote:

>> Have you made sure that your dispatcher transformer is configured correctly? If 
>> it is *not* threadsafe, you have to use the "prototype" scope. Otherwise you can 
>> use the "singleton" scope (which is actually the default!).
> 
> This is what I always thought and how it is in 2.1 and the old 2.2.
> version of cocoon that forrest is using.
> 
> <bean id="dispatcher"
>     name="org.apache.cocoon.transformation.Transformer/dispatcher"
>     class="org.apache.forrest.dispatcher.transformation.DispatcherTransformer">
>     <property name="manager" ref="org.apache.avalon.framework.service.ServiceManager"/>
>   </bean>
> 
> We made a test with forrest trunk and this fixed the errors but before
> migrating the app I will test with defining the "singleton" scope.

If you have already concurrency issues then you might try the prototype 
scope! With the above setup the DispatcherTransformer IS in singleton scope.

Joerg
Permalink | Reply | 0 comments |
headers
Felix Knecht | 1 Feb 08:05

Run latest from trunk


Hi all

When building and running the latest trunk I have some strange effects:
The frontpage looks really ugly (http://localhost:8888/) I thought 
to have seen it already better.
Moving over to forms sample block and click on BasicSamples/Various 
(Actions) the form (http://localhost:8888/samples/forms/form1) looks as 
ugly as the frontpage and I got errorrs in the log I haven't had times 
ago (see below). Note that the sample form loads correctly when loading 
a second time (moving back and click again on Variaous(Actions) ).

Anyone else recognize this effects?

Regards
Felix

Just the start of the Execption log

2008-02-01 07:57:23.195::INFO:  Started SelectChannelConnector @ 
0.0.0.0:8888
[INFO] Started Jetty Server
Creating a new contact row
Repeater event RepeaterEventAction[Row added=0] on row 0 (contact named 
null)
Creating a new contact row
Repeater event RepeaterEventAction[Row added=0] on row 1 (contact named 
null)
HTMLArea is deprecated. Please use alternatives instead.
2008-02-01 08:00:29.057::WARN:  EXCEPTION
(Continue reading)

Permalink | Reply | 5 comments |
headers
Felix Knecht | 1 Feb 09:33
Picon
Favicon

Re: Run latest from trunk

Felix Knecht schrieb:
> Hi all
>
> When building and running the latest trunk I have some strange effects:
> - The frontpage looks really ugly (http://localhost:8888/) I thought 
> to have seen it already better.
> - Moving over to forms sample block and click on BasicSamples/Various 
> (Actions) the form (http://localhost:8888/samples/forms/form1) looks 
> as ugly as the frontpage and I got errorrs in the log I haven't had 
> times ago (see below). Note that the sample form loads correctly when 
> loading a second time (moving back and click again on Variaous(Actions) ).
>
> Anyone else recognize this effects?
IMO it's following commit which causes the problems I have:
http://svn.apache.org/viewvc?view=rev&revision=615697

Just saw that this is a bugfix. I'll reopen the 
issuehttps://issues.apache.org/jira/browse/COCOON-2150

Regards
Felix
Permalink | Reply | 4 comments |
headers
Felix Knecht (JIRA | 1 Feb 09:37
Picon
Favicon

[jira] Reopened: (COCOON-2150) Error on resetting response


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

Felix Knecht reopened COCOON-2150:
----------------------------------

Make a clean build and 
- pointing browser to http://localhost:8888/ - this looks really ugly
- pointing browser to http://localhost:8888/samples/forms/form1- throws exceptions, looks ugly as
well, form tabs are not working

Browser: firefox

> Error on resetting response
> ---------------------------
>
>                 Key: COCOON-2150
>                 URL: https://issues.apache.org/jira/browse/COCOON-2150
>             Project: Cocoon
>          Issue Type: Bug
>          Components: - Servlet service framework
>    Affects Versions: 2.2-dev (Current SVN)
>            Reporter: Jörg Heinicke
>            Assignee: Grzegorz Kossakowski
>            Priority: Minor
>             Fix For: 2.2-dev (Current SVN)
>
>
> This is the exception shown on the console:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Felix Knecht (JIRA | 1 Feb 09:39
Picon
Favicon

[jira] Updated: (COCOON-2150) Error on resetting response


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

Felix Knecht updated COCOON-2150:
---------------------------------

    Priority: Critical  (was: Minor)

> Error on resetting response
> ---------------------------
>
>                 Key: COCOON-2150
>                 URL: https://issues.apache.org/jira/browse/COCOON-2150
>             Project: Cocoon
>          Issue Type: Bug
>          Components: - Servlet service framework
>    Affects Versions: 2.2-dev (Current SVN)
>            Reporter: Jörg Heinicke
>            Assignee: Grzegorz Kossakowski
>            Priority: Critical
>             Fix For: 2.2-dev (Current SVN)
>
>
> This is the exception shown on the console:
> java.lang.IllegalStateException: Committed
>         at org.mortbay.jetty.Response.resetBuffer(Response.java:855)
>         at org.mortbay.jetty.Response.reset(Response.java:834)
>         at javax.servlet.ServletResponseWrapper.reset(ServletResponseWrapper.java:182)
>         at org.apache.cocoon.servletservice.ServletServiceContext$PathDispatcher.forward(ServletServiceContext.java:576)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jeroen Reijn | 1 Feb 09:54
Picon

Re: Run latest from trunk

I can confirm the behavior. It happens on the frontpage and I've also 
seen it happen on some blocks sample pages. (I tried the htmlarea in the 
forms block).

Regards,

Jeroen

Felix Knecht wrote:
> Felix Knecht schrieb:
>> Hi all
>>
>> When building and running the latest trunk I have some strange effects:
>> - The frontpage looks really ugly (http://localhost:8888/) I thought 
>> to have seen it already better.
>> - Moving over to forms sample block and click on BasicSamples/Various 
>> (Actions) the form (http://localhost:8888/samples/forms/form1) looks 
>> as ugly as the frontpage and I got errorrs in the log I haven't had 
>> times ago (see below). Note that the sample form loads correctly when 
>> loading a second time (moving back and click again on 
>> Variaous(Actions) ).
>>
>> Anyone else recognize this effects?
> IMO it's following commit which causes the problems I have:
> http://svn.apache.org/viewvc?view=rev&revision=615697
> 
> Just saw that this is a bugfix. I'll reopen the 
> issuehttps://issues.apache.org/jira/browse/COCOON-2150
> 
> Regards
(Continue reading)

Permalink | Reply | 0 comments |
headers
Nico Verwer (JIRA | 1 Feb 10:23
Picon
Favicon

[jira] Created: (COCOON-2164) Bug in JaxpResolver in validation block

Bug in JaxpResolver in validation block
---------------------------------------

                 Key: COCOON-2164
                 URL: https://issues.apache.org/jira/browse/COCOON-2164
             Project: Cocoon
          Issue Type: Bug
          Components: Blocks: Validation
    Affects Versions: 2.1.11, 2.1.10
            Reporter: Nico Verwer

There is a bug in the validation block, in org.apache.cocoon.components.validation.jaxp.JaxpResolver.
It implements org.w3c.dom.ls.LSResourceResolver, but the parameter order in method resolveResource
is wrong.
According to the API of org.w3c.dom.ls.LSResourceResolver, this should be:
resolveResource(String type, String namespaceURI, String publicId, String systemId, String baseURI)
but in org.apache.cocoon.components.validation.jaxp.JaxpResolver it is
resolveResource(String type, String namespace, String systemId, String publicId, String base)

The publicId and systemId have been swapped. This prevents the validation block from using XML schemas
that have import or include.
Using the parameters in the right order solves this problem.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Permalink | Reply | 2 comments |
headers
Thorsten Scherler | 1 Feb 10:26
Picon

Re: [2.2] Weird NPE when concurrency

On Thu, 2008-01-31 at 22:42 +0100, Reinhard Poetz wrote:
> Thorsten Scherler wrote:
> > On Thu, 2008-01-31 at 21:41 +0100, Reinhard Poetz wrote:
> >> Thorsten Scherler wrote:
> >>> Hi all,
> >>>
> >>> we have build a webapp based on cocoon 2.2. Everything is working fine
> >>> if a single person is using the app, but as soon as we have concurrent
> >>> user the code fails with NPE in different lines of the code.
> >>>
> >>> My questions are:
> >>> Every pipeline is thread safe, right?
> >>> The mounts to the different servlet (blocks) is synchronized, right?
> >>> Is there a connection timeout for inner block communications?
> >>>
> >>> The architecture is as follow:
> >>> main webapp - mounts dispatcher sitemap (from block)
> >>>
> >>> Main match:
> >>>  <map:match pattern="**.html">
> >>>         <map:generate src="lm://resolve.structurer.{1}" type="jx">
> >>>           <map:parameter name="lenient-xpath" value="true"/>
> >>>           <map:parameter name="getRequest" value="{1}"/>
> >>>           <map:parameter name="contextPath"
> >>> value="{request:contextPath}"/>
> >>>           <map:parameter name="getRequestExtension" value="html"/>
> >>>         </map:generate>
> >>>         <map:transform type="dispatcher">
> >>>           <map:parameter name="cacheKey" value="{0}"/>
> >>>           <map:parameter name="validityFile"
(Continue reading)

Permalink | Reply | 4 comments |
headers
Joerg Heinicke | 1 Feb 13:53
Picon
Picon

Re: [2.2] Weird NPE when concurrency

On 01.02.2008 04:26, Thorsten Scherler wrote:

> I will update the documentation and point this out since it is a major
> difference to 2.1. Can somebody create me an user daisy? TIA.

As far as I remember you have to create it yourself and only afterwards 
somebody can assign the necessary roles to you.

Joerg
Permalink | Reply | 3 comments |
headers
Thorsten Scherler | 1 Feb 14:16
Picon

Re: [2.2] Weird NPE when concurrency

On Fri, 2008-02-01 at 07:53 -0500, Joerg Heinicke wrote:
> On 01.02.2008 04:26, Thorsten Scherler wrote:
> 
> > I will update the documentation and point this out since it is a major
> > difference to 2.1. Can somebody create me an user daisy? TIA.
> 
> As far as I remember you have to create it yourself and only afterwards 
> somebody can assign the necessary roles to you.

Thanks, will do.

salu2
--

-- 
Thorsten Scherler                                 thorsten.at.apache.org
Open Source Java                      consulting, training and solutions
Permalink | Reply | 2 comments |

Gmane