users gets a timeout errror , but the document is saved!!!!!

[Former Member]

IN BSP app , the user gets a timeout errror , but the document is saved in the backgrund process.

The timeout is controllled by icm/keepalive_timeout.

The user gets a timeout error on the browser.But the process started by him still runs and creates the document.

But the process started doesnt get killed even after the "rdisp/plugin_auto_logout" paramter has been exceeded.

So even though the document has been created , users goes in further to create a fresh document assuming the earlier one timed out .

IS there a way wehere we can kill a process after n seconds >???

This is wat i did for it .

So what I did was start a counter at the start of the create claim method , and just before the COMMIT WORK statement (which actually stores the claim to the database) , end the counter .

Check if the difference is greater than the time-out parameter set in SMICM.

iF greater than don't "COMMIT" but do a ROLLBACK and just log the entry which we could use for further processing.

[raja_thangamani]

You can not kill the process once its started.Either increase the timeout or here is the work around:

Write all database update logic in UPDATE TASK (CALL FM in UPDATE TASK ), then after all database updates,

Check if the difference is greater than the time-out parameter set in SMICM, if yes just ROLLBACK, if not call COMMIT WORK, at this time all ur changes will be writtern from VBLOG into Database.

Hope this helps.

Raja T

[Former Member]

This is in a mehtod of a controller class

1. Fill all structures for BAPI CALL

2. Call BAPI BAPI_CREATE

3. Commit work (Twice)

commit work and wait.

call function 'BAPI_TRANSACTION_COMMIT'

exporting

wait = 'X'

importing

return = wa_return2.

4. If a type of doc., then create sub equipment if one

Plus commit work and wait.

5. If a type of doc., entry in sub assemble table

6. Create file attachments , all attachmnets

7. modify sap table from l_add_data. (for some z FIELDS)

8. Call web service

Some more function calls in update task Plus commit work and wait after each call

modify table from table ver2_item.(Not recommended SAP practiCe)

{exit method without any commit}

This are the steps , how to optimizze