Hey Jason,
it turns out the cause of this problem is that I have a war file that is
never unpacked, and in the method ViewerAttributeBean.processReport(),
there's a line
if ( lastModifiedOfDesign != -1L)
which checks the modified date of the rptdesign file, unfortunately in this
case, this will always return false because the design file is not a valid
file system file, it's packed inside the war file, so whatever is in that if
statement never gets executed, which means the rptdocument file is never
removed, and later on after the soap call to the BirtViewerReportService, a
re-execution of the report is called only if the rptdocument is not present,
so in this case, a re-execution of the report is never made.
Sorry that's a very messy explanation, hope you understand what I just typed
Anyway, shall I still log a bug?
"Jason Weathersby" <jasonweathersby@xxxxxxxxxx> wrote in message
news:g3gge5$jti$2@xxxxxxxxxxxxxxxxxxxx
Robert,
Are you getting the error when using the sample db? Or is it just the
reports that use the connection pool?
Jason
Robert I. Lin wrote:
Ok, I will file a bug, but meanwhile I need to fix this bug on my own or
else I can't ship my product, any suggestions on how I can approach this?
BTW, just curious why the released jar files don't have line numbers in
them, this basically makes debugging impossible, may I suggest adding the
line numbers back for future releases so that people can debug and
understand what is happening.
"Jason Weathersby" <jasonweathersby@xxxxxxxxxx> wrote in message
news:g3drtt$4jm$2@xxxxxxxxxxxxxxxxxxxx
Robert,
Can you log a bugzilla entry for this?
Jason
Robert I. Lin wrote:
Hi Jason,
for some reason it stopped working again, my reports failed to refresh,
but I tried your suggestion of giving a different __document parameter
each time, and that works, is there any suggestion on what to do from
this point on?
Thanks.
Robert
"Robert I. Lin" <Robert.Lin@xxxxxxxxxxxx> wrote in message
news:g2pdp8$8td$1@xxxxxxxxxxxxxxxxxxxx
Hey Jason,
that didn't work either, but what did work is I switched to using the
tag libraries instead of calling the servlet directly, and that works.
I have no idea why that is ...
Anyway, thanks for your help again.
Robert
"Jason Weathersby" <jasonweathersby@xxxxxxxxxx> wrote in message
news:g2m5jc$bqf$2@xxxxxxxxxxxxxxxxxxxx
Robert,
Can you try adding __document=c:/tmp/firsttry.rptdocument to the url
the first time you run it and the then specify another document the
second time you run it? This is not a fix but a test. Also could
you post your web.xml from the deployed viewer?
Jason
Robert I. Lin wrote:
Another thing might be - since /run works /frameset doesn't, my
webapp is deployed inside a war file, and that includes the BIRT
servlets, so if the runtime is trying to generate .rptdocument
files, then it wouldn't be able to since all the files are packed in
a war without ever unzipping. Does that make sense?
"Robert I. Lin" <Robert.Lin@xxxxxxxxxxxx> wrote in message
news:g2ka3f$of4$1@xxxxxxxxxxxxxxxxxxxx
I don't see to get the same caching problem when I use the /run
servlet, but then I don't get the tool bars and navigation bars,
and also I have another problem where the drillthroughs in my
reports don't work ....
"Robert I. Lin" <Robert.Lin@xxxxxxxxxxxx> wrote in message
news:g2k86u$pin$1@xxxxxxxxxxxxxxxxxxxx
Hey Jason,
I tried using __overwrite I still see the same problem. I'm using
version 2.2.1.1, one possible cause I see is that I use a
connection pool underneath via driver bridge, maybe I'm forgetting
to initialize something?
Robert
"Jason Weathersby" <jasonweathersby@xxxxxxxxxx> wrote in message
news:484D9C2D.700@xxxxxxxxxxxxx
Robert,
This should not be the case. What version of BIRT are you using
and try adding &__overwrite=true to your url.
Jason
Robert I. Lin wrote:
Hi,
I'm running my report using the /frameset servlet and it seems
that my report results is cached, if I try to run it again with
different input parameters, I will still get the result I got
the first time I ran that report.
Any idea how to get around this? Thanks.