Lajs is failing. - LawsonGuru.com - LawsonGuru.com Forums

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3291
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1372
Roger French	1315
mark.cook	1244

Srini Rao

Veteran Member

Posts: 149

3/20/2013 6:17 PM

We are on windows 2008 virtual. LAJS fails almost every day and we need to start it manually.

The environment service laserv-lawtest is installed and started.
The lase program is enabled and started.
The ladb program is enabled and started.
The lainetd program is enabled and started.
The lajs program is enabled but not started.
The latm program is enabled and started.
The larmi program is disabled.
The lawarmagent program is disabled.
The pfrmi program is enabled and started.
The pfem program is enabled and started.
The pfbpm program is enabled and started.
The pfsch program is enabled and started.
K:\linte\launt\JPS_LAWSON> startlajs
lajs has been started.
K:\linte\launt\JPS_LAWSON>

I did checked the ladb.log file and I do see that it failed to connect to GENDB.

*** begin msfdb2000 error message ***Wed Mar 20 13:36:50 2013 - program 'GENUSERPROFILEIMPL', User 'OSID:NT00000001', RMId '' Driver Version '9.0.1.11.231 2012-09-04 22:00:00'

FINDMIDRNGDBREC() error on file 'USER' in 'GEN'

FindBegRngSqlRec(dbo."R_USER", 0)

CMsfCSRSqlStatement::First(BNLF0001I00_V40) -

SQL Server Error Code: 0, Source: Microsoft OLE DB Provider for SQL Server, Description: Connection failure

--- Start of Key area dump ---

"USERNAME"=NT0000329f

--- End of Key area dump ---

*** end msfdb2000 error message ***

Jimmy Chiu

Veteran Member

Posts: 641

3/21/2013 12:12 PM

What is the row count in your QUEUEDJOB table in GEN database?

Srini Rao

Veteran Member

Posts: 149

3/21/2013 1:31 PM

It's 16366.

Joe O'Toole

Veteran Member

Posts: 314

3/21/2013 1:33 PM

We have a similar problem since moving to Windows 2008 R2 64 (not virtual) and LSF 9.019. Every time we reboot LAJS startup fails. We are getting an "unable to communicate with database" error. We also have to stop and restart LATM otherwise Portal form inquiries fail. We have added delays and dependencies to the services but nothing seemed to help. Lawson support was not able to help so in the end I coded a script to restart these automatically after system reboot. It is still annoying that they are not starting as expected however. For what it's worth we have about 41,000 records in our QUEUEDJOB table.

Srini Rao

Veteran Member

Posts: 149

3/21/2013 2:07 PM

I tried that, I removed the Lawson from start-up and started manually from DOS prompt. I will having the issue. We are still working Lawson professional services and still no luck.

Jimmy Chiu

Veteran Member

Posts: 641

3/25/2013 12:47 PM

What's your lajs.log file size?

Joe O'Toole

Veteran Member

Posts: 314

3/25/2013 1:10 PM

Mine is about 1.9 MB what would the relevance of that be?

Kwane McNeal

Veteran Member

Posts: 479

3/25/2013 1:34 PM

Joe, I believe Jimmy asked that question, because since Lawson uses signed 32-bit pointers for log files, if your file had reached 2GB, then lajs wouldn't be able to append to it and would likely abort. This is the current behaviour of latm.

I am noticing that at a UNIX client I work with I have some environments where lajs terminates in a similar fashion, and it seems to be related to internal network wait getting info from lase, before and after it makes a call to ladb. I wasn't able to fully track it down, as I don't have the source code for ladb, but I'd check the following:

1) Is lase tuned correctly? Since ESP9, you have had to bump up the JVM from 768M to 2048M (GENDIR/java/command/lsserver.properties)
2) Are the database and application server in the same VLAN (preferrably the same VLAN *and* subnet), if not, you may be introducing delays by adding routing overhead to packets.
3) Are you using Broadcom network adapters (if you're virtual, does your ESX host use them)? Major issues with some models and firmware releases. I have counseled several clients on this as of late.

I have seen all of these exhibit the issues at hand.

Kwane

Joe O'Toole

Veteran Member

Posts: 314

3/25/2013 2:49 PM

We never bumped up from 768M but have not noticed any other problems related to this (we are not using LSF security). What benefit would i expect to see from the extra VM? We are on the same subnet. I think we are using Broadcom cards, but again not seeing day to day issues other than the services starting.

Kwane McNeal

Veteran Member

Posts: 479

3/25/2013 3:07 PM

The bump up isn't related to Lawson Security usage. The additional memory ensures that lase has the heap needed to process security requests for the whole system. Unlike Env 8.x, LSF 9's 'lase' process handles security for *both* LAUA and LS ('ladb' performed this in Env 8.x).

You could see any and all of the following:
1) initial connections to GEN being killed or timed out. This would include calls made by server processes such as latm and lajs, especially if you have scheduled recurring jobs.
2) hanging CGI calls (particularly xauthen.exe) when using the Service Centers
3) Batch jobs taking an inordinate amount of time to run.
4) Hanging access to high volume and/or usage to online forms

Kwane

Kwane McNeal

Veteran Member

Posts: 479

3/25/2013 3:10 PM

...and on the Broadcom NICs, the newer ones seem to be ok, though I noticed slower performance with them than non-Broadcom NICs that were of a previous generation.
The older ones definitely have issues.

Contact me offline if anyone needs more info.

Kwane

DougAB

Advanced Member

Posts: 28

3/25/2013 3:57 PM

Kwane,

We are experiencing some slowness issues and it may be related to our Broadcom cards. Can I contact you for additional discussion on this? What's the best way, email or phone?

Kwane McNeal

Veteran Member

Posts: 479

3/25/2013 4:04 PM

Doug,
Generally, either would be fine, but in this case call me 505-433-7744, as this won't take much time. I am on a call now, but should be off by 2pm EDT

Kwane

Jimmy Chiu

Veteran Member

Posts: 641

3/25/2013 5:24 PM

Joe, i run the same setup as you do. Never experienced lajs not starting here. I am on LSF9.0.1.9 and Win2008R2x64 also (non virtual). My dev environment runs on virtual and no lajs issue also. I do have JVM heap size sets to 1024MBmin/2048MBmax. Also, I have my windows non-interactive heap size under laconfig sets to 1024.

For troubleshooting, I would do a cold boot. Wait for all processes finished loading and the system went into idle. Then, startlaw. See if lajs would fail to load then...

As of Boardcom nic... my personal practice, disable them. I can't put in an intel nic fast enough whenever i prep a server.

Balaji

Advanced Member

Posts: 20

3/26/2013 11:57 AM

Did you check the event viewer in the OS?