But does JMeter does that? Does JMeter do multiply request for the
same
session at the same time?
I have JMeter configured to have 200 threads (yes, insane :)
continuously request the page. However,
wicket should synchronize on the current session and serialize the
requests for the same session.
Maybe the test case is a 'little' exaggerated but still it shouldn't
be possible to produce
race conditions at all.
Releasing 1.3.4 is in any case a good thing as it can only get better
for users when more
issues are resolved in an official release.
Cheers
Peter
Am 20.06.2008 um 10:27 schrieb Johan Compagner:
that one is really strange.
It looks like a concurrency issue but pages cant be accessed by
multiply
threads at once.
For example if you place a breakpoint at one of these breakpoints
And you just do 2 request in your browser does it get to that place
twice? I
guess not
Maybe the code to get the page lock has a loop that it isnt synced
completely correctly and that 2 request that come in
at exact the same time can both go further..
But does JMeter does that? Does JMeter do multiply request for the
same
session at the same time?
I thought it has X number of sessions and then did 1 request per
session
johan
On Fri, Jun 20, 2008 at 10:10 AM, Peter Ertl <[EMAIL PROTECTED]>
wrote:
I would love to see 1.3.4 but I see some serious issue still open
(and I
don't know how bad it is)
https://issues.apache.org/jira/browse/WICKET-1693
seems to affect not only 1.4 but 1.3 as well. I just did a test on
current
wicket 1.3 and got another bunch of NullPointerExceptions under
stress.
I uploaded test-project-for-wicket-1.3.tar.gz for reproducing this
issue on
1.3 (without generics).
you need IDEA and jmeter to use it (hopefully that's not a big
problem)
I don't know exactly why this concurrency issue happens but in heay-
load
environments it could be a blocker :-(
Cheers
Peter
Am 19.06.2008 um 14:06 schrieb Frank Bille:
[0]: https://issues.apache.org/jira/browse/WICKET-1646
[1]: https://issues.apache.org/jira/browse/WICKET-1667
On Thu, Jun 19, 2008 at 2:03 PM, Frank Bille <[EMAIL PROTECTED]>
wrote:
I was just about writing a similar mail. To my understanding, the
two[0][1]
regression/showstopper issues as been fixed. I don't know of any
other
issues, which needs to be fixed before.
It's nice of you to do the build, but I actually have real,
dedicated
spare
time on saturday, so perhaps you have some social relations that
needs
attention :-)
Frank
[0]
[1]
On Thu, Jun 19, 2008 at 1:50 PM, Martijn Dashorst <
[EMAIL PROTECTED]> wrote:
I can spare a couple of cycles to build 1.3.4, but I thought there
were some regressions? Is 1.3.4 in releasable state?
Martijn
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
