Welcome to the SRP Forum! Please refer to the SRP Forum FAQ post if you have any questions regarding how the forum works.
RTI TASK SUBMIT not always working
Hi all,
Wondering if anyone else has run into a similar problem to what we've been experiencing here.
We have O4W websites setup for a number of clients. Within the website pages we have a 'download pdf' option for one of the screens where we use something like:
RT_TASK_SUBMIT(,"OUR_PROGRAM",ID_for_program,"")
which creates and returns the PDF file using OIPI that we push to the user using O4WDownload
The problem we are experiencing is that the command has been, fairly often, not firing the process. When I look in the SYSTASKS table, all of the tasks are being added there with the status 'IMMEDIATE' to be launched right away (we aren't using nor want to use a scheduler or what not), but they never get started.
It a*appears* as though the oengines are being launched though, just not calling the task we want it to, so we eventually have too many crashed oengines for the website to work properly either.
Does anyone have any similar issues and a work around?
I will mention we looked at trying the banded report writer, but ended up not being able to use it right now due to how it works with multi values and large text fields not lining up properly without cutting text.
Wondering if anyone else has run into a similar problem to what we've been experiencing here.
We have O4W websites setup for a number of clients. Within the website pages we have a 'download pdf' option for one of the screens where we use something like:
RT_TASK_SUBMIT(,"OUR_PROGRAM",ID_for_program,"")
which creates and returns the PDF file using OIPI that we push to the user using O4WDownload
The problem we are experiencing is that the command has been, fairly often, not firing the process. When I look in the SYSTASKS table, all of the tasks are being added there with the status 'IMMEDIATE' to be launched right away (we aren't using nor want to use a scheduler or what not), but they never get started.
It a*appears* as though the oengines are being launched though, just not calling the task we want it to, so we eventually have too many crashed oengines for the website to work properly either.
Does anyone have any similar issues and a work around?
I will mention we looked at trying the banded report writer, but ended up not being able to use it right now due to how it works with multi values and large text fields not lining up properly without cutting text.