Topic
  • 2 replies
  • Latest Post - ‏2013-05-27T05:51:55Z by mandreas
mandreas
mandreas
95 Posts

Pinned topic BIRT: Stuck Reports & schedule loops

‏2013-05-02T07:42:17Z |

Hi

We use different scheduled BIRT-reports for our weekly reporting. Recently some of the generated PDFs are delivered 2 to 5 times.

In the errorlog there are such message

'A thread running a report seems to be stuck. Details: threadName=[maximo-ReportRunThread-5], report=[total_ticketinfo_schedule_site.rptdesign], app=[SR], user=[ID], scheduledJob=[true], startTime[Tue Apr 30 20:18:40 CEST 2013], stuck for [824 seconds'

How can I prevent automatically retries?

TSRM 7.2.1

Thanks for help

Andreas

  • SubratM
    SubratM
    9 Posts
    ACCEPTED ANSWER

    Re: BIRT: Stuck Reports & schedule loops

    ‏2013-05-25T21:46:10Z  

    By default it is  assumed that a SQL will complete in few minutes. When a SQL runs for more than or the report renders for more than 15 minutes, Maximo thinks that the server which was executing the report has gone down so the report is rescheduled to be executed.  The stuck thread message here means the reportSQL is taking more than 15 minutes to run.

    The solution is to increase the LOCKINTERVALINMINUTES parameter of REPORTLOCKRELEASE Crontask. Make it larger than the expected time the report will run.

  • SubratM
    SubratM
    9 Posts

    Re: BIRT: Stuck Reports & schedule loops

    ‏2013-05-25T21:46:10Z  

    By default it is  assumed that a SQL will complete in few minutes. When a SQL runs for more than or the report renders for more than 15 minutes, Maximo thinks that the server which was executing the report has gone down so the report is rescheduled to be executed.  The stuck thread message here means the reportSQL is taking more than 15 minutes to run.

    The solution is to increase the LOCKINTERVALINMINUTES parameter of REPORTLOCKRELEASE Crontask. Make it larger than the expected time the report will run.

  • mandreas
    mandreas
    95 Posts

    Re: BIRT: Stuck Reports & schedule loops

    ‏2013-05-27T05:51:55Z  

    Thanks - increasing the parameter helps.

    Additionally I've optimized the selects.