Slowness with logging in

We are new to Infor-Lawson and are still in the build phase of the system. All users are reporting slowness when logging into Mingle. Once logged in, the performance is not an issue but from initial login page to actual landing page - it's about 1 minute delay. Has anyone else experienced this and if so, can direction be given on what all would need to be checked to resolve it? Thank you!

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

unknown

Hi! A while ago we had this same issue where users took a long time for the login portion. Resolution for us: Are you LDAPbound? If so, are you bound to port 389 on your domain controller? If so, you'll want to redo your ldapbind and bind to the port called the global catalog port (default: 3268, I think?). Let me know if you have questions about this. Hope this helps. Lenny

mbozenik

I have the same issue from time to time. I wasn't aware of the global catalog port. But I had to restart WebSphere to get to it work. Sometimes I have to stop Lawson as well. Stop WAS and stoplaw and then startlaw and start WAS. Sometimes it takes two or three tries. We are LDAPbound. Again I'll have to research the global catalog port setting, but we can still get it working it just take a few restarts. Note you'll need to close all browser sessions to confirm it's working correctly. That's because in our case the login session is cached some how and closing all browser sessions clears it. Because like you said once you are in it's ok, it's just getting through that initial connection.

unknown

See KB1657502. This helped reduce our login time from 40 seconds to 6-8 seconds.

mbozenik

I worked through that KB a couple of times over that past year. Typically our logins are around 6-8 seconds. The issue is during restarts after applying patches or over a period of time(sometimes days, weeks, or months) the users start to see the 60 to 80 second login times. It's fine one minute and then the next, 60 to 80 seconds. No errors are logged. Something just goes bad with WAS. Sometimes a restart of WAS resolves it and sometimes we have to restart WAS and Lawson.

unknown

We've seen that as well. We do monthly restarts and patch applications. If the system comes up lagging then we restart the node with the issue, or bounce server.

Copyright © 2025 Infor. All rights reserved.