Process timeout issue

pbrad

Hi,

I have a report that is called from the second rule of a process. The first rule of the process brings up a non-persisted form that sets the report parameters.

The report is fairly complex with a number of subtotals and other calculations. It runs fine in V4 if you run the report against 1 week of data. However if you run it against several weeks of data it fails. It shows the 'Sending Data' animated graphic three or four times and then shows a small dialog box that says 'connection failed'.

I am guessing that this process is just timing out and I need to adjust a timeout parameter in one of the new js files? If so, which one? If not, what do I do? If I login using the V3 .do url it works properly no matter what date parameters are entered.

Thanks,
Pete

christopherb

Thank you Pete I was going to post this same issue. I don't know if this is related but also running a report that contains a large amount of data the operation to create the report does not complete.

pbrad

Same issue when trying to export a business object with 10,000 records. It seems to me that it must be a timeout setting somewhere that needs to be higher.
Pete

aware_support

Can you please send us a BSV or describe how to reproduce the problem?

pbrad

Hi,

Giving you a sample bsv is not a problem but you need a large database in order to duplicate the problem. If the process of displaying a report or exporting a business object takes more than about 20 seconds, it will throw the 'connection failed' error. PM me if you would like to do view the error on my system using the same method that we did last week.

Pete

aware_support

This has been fixed in build 1136

pbrad

Works perfectly now.

Thanks!
Pete

rbross

Maybe this is broken again or I am missing something simple?

I call a process from a query it opens a non-persistent BO with ENTERNEW to get report parameters Then calls a 2nd process to find the records based on parameters passing the non-persistent BO
Rule #1 find the records Rule #2 uses DISPLAY DOCUMENT 'Report Name' there over 2000 records returned, following the Log viewer it is finding all the records in batches of 1000 and shows it is calling the report but it never display the completed report?

have to be missing something simple. I really don't want to have to create a separate report for each sort option using its own query based on the sort option selected.

Rule#1 in process

If CHARS_FROM_LEFT(ReportParameters.InvMasterSort,1)=1
THEN
FIND ALL InventoryMaster ORDER BY InventoryMaster.sc_IC_Code ASC, InventoryMaster.IM_Desc ASC

ELSE IF CHARS_FROM_LEFT(ReportParameters.InvMasterSort,1)=2
THEN
FIND ALL InventoryMaster ORDER BY InventoryMaster.IM_Desc ASC

ELSE IF CHARS_FROM_LEFT(ReportParameters.InvMasterSort,1)=3
THEN
FIND ALL InventoryMaster ORDER BY InventoryMaster.IM_IndexNo ASC

Rule #2 in Process

IF CHARS_FROM_LEFT(ReportParameters.InventoryMasterReport,1)=1 AND CHARS_FROM_LEFT(ReportParameters.InvMasterSort,1)=1
THEN
DISPLAY DOCUMENT InventoryMaster_Listing_ByCode_Desc

ELSE IF CHARS_FROM_LEFT(ReportParameters.InventoryMasterReport,1)=1 AND CHARS_FROM_LEFT(ReportParameters.InvMasterSort,1)=2
THEN
DISPLAY DOCUMENT InventoryMaster_Listing

ELSE IF CHARS_FROM_LEFT(ReportParameters.InventoryMasterReport,1)=1 AND CHARS_FROM_LEFT(ReportParameters.InvMasterSort,1)=3
THEN
DISPLAY DOCUMENT InventoryMaster_Listing

Jaymer

if you think its related to a timing/time out issue (the original post), then modify your query to TAKE BEST 1
and try it.
Or add a WHERE to find a small # of recs.
Does it still not print anything?

rbross

It works if you do a FIND and the records returned are less than 1000. If you do a FIND ALL then it does not work.
The records returned from the FIND all just over 2200.
If you do DISPLAY DOCUMENT 'Report Name' USING 'QueryName' then it just opens a pick one or More list and you have to select the records.
For now, the workaround is to duplicate the report and create a query for each sort you want and use a separate query for each report so it sorts the way the user has selected from the report parms.

BobK

rbross wrote
following the Log viewer it is finding all the records in batches of 1000 and shows it is calling the report but it never display the completed report?

I am just guessing here, but maybe the problem is that AwareIM is trying to process multiple batches.

Can you try adding the following to your FIND
IN BATHES OF 3000 (or some number greater then the expected number of records to be found)
That way everything will happen in 1 batch

bondicoffee

I have a scenario where I have to process 30000 records.
I search the record and invoke a subprocess to update the record in a batch of 1. While session gets timed out as I have set the session for an hour, I need the process to run independently of the browser session. Is there any way I can do this?

rocketman

I had a similar issue where the process(es) took so long that AIM timed out. I did find however that the process did continue running and completing on the server. My workaround was to put the results into a temporary (persisting) table which I could then call up when I next logged on. My 1st process begins by checking to see if there's anything in the temporary table and deleting anything that's there.

My only concern with this approach is what it's doing within MySql as my understanding is that MySQL is not very good at recovering the space used by deleted items

For completeness, I have tried getting the process to run IN BACKGROUND but because process 1 was constantly calling process 2, that never worked, and in any event in one of my processes where it DID work, AIM never put the results on screen - it just told me the process had finished, but there was no way to view the results

BLOMASKY

Guys, while I have no idea what your business logic is, it would seem to me that a stored procedure would be a LOT faster than processing 30K records one at a time. SQL is set based and generally takes about the same amount of time to process 1 record as it does to process 10,000. (assuming you do have good indexes for your where clause and any sorts. Did you investigate having Aware call a SP for this?

Bruce