Background Process Execution timeout 300

[robert_altenstraer]

Hello all

maybe someone can help me....

We run the Background Process Execution for Auto Close Message by the System since one week, but the messages doesn´t close.

at first I found out that the job doesn´t run, related on the Paramter in the VM ( note: 1958664 )

now the job run and there is also no error in the ME Pod ( Background Process Execution ( activity SY999 ) ),  but in the nwa log I can see errors:

Messages:

com.sap.engine.services.dbpool.exceptions.BaseSQLException: The transaction ( JTA Transaction : 4762471 ) has timed out after "300" seconds. The specified timeout is "300" seconds.

The transaction ( JTA Transaction : 4762471 ) has timed out after "300" seconds. The specified timeout is "300" seconds. The only outcome is rollback.

[EXCEPTION]
com.sap.engine.services.dbpool.exceptions.BaseSQLException: The transaction ( JTA Transaction : 4762471 ) has timed out after "300" seconds. The specified timeout is "300" seconds.
at com.sap.engine.services.dbpool.wrappers.ResultSetWrapper.throwExcIfTxHasTimedOut(ResultSetWrapper.java:973) ...

our playground:

Base 6.1.4.52 Counter 2015093006

MSSQL DB

does anyone know where this timeout is set ??  I checked the notes therfore and in the transaction timeout there is a "0"   and this is ok for MSSQL

( note: 1825121 )

Thanks for help

Robert

[sergiy_katerinich · Accepted solution]

Hi Robert,

Please check #1 and #6.1 of Note 1825121.

Regards,

Sergiy

[alexander_teslyuk]

For similar cases in future , you may also find useful this blog about SAP_JTA timeout parameter:

Br, Alex.

[alexander_teslyuk]

Hello Robert,

Did you restart Netweaver after setting transaction timeout to 0? If yes, could you try to clean the message logs tables as per SAP Note 2091068 - 'Delete of Message Log tables'. It may improve the performance, so the background job will simply not execute for 300 seconds.

Br, Alex.