|
| Re: BIRT Servlet Stress Test Problem [message #531419 is a reply to message #531248] |
Tue, 04 May 2010 19:52   |
|
Can you set the max perm size on WS to at least 256 and run the test
again? The connection should be getting closed.
-XX:MaxPermSize=256M
Jason
On 5/4/2010 6:23 AM, Melvin Mah wrote:
> I am currently performing a stress test to see how much the BIRT report
> servlet can take by launching 5-10 reports simultaneously. At around
> this time, the machine hosting the servlet gets slower and slower
> particularly if a SQL query used in one of the reports returns a lot of
> data queried from the database.
>
> From what I've look around and from what other people say about this
> and some say that it's due to the perm / heap size defined in Weblogic,
> while some said that it's that maybe the DB connection for the report is
> not closed.
>
> Two things that I hope to get some answers:
>
> 1. Does the close method in IRunAndRenderTask also closes the DB
> connection to once the query returns its results?
>
> 2. Is this whole thing actually got to do with how much PermSize / Heap
> size that is defined in the Weblogic service?
>
>
|
|
|
|
| Re: BIRT Servlet Stress Test Problem [message #531690 is a reply to message #531449] |
Wed, 05 May 2010 19:00 |
|
Melvin,
If the connection is a jdbc connection and not setup with JNDI it should
be getting closed. Can you open bug to diagnose the issue?
Jason
On 5/4/2010 10:24 PM, Melvin Mah wrote:
> Hi Jason,
>
> The machine that we're testing has the MaxPermSize set to 512 since the
> RAM's capacity is 2GB. But if it's a 512, will it still be that slow? If
> I try to set it to 1024, the service will not start at all.
>
> I'm confused but sorry to ask again whether if IRunAndRenderTask
> .close() also closes the DB connection once the report rendering process
> has already finished?
>
> Thanks
|
|
|
|
Powered by
FUDForum. Page generated in 0.02661 seconds
] 
Search
Help
Register
Login
Home
