interesting and relevant. As I
mentioned on list, maybe the ConcurrentHashMap will be the answer to not
synchronize the whole getAttribute method.
http://www.theserverside.com/tt/articles/article.tss?l=ScalingYourJavaEEApplications
Concurrency testing of the locationmap throws errors
Concurrency testing of the locationmap throws errors
Key: FOR-1082
URL: https://issues.apache.org/jira/browse/FOR-1082
Project: Forrest
Issue Type: Bug
Components: Locationmap
On Mon, 2008-06-30 at 09:14 -0400, Tim Williams wrote:
On Mon, Jun 30, 2008 at 9:04 AM, Thorsten Scherler
[EMAIL PROTECTED] wrote:svnc
On Mon, 2008-06-30 at 08:34 -0400, Tim Williams wrote:
On Mon, Jun 30, 2008 at 8:12 AM, Thorsten Scherler
...
I reckon in that case, it's either the
On Tue, 2008-07-01 at 09:04 +0200, Thorsten Scherler wrote:
...
I will test the performance
...
Actually with the same test as before the performance is better.
Mainly because before the first results are errors and ruin the average.
Since now we have 0% error the first hits are around
On Tue, 2008-07-01 at 09:25 +0200, Thorsten Scherler wrote:
On Tue, 2008-07-01 at 09:04 +0200, Thorsten Scherler wrote:
...
I will test the performance
...
Actually with the same test as before the performance is better.
Mainly because before the first results are errors and ruin the
On Thu, 2008-01-31 at 15:16 -0500, Tim Williams wrote:
On Jan 31, 2008 1:19 PM, Thorsten Scherler
[EMAIL PROTECTED] wrote:
Hi all,
I am ATM testing the dispatcher with jmeter and concurrent user.
The problem that I encounter is that the locationmap is throwing an
error as soon as
On Mon, Jun 30, 2008 at 7:46 AM, Thorsten Scherler
[EMAIL PROTECTED] wrote:
On Thu, 2008-01-31 at 15:16 -0500, Tim Williams wrote:
On Jan 31, 2008 1:19 PM, Thorsten Scherler
[EMAIL PROTECTED] wrote:
Hi all,
I am ATM testing the dispatcher with jmeter and concurrent user.
The problem
On Mon, 2008-06-30 at 08:05 -0400, Tim Williams wrote:
...
I am ATM playing around and it happens in
LocationMapModule.getLocationMap() but I am not sure how I can prevent
it.
Try making the entire method synchronized instead of just the blocks.
This may not be the end solution but will
On Mon, Jun 30, 2008 at 8:12 AM, Thorsten Scherler
[EMAIL PROTECTED] wrote:
On Mon, 2008-06-30 at 08:05 -0400, Tim Williams wrote:
...
I am ATM playing around and it happens in
LocationMapModule.getLocationMap() but I am not sure how I can prevent
it.
Try making the entire method
On Mon, 2008-06-30 at 08:34 -0400, Tim Williams wrote:
On Mon, Jun 30, 2008 at 8:12 AM, Thorsten Scherler
...
I reckon in that case, it's either the caching or its deeper in the
actual LM/nodes. You could try turning off caching completely and see
if it helps.
Turning caching off does
On Mon, Jun 30, 2008 at 9:04 AM, Thorsten Scherler
[EMAIL PROTECTED] wrote:
On Mon, 2008-06-30 at 08:34 -0400, Tim Williams wrote:
On Mon, Jun 30, 2008 at 8:12 AM, Thorsten Scherler
...
I reckon in that case, it's either the caching or its deeper in the
actual LM/nodes. You could try
Hi all,
I am ATM testing the dispatcher with jmeter and concurrent user.
The problem that I encounter is that the locationmap is throwing an
error as soon as there are concurrent user. :(
I have no clue ATM why that is happening but try
map:match pattern=test
map:generate
On Jan 31, 2008 1:19 PM, Thorsten Scherler
[EMAIL PROTECTED] wrote:
Hi all,
I am ATM testing the dispatcher with jmeter and concurrent user.
The problem that I encounter is that the locationmap is throwing an
error as soon as there are concurrent user. :(
I have no clue ATM why that is
13 matches
Mail list logo
