Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Intelligence (Analytics)
RCP-app very slow on 64Bit w2k8-server
Lea
Hi,<br />
<br />
I implemented our application that contains the birt plugin on an Ubuntu-64Bit with a 64-openjdk version 1.6.0_20. That works perfectly. On a windows xp 32bit jvm 1.6.0_21, everything works fine. But on a w2k8-server with 64Bit-jdk 1.6.0_21 or 1.6.0_26 it runs very slow after using the preview. The 'original' designer from BIRT's website works fine on all windows platforms.<br />
<br />
I implemented my own preview menu action, because I wanted to have that in a menu. I start the webviewer with:<br />
<br />
<pre class='_prettyXprint _lang-auto _linenums:0'>
HashMap<String, Object> options = new HashMap<String, Object>();
options.put(WebViewer.SERVLET_NAME_KEY, "frameset");
options.put(WebViewer.FORMAT_KEY, WebViewer.HTML);
options.put(WebViewer.RESOURCE_FOLDER_KEY, ReportPlugin.getDefault().getResourceFolder());
options.put(WebViewer.MAX_ROWS_KEY, ViewerPlugin.getDefault().getPluginPreferences().getString(WebViewer.PREVIEW_MAXROW));
options.put(WebViewer.MAX_CUBE_ROW_LEVELS_KEY,ViewerPlugin.getDefault().getPluginPreferences().getString(WebViewer.PREVIEW_MAXCUBEROWLEVEL));
options.put(WebViewer.MAX_CUBE_COLUMN_LEVELS_KEY, ViewerPlugin.getDefault().getPluginPreferences().getString(WebViewer.PREVIEW_MAXCUBECOLUMNLEVEL));
options.put(WebViewer.SHOW_PARAMETER_PAGE_KEY, Boolean.toString(parameterDlgWanted));
WebViewer.display(path, options);</pre>
<br />
After that call my application is no longer usable since it runs very, very slow. It shows the preview after a long time and when I close it, the whole application remains slow. <br />
<br />
What am I doing wrong? Are there any recommended JVM-Parameters for memory that I'm missing? Why is it not running on 64Bit-JVM/Windows.<br />
<br />
Thanks,<br />
<br />
--Lea
Find more posts tagged with
Comments
Lea
Found a solution. I do not know why the other JVMs did not ran into that exception but as soon as I added the console debug output I got a MemoryException.
Adding that so the JVM params worked:
-XX:MaxPermSize=512m -Xms40m -Xmx1024m