Intermittent connections issues - Login Failed

deanna-plant

We are receiving Login Failure errors on our flows that are connecting to our main connectio on an intermittent basis.  When testing the connection in IPAdmin it is failing on the File Access, Infor Lawson and System Command configuration tabs.  The JDBC (SQL) connection remains successful. We thought the issue was caused by our certification not have the Subject Alternative Name but have since fixed that, thought it was working but now is not working again.

Anyone else have this type of behavior?  If so, what was the cause/resolution?

Thank you!

russel-cornelson

There have been many of these types of issues reported over the years,  typically this is caused by the LSF Environment, or LSF's web server being at capacity or experiencing some type of issue.   Process Flow is trying to call the LSF Environment and when it can't get through for any reason it fails and reports the issue.

That problem on the LSF environment could be pretty much anything,  but its always good to make sure that your process flow environment is configured in a way to as friendly as possible to the LSF environment,  aka making sure that you have S3 Connection Pooling enabled.


Without S3 pooling,  every call to the LSF Environment will actually make about 4 calls..


Example
1. to make a change on an LSF form
/servlet/Router/Transaction/Erp  

2. Since pooling not enabled we dont pass a C.LWSN cookie; therefore we get redirected to security.
/ssoconfig/SSOCfgInfoServlet

3. SSOCfgInfoServlet will tell us which system is primary auth so we then make
/sso/SSOServlet   to log in

4.  Finally we remake the call
/servlet/Router/Transaction/Erp


So your webserver, without pooling needs to make 4 calls against your webserver.  Versus .... 1 call for most calls,  and only makes the 4 calls when the session expired, or establishing a new pool.




Bottom line:   Ensure pooling is enabled, it alleviates stress on your LSF Environment.    Even if something else (addins/userload) is causing the issue,  by keeping pooled connections you reduce the likelihood of it affecting your system.

Finding True Root Cause:   Analysis and investigation of Lawson System Foundation application servers/web servers/security logs.