| Out of Memory Error [message #251599] |
Tue, 07 August 2007 16:59  |
Eclipse User |
|
|
|
Originally posted by: cjw5014.gmail.com
Hi everyone,
I have a report that was in 2.1.2 and I am converting it into a 2.2.0.
In 2.1.2 the report successfully returned and displayed 3685 rows from
the database with no errors. I have verified this by copying the logged
query BIRT used to generate the report and running it in my database
control center. Both the control center and 2.1.2 returned the same
total rows. When I changed the report over, BIRT would run out of
memory with as low as 2000 rows. The report did not display until I
lowered the limit to 1000. Both reports are being run on the same
machine with the same JVM settings. Does anyone have any ideas on what
the issue is here? Does BIRT 2.2.0 take almost 4 times the amount of
memory for 1 row as 2.1.2 did or could something else be going on?
Thanks for any assistance.
-Chris
|
|
|
|
|
|
|
| Re: Out of Memory Error [message #255889 is a reply to message #255881] |
Thu, 20 September 2007 22:21  |
| Eclipse User |
|
|
|
Jennifer,
I read this and immediately came up with the following possible
responses (tounge-in-cheek).
1/ Do you think a 600-page report is a problem for the BIRT runtimes or
a problem with the report design?
2/ You are aware that SQL has SUM and AVERAGE functions to aggregate
data, aren't you? People who want a large amount of detail should be
given read access to the database and an SQL tutorial. Reports are for
management types whose attention span is generally limited to a page and
a half (when sober).
3/ If one of my minions sent me a 600-page report, I'd print it out
(single-sided), walk into his office, and beat him to death with it (if
it was one of my bosses, I'd simply send a response that I'm looking at
it immediately and I've put on hold all my productive work for the six
weeks it's going to take to analyse it).
Not having a go at you or anything like that. It's just that it's
drilled into us in the early stages of report design that brevity is one
of the most important qualities of a report.
Cheers,
Al.
J Jones wrote:
> I have the same problem. A report that created 600 PDF pages in BIRT
> 2.1 now runs out of memory in BIRT 2.2. Where do I put these
> parameters? In the eclipse.ini file? Right now I'm just trying to run
> the reports in Eclipse and using the preview tab on the BIRT report editor.
>
> Thanks,
> Jennifer
>
> Jason Weathersby wrote:
>> Brian,
>>
>> I thought this was set automatically in the osgi configuration.
>> Did this clear up your memory problem. I have been using this setting
>> for months.
>>
>> Jason
>>
>> Brian Kuhn wrote:
>>> Have those settings been reliable for you?
>>>
>>> I didn't stop having OOM's until I just grabbed all I could in one shot:
>>>
>>> -vmargs -Xms1024m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=256m
>>>
>>> This has been the case for me for the Actuate 2.1.2 and the Open
>>> Source 2.2.0 releases.
>>>
>>> Regards,
>>> Brian
>>>
>>>
>>>
>>> Jason Weathersby wrote:
>>>> Chris,
>>>>
>>>> Can you log a bugzilla entry for this. This should not be the case.
>>>> Also can you try these vm settings, although they should already be
>>>> in osgi config file:
>>>>
>>>> -vmargs -Xmx256M -XX:MaxPermSize=128M
>>>>
>>>> Jason
>>>>
>>>> Chris wrote:
>>>>> Hi everyone,
>>>>>
>>>>> I have a report that was in 2.1.2 and I am converting it into a
>>>>> 2.2.0. In 2.1.2 the report successfully returned and displayed 3685
>>>>> rows from the database with no errors. I have verified this by
>>>>> copying the logged query BIRT used to generate the report and
>>>>> running it in my database control center. Both the control center
>>>>> and 2.1.2 returned the same total rows. When I changed the report
>>>>> over, BIRT would run out of memory with as low as 2000 rows. The
>>>>> report did not display until I lowered the limit to 1000. Both
>>>>> reports are being run on the same machine with the same JVM
>>>>> settings. Does anyone have any ideas on what the issue is here?
>>>>> Does BIRT 2.2.0 take almost 4 times the amount of memory for 1 row
>>>>> as 2.1.2 did or could something else be going on?
>>>>>
>>>>> Thanks for any assistance.
>>>>> -Chris
|
|
|
| Re: Out of Memory Error [message #256452 is a reply to message #255881] |
Thu, 27 September 2007 09:49 |
| Eclipse User |
|
|
|
Originally posted by: jasonweathersby.alltel.net
Jennifer,
Can you try BIRT 2.2.1 which should be out this week?
Jason
J Jones wrote:
> I have the same problem. A report that created 600 PDF pages in BIRT
> 2.1 now runs out of memory in BIRT 2.2. Where do I put these
> parameters? In the eclipse.ini file? Right now I'm just trying to run
> the reports in Eclipse and using the preview tab on the BIRT report editor.
>
> Thanks,
> Jennifer
>
> Jason Weathersby wrote:
>> Brian,
>>
>> I thought this was set automatically in the osgi configuration.
>> Did this clear up your memory problem. I have been using this setting
>> for months.
>>
>> Jason
>>
>> Brian Kuhn wrote:
>>> Have those settings been reliable for you?
>>>
>>> I didn't stop having OOM's until I just grabbed all I could in one shot:
>>>
>>> -vmargs -Xms1024m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=256m
>>>
>>> This has been the case for me for the Actuate 2.1.2 and the Open
>>> Source 2.2.0 releases.
>>>
>>> Regards,
>>> Brian
>>>
>>>
>>>
>>> Jason Weathersby wrote:
>>>> Chris,
>>>>
>>>> Can you log a bugzilla entry for this. This should not be the case.
>>>> Also can you try these vm settings, although they should already be
>>>> in osgi config file:
>>>>
>>>> -vmargs -Xmx256M -XX:MaxPermSize=128M
>>>>
>>>> Jason
>>>>
>>>> Chris wrote:
>>>>> Hi everyone,
>>>>>
>>>>> I have a report that was in 2.1.2 and I am converting it into a
>>>>> 2.2.0. In 2.1.2 the report successfully returned and displayed 3685
>>>>> rows from the database with no errors. I have verified this by
>>>>> copying the logged query BIRT used to generate the report and
>>>>> running it in my database control center. Both the control center
>>>>> and 2.1.2 returned the same total rows. When I changed the report
>>>>> over, BIRT would run out of memory with as low as 2000 rows. The
>>>>> report did not display until I lowered the limit to 1000. Both
>>>>> reports are being run on the same machine with the same JVM
>>>>> settings. Does anyone have any ideas on what the issue is here?
>>>>> Does BIRT 2.2.0 take almost 4 times the amount of memory for 1 row
>>>>> as 2.1.2 did or could something else be going on?
>>>>>
>>>>> Thanks for any assistance.
>>>>> -Chris
|
|
|
Powered by
FUDForum. Page generated in 0.57606 seconds
Home