Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Infor / Lawson Platforms
S3 Systems Administration
High volume transactions causing LSF9 problems
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Zac Shields
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
5211
People Online:
Visitors:
332
Members:
0
Total:
332
Online Now:
New Topics
Lawson S3 HR/Payroll/Benefits
Post Tax Benefit Plan Table
11/14/2024 9:16 PM
Hi, totally new to Laswon. I have a repor
Lawson S3 Procurement
ED501 Error: Map 850 not supported by /law/c15vda/lawson/test10/edi/bin/laws_out_91
11/12/2024 3:47 PM
Tried runnning ED501 and getting the atathced erro
Lawson S3 HR/Payroll/Benefits
Error
11/6/2024 9:54 PM
When I try to enroll a retiree in 72.1 health plan
Infor ERP (Syteline)
Syteline: New Data Maintenance Wizard (Error) Need help
11/1/2024 4:24 PM
Hi, I need help with an error on syteline while us
Dealing with Lawson / Infor
Implementing Lawson v10 with Cerner Surginet, Case Cart Picking, and Quick Adds for the OR
10/29/2024 4:20 PM
Hi Everyone, I am wondering if there is any org
Lawson S3 HR/Payroll/Benefits
Canada Tax Calculation (Federal and Provincial) Issue
10/23/2024 5:00 AM
Initially, we had problem with CPP2 calculation is
Lawson S3 HR/Payroll/Benefits
CA Section 125 401k Plan
10/22/2024 10:13 PM
Does anyone have any recommendations on how to fac
S3 Systems Administration
Running AC120 deleted records from ACMASTER table
10/22/2024 3:40 PM
We recently ran the AC120 as normal and somehow it
Lawson S3 Procurement
RQ13 Approval Info
10/17/2024 2:12 PM
When a Requisition is approved on RQ13, what table
S3 Customization/Development
Read and Write CSV file COBOL
10/9/2024 2:53 PM
Does anyone have a quik example of a program that
Top Forum Posters
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
Forums
Filtered Topics
Unanswered
Unresolved
Announcements
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
Infor / Lawson Platforms
S3 Systems Administration
High volume transactions causing LSF9 problems
Please
login
to post a reply.
6 Replies
0
Subscribed to this topic
27 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
Dr House
New Member
Posts: 3
9/14/2009 7:19 PM
We are currently running LSF9, MSP5 w/patches on AIX, in a 4 server environment (web/ldap/oracle/app). We are able to replicate a problem with the Lawson environment not being able to process transactions appropriately. After pushing through lots of tranactions (potentially 50k+) in a short time frame (24 hours), our system begins to behave in a extraordinary fashion - but not in a good way.
Basically we have a script that feed lajs batch jobs (jqsubmit -w), but the batch job submission will hang until a command like `jqstatus -a` (or any flag you wish including -h help!) will the transaction return to the command line. This is an indefinite hang - so until another command run against the job scheduler, the jqsubmit will hang, this can mean 5 mins or as long as 2-3 days. Note that we are using the -w parameter when submitting the job.
Has anyone ever heard of this before?
Dr House
New Member
Posts: 3
9/14/2009 7:22 PM
Let me modify my previous statement that we are using wtsubmit (as jqsubmit -w doesn't exist). We also use `jobload -c filename` - both have the same behavior.
Jimmy Chiu
Veteran Member
Posts: 641
9/15/2009 3:26 PM
I would increase the heap size under laconfig to see if that helps.
You may have reached the limit of your server hardware also. What's the spec on your app server?
Dr House
New Member
Posts: 3
9/15/2009 3:43 PM
I will try that out, we've tried many different things to avoid this problem, adding memory, lawson patches (app and env), oracle patches, websphere patches, tivoli patches, but none have proven to reduce the frequency or avoid the problem.
We have our partitions running on a p595 the app server has 16 processors with 65GB of RAM, the DB server has 8 processors & 32 GB of RAM. We currently run websphere, but don't use the portal - our users still come in from the LID.
Thanks for the help, I will try upping the heap size and try to break the server again. I'll report back what I find (positive or negative).
Jimmy Chiu
Veteran Member
Posts: 641
9/15/2009 3:52 PM
You also mentioned that you have a script to feed lajs batch job. Maybe slow down the script and put some delay in between each submit?
Also i would assume with the amount of transaction you are processing, your app server and db server are on multiple fiber connections? Reducing the network latency or delay may help the situation also.
Norm
Veteran Member
Posts: 40
9/15/2009 4:41 PM
Sounds like you're real problem is with LAJS since it appears you're using wtsubmit to submit batch jobs. We do something similar, but on a much smaller scale. Ours probably only submits a couple thousand jobs in a 24 hour period.
We're not experiencing that perticular proble, but we'll have a problem where some of our jobs simply abort after zero or one second elapsed time. It's almost os if lajs loses track of the process and then kills it. Very weird.
I'm not a big fan of LAJS, I don't think it was built to handle volumes of 'automatically' submitted jobs. But that doesn't really help you does it? You say that running something like a jqstatus command frees up the block. Can you use cron (or a similar process) to submit a jqstatus command every minute or so to see if that helps LAJS stay unfrozen?
John Henley
Posts: 3353
10/3/2009 10:07 PM
Since this is all running in batch/LID,etc. websphere shouldn't really play a part...it really sounds like you are experiencing a resource/memory leak.
Have you looked at basic environment settings, such as ladb.cfg?
It could be something really simply (trust me, I've seen crazier stuff) like someone sent the INSERTBUFSIZE really high in the ORACLE file, and forgot to set it back down.
Please
login
to post a reply.