Re: Concurrency testing of the locationmap throws errors

2008-06-30 Thread Thorsten Scherler
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

Re: Concurrency testing of the locationmap throws errors

2008-06-30 Thread Tim Williams
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

Re: Concurrency testing of the locationmap throws errors

2008-06-30 Thread Thorsten Scherler
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

Re: Concurrency testing of the locationmap throws errors

2008-06-30 Thread Tim Williams
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

Re: Concurrency testing of the locationmap throws errors

2008-06-30 Thread Thorsten Scherler
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

Re: Concurrency testing of the locationmap throws errors

2008-06-30 Thread Tim Williams
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

Problem with pdf generation with odt entry

2008-06-30 Thread Cyriaque Dupoirieux
Hi, I think that there is a problem of compliance between the pdf plugin and the odt plugin. The pdf plugin does not find images with the following error : [Fatal Error] :-1:-1: Premature end of file. WARN - No ImageReader found for