killing looping lacobrts processes in LSF9 help

Frank,
I feel it is due to LSF9.0 security issue .See same eror you getting with Security turn off or turn security debug flag on and see which security rule causing this.

Thanks,
Subba

I would do this and see if it will help just temporarily.

Edit your %lawdir%\system\latm.cfg

OPENTIMEOUT 600
LOOPTIMEOUT 30

A reboot is required after the changes. Then wait and see if it will pop the errors.

Posted By Jimmy Chiu on 07/13/2010 12:48 PM
I would do this and see if it will help just temporarily.

Edit your %lawdir%\system\latm.cfg

OPENTIMEOUT 600
LOOPTIMEOUT 30

A reboot is required after the changes. Then wait and see if it will pop the errors.

If I'm not mistaken, a reboot is not required. tmcontrol -rc should reinitialise those settings.

Posted By Jimmy Chiu on 07/13/2010 12:48 PM
I would do this and see if it will help just temporarily.

Edit your %lawdir%\system\latm.cfg

OPENTIMEOUT 600
LOOPTIMEOUT 30

A reboot is required after the changes. Then wait and see if it will pop the errors.

If I'm not mistaken, a reboot is not required. tmcontrol -rc should reinitialise those settings.

We tried changing OPENTIMEOUT and LOOPTIMEOUT and this didn't solve the problem. We applied 2 JT's and the "killing looping lacobrts" message went away, but we now have a new error....see below. The users get on and test and it took 24hrs to get it to fail and get this new message. Any ideas?

TIA
Frank
INFORMATION FROM THE LATM.LOG

Program Code = PR05 , DataArea/DataID = HRPROD
Tue Jul 13 15:20:25 2010: ERROR: Stopped due to a signal 9
Tue Jul 13 15:20:25 2010: SIGNAL: Kill

Wed Jul 14 09:12:07 2010: latm (PrcTPCrash): Received death notification of lacobrts, Uid=14, Pid=9943
Wed Jul 14 09:12:07 2010: Program Code = HR11 , DataArea/DataID = HRPROD
Wed Jul 14 09:12:07 2010: ERROR: Stopped due to a signal 13
Wed Jul 14 09:12:07 2010: SIGNAL: Write on a pipe with no one to read it

lacobrts timed out waiting for OPEN message
lacobrts timed out waiting for OPEN message
lacobrts timed out waiting for OPEN message

We tried turning off security and still get the errors.

Posted By FrankH on 07/14/2010 09:59 AM
We tried changing OPENTIMEOUT and LOOPTIMEOUT and this didn't solve the problem. We applied 2 JT's and the "killing looping lacobrts" message went away, but we now have a new error....see below. The users get on and test and it took 24hrs to get it to fail and get this new message. Any ideas?

TIA
Frank
INFORMATION FROM THE LATM.LOG

Program Code = PR05 , DataArea/DataID = HRPROD
Tue Jul 13 15:20:25 2010: ERROR: Stopped due to a signal 9
Tue Jul 13 15:20:25 2010: SIGNAL: Kill

Wed Jul 14 09:12:07 2010: latm (PrcTPCrash): Received death notification of lacobrts, Uid=14, Pid=9943
Wed Jul 14 09:12:07 2010: Program Code = HR11 , DataArea/DataID = HRPROD
Wed Jul 14 09:12:07 2010: ERROR: Stopped due to a signal 13
Wed Jul 14 09:12:07 2010: SIGNAL: Write on a pipe with no one to read it

lacobrts timed out waiting for OPEN message
lacobrts timed out waiting for OPEN message
lacobrts timed out waiting for OPEN message

What JTs did you apply?  We are seeing this same error in out latm log.

What version of Lawson are you on?  Are you on AIX or Windows?  Does it only happen in HR11?

Did Lawson have you trace the program? compile HR11

qcompile -T prod hr hr11

compile invokes

lstinvk -qT prod hr11

When the program times out the trace will be within the lacobrts log.

Usually I would set the looptimeout to 60 seconds so you don't have to sit there and wait.

I'm guessing Lawson has already taken you through this process, but wanted to throw it out there if they have not.

We are planning to upgrade to MSP5 and ESP7 , did Lawson addressed this issue?

Anyone have any updates on this issue? We are getting this issue about once a week mostly on HR11 and PA52

We are having a similar issue with an upload to LP31 - only in test but it is preventing us from moving forward with this user on Lawson security - when we get this error lawson security hangs hangs the entire system - it kills lacobrts - we have to manually kill every process to restart - did you get a solution?

Can anyone please help me on how to enable and disable the security flag? I am using Lawson Insight Desktop(LID) version 7.3.3.0.
One of my customize screen starts clocking if I update my stuff through it.
The problem and logs are just similar to the one that has been sent/pasted in the original query.
Appreciate your response!