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)
BIRT infinite loop
osuwariboy
Hello everyone,<br />
<br />
I have a really weird problem with one of my BIRT report. I'm using Eclipse Indigo with BIRT 3.2.23. My report's calling a stored procedure that works perfectly when run directly from the database. However, something strange happens when it's called in BIRT. When I go to refresh the dataset, it goes on and on and on and never stops. When I checked the process list in MySQL, I was able to see the procedure being called (which is normal) and then returning its results... and then being called <em class='bbc'><strong class='bbc'>again</strong></em> and returning its results <em class='bbc'><strong class='bbc'>again</strong></em> and so on and so forth. So my only question is: WTF!?!?!?!?!?!?!?!<br />
<br />
Anyone has any idea what on earth's going on? Why is BIRT feeling the need to call the procedure in an infinite loop to <em class='bbc'><strong class='bbc'>refresh its dataset!?!?!?!</strong></em><br />
<br />
Any pointer would be greatly appreciated, thanks in advance,<br />
<br />
Osu<br />
<br />
P.S. BTW, sorry for the lack of details... but I don't really have all that many to give to begin with. There's no error message or even any debugging info to give since no error are actually generated, it just freezes over until I manually kill the process in MySQL.
Find more posts tagged with
Comments
bgbaird
Osu, you might want to ensure that the stored proc does not have any other stored procs nested inside. That has given me fits before.
osuwariboy
Thanks for the advice bgbaird, but there are no nested calls in my stored procedure. I do however have two datasets which are both calling the same stored procedure (with slightly different parameters, mind you). Could that be what's causing the problem? I mean it might be that this is what happens:
1) First dataset starts loading itself by calling the stored procedure
2) Second dataset tries loading itself, thus overriding the call to the procedure made in 1)
3) First dataset sees its call's been overriden and thus starts everything over... by recalling the stored procedure and thus overriding the call made in 2)
Rince and repeat until someone kills the process. Anyway, I have no idea if this is truly what happens, but any sort of help would be greatly appreciated
.
Thanks in advance.
Osu
