Discussions
Categories
Choose a Product
THRUST SERVICES
CORE APPS
CE PRODUCTS
...
Quick Links
POPULAR
HELPFUL TIPS
Groups
My Links
FOR SIGNED IN MEMBERS:
Back to website
Home
Developing Analytics Applications
Frameset servlet very slow
Migrateduser
<p>By looking around the Internet, I have seen this topic before, but nothing seems to offer a specific answer. I am running birt-viewer along with a web app on two machines: A test machine and a live machine. I'm using Tomcat as the app server. On the test machine, the viewer runs as expected - I just access the frameset link and I get the little animated "in progress" display for a few seconds and then the paginated report pops up. On the live server, I get the start of the page ("BIRT Report Viewer" heading and the green bar with the six icons on the left hand side) but no report for a long time - several minutes. No progress indicator at all.</p>
<p> </p>
<p>The machines look to be identical:</p>
<p> </p>
<p>Tomcat version: 7.0.55</p>
<p>Java version: 1.8.0_31-b13</p>
<p>birt-runtime version: 4.4.1</p>
<p>Linux: Mint 17 (kernel 3.13.0-24-generic - 64-bit) (Mint is a Ubuntu derivative)</p>
<p> </p>
<p>The live server (that doesn't work) is standalone and has 8 gig of RAM. The test machine (that runs fine) is actually running in a VMware partition with 4gig of RAM.</p>
<p> </p>
<p>The resource stats from the Tomcat Complete Server Status page show that the resources available on the live machine are higher than the resources on the test machine.</p>
<p> </p>
<p>While looking around for others with the same problem, I found a note that said that if you replace "frameset" with "run" it would work right away. I tried that, and sure enough -- it does. But, I need to use frameset for both pagination as well as exporting options (not to mention the fact that I want to understand why apparently identical environments behave differently).</p>
<p> </p>
<p>I saw other notes that said their problem was related to a Java version that was too old (Java 6.something, I believe). That is clearly not my problem. I was running Java 7u65 or so before and when it didn't work, I just upgraded to the latest rev from Oracle.</p>
<p> </p>
<p>I have no idea where to look. The viewer appears to be acting like something that has to wait for a timeout before it proceeds. Has someone seen and solved this problem? Is there some way to see some important vitals within Tomcat or birt-viewer so that I can get to the bottom of this?</p>
<p> </p>
<p>thx,</p>
<p>Vince</p>
Find more posts tagged with
Comments
There are no comments yet