Hey guys,
has there been any progress in this matter? Any new insights?
We have a jira issue classified as Major Bug accusing us of
concurrency issues - IMO the worst thing that can happen to a web
application framework - and there's been no word for almost 2 weeks.
I'd like to see that
On 03/29/2012 12:15 PM, Steven Dolg wrote:
Hey guys,
has there been any progress in this matter? Any new insights?
Sorry last stand was that Javier is working on a block to reproduce the
issue outside our production env but he is ATM bombed with other tasks
since we entered the final
El 29 de marzo de 2012 18:01, Thorsten Scherler scher...@gmail.comescribió:
On 03/29/2012 12:15 PM, Steven Dolg wrote:
Hey guys,
has there been any progress in this matter? Any new insights?
Sorry last stand was that Javier is working on a block to reproduce the
issue outside our
Hello again,
using the test project from Thorsten [1] I created a very simple client,
running several threads to send requests for a randomly selected static
resource (one of the image files).
(Of course I reverted the synchronized in SpringComponentProvider
before running the tests!)
I ran
El 16 de marzo de 2012 11:07, Steven Dolg steven.d...@indoqa.com escribió:
Hello again,
using the test project from Thorsten [1] I created a very simple client,
running several threads to send requests for a randomly selected static
resource (one of the image files).
I was working on it
On 03/16/2012 02:33 PM, Javier Puerto wrote:
...
Controllers in general (or your specific one) could be causing
problems. (The synchronized in the SpringComponentProvider could
even cause parts of the execution before it to be executed
sequential instead of parallel).
On 2012-03-15 4:25, Thorsten Scherler wrote:
I think the key is the map:match pattern=**.* which is a welcome
door for concurrency issues. You need to request the page around 10
times and you see image glitches.
I started a small testing project but will need to finish it later.
BTW I
] Reload Mechanic: automatic
Robby
-Original Message-
From: Igor Malinin [mailto:igor...@gmail.com]
Sent: Thursday, March 15, 2012 9:13 AM
To: dev@cocoon.apache.org
Subject: Re: [C3] Concurrency issues with ComponentProvider
On 2012-03-15 4:25, Thorsten Scherler wrote:
I think the key
I just removed all references to RCL from from the project and then used
JRebel instead of it. I had to change then one line in XsltTransformer
to make XSLTs reloadable (it skipped checking originally if XSLT came
from a JAR).
AFAIK Jetty is able to re-deploy application in case it detects
not fix this
apparently.
Robby
-Original Message-
From: Igor Malinin [mailto:igor...@gmail.com]
Sent: Thursday, March 15, 2012 9:55 AM
To: dev@cocoon.apache.org
Subject: Re: [C3] Concurrency issues with ComponentProvider
I just removed all references to RCL from from the project
Hi Igor
El 15 de marzo de 2012 09:12, Igor Malinin igor...@gmail.com escribió:
On 2012-03-15 4:25, Thorsten Scherler wrote:
I think the key is the map:match pattern=**.* which is a welcome door
for concurrency issues. You need to request the page around 10 times and
you see image glitches.
I don't remember exactly all the steps, but basically Cocoon RCL is the
cocoon-maven-plugin, so you should remove this plugin from pom.xml then
RCL will not be used. Commenting out instructions in .rcl files will not
remove RCL itself from the build.
No modification of Cocoon is required,
Message-
From: Igor Malinin [mailto:igor...@gmail.com]
Sent: Thursday, March 15, 2012 10:50 AM
To: dev@cocoon.apache.org
Subject: Re: [C3] Concurrency issues with ComponentProvider
I don't remember exactly all the steps, but basically Cocoon RCL is the
cocoon-maven-plugin, so you should remove
I cannot look into this right now, but I'll sure do this evening.
I had some frustrating problems with svn yesterday and after a full hour
of not being able to do a simple svn up I gave up.
Seems to work now, so I'll try again this evening...
This should be removed without RCL:
webAppSourceDirectory${project.build.directory}/rcl/webapp/webAppSourceDirectory
I don't start individual blocks so I cannot help with this. But you can
always workaround it by creating web-app that references one block and
nothing else.
On 2012-03-15
Hi Javier,
that's the first time, I've heard of concurrency issues in C3.
That's not to say there cannot be any, just that it's probably a rare
case or you're stressing the system more than anyone else has yet.
Some thoughts top off my head:
- providers and factories should be singletons, as
Thanks Steven
El 14 de marzo de 2012 15:37, Steven Dolg steven.d...@indoqa.com escribió:
Hi Javier,
that's the first time, I've heard of concurrency issues in C3.
That's not to say there cannot be any, just that it's probably a rare case
or you're stressing the system more than anyone else
On 03/14/2012 04:17 PM, Javier Puerto wrote:
Thanks Steven
El 14 de marzo de 2012 15:37, Steven Dolg steven.d...@indoqa.com
mailto:steven.d...@indoqa.com escribió:
Hi Javier,
that's the first time, I've heard of concurrency issues in C3.
That's not to say there cannot be any,
18 matches
Mail list logo
