El 29 de marzo de 2012 18:01, Thorsten Scherler escribió:
> 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 b
Hello folks,
I was looking at cocoon3 Pipeline interface. I saw:
setup(OutputStream outputStream)
setup(OutputStream outputStream, Map parameters)
It seem one always needs to call setup() (which makes sense). But why
is there a method like this? Couldn't it be the execute method which
takes the
[
https://issues.apache.org/jira/browse/COCOON3-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Javier Puerto updated COCOON3-93:
-
Attachment: concurrency.jmx
concurrency.tar.gz
Concurrency block and JMeter stres
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 testing
Hi all,
there are a couple of "misplaced" classes that I put in C3 sources (see
[1] and [2]) for more details); moreover, there are some pending patches
(like as [3], for example) and proposed changes that have been passing
in mailing lists during the past months.
My proposal is to sanitize the si
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 re
