nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

OutOfMemoryError without 'useOldAliasMetadataBehavior=true'

remo

Hi 
 
I work with BIRT 2.5.2 
 
Due to BIRT bug #212387 (<a class='bbc_url' href='https://bugs.eclipse.org/bugs/show_bug.cgi?id=212387'>https://bugs.eclipse.org/bugs/show_bug.cgi?id=212387</a>), we had to use the parameter "useOldAliasMetadataBehavior=true" on all connection URLs to our MySQL DB in the past. 
 
Now that this bug is fixed (which I'm not sure about), I wanted to remove the mentioned parameter in the connection URL. But then all the reports raise an OutOfMemoryError, unfortunately without a stack trace that could give further hints: 
 
java.lang.ClassCastException: java.lang.OutOfMemoryError cannot be cast to java.lang.Exception 
 
To clarify: the execption is thrown in the "Preview" view of the Report Designer and also when the report is deployed in an application. However, in "Edit Data Set" -> "Preview Results" the result set is shown. 
 
In the end, I guess bug #212387 is still not resolved, as Actuate's Maggie Shen says in comment no 24. She says that she will open a new bug which I was unable to find. 
Of course I don't know if that's connected in any way to my OutOfMemoryError. 
 
Thanks for help! 
 
Remo

Find more posts tagged with

Comments

mwilliams

Hi Remo,

If you run it in the web viewer and not in "preview" mode, do you get the same error?

remo

Yes, there's the same error in the web viewer.

btw: On the web viewer welcome page (http://localhost:8080/WebViewerExample/), BIRT reports itself as version 2.5.1, altough it's 2.5.2 - extracted from the birt_runtime-2_5_2.zip...

Remo

mwilliams

Remo,

Are all the engine files and such in your download for 2.5.2? It just says 2.5.1 in the welcome page? Is this correct?

Do other reports work just fine? Just not this one? You might make sure that your MaxPermGenSize is set to a large enough value.

remo

Michael,

For me, it's hard to tell whether all files are for 2.5.2. It's the official download I have here and some plugin directories in fact contain "2.5.2" in their name. Might be just a problem of the welcome page - I don't know.

Some other reports work fine, others don't. I increaded max perm gen space to 256m - still the same error.
Again: The report executes without error, if I add 'useOldAliasMetadataBehavior=true' again. What has changed in bug fix #212387?
I assume it's some kind of transition problem: the report has been designed with 'useOldAliasMetadataBehavior=true' in an earlier version of BIRT but is now executed without 'useOldAliasMetadataBehavior=true' in BIRT v.2.5.2.

Thanks,
Remo

mwilliams

Remo,

Please log a bug for this at http://www.birt-exchange.org/org/resources/bug-reporting/.

You might also try downloading BIRT 2.6 and seeing if the same thing happens to you.