Java.lang.nullpointerexception is being faced for all LDAP users while they login
Hi,
In my AGILE application, very often all the LDAP users while they try to login , they are facing “java.lang.NullpointerException“, we are restarting the AGILE system to solve this issue, is there any other way to solve this, any suggestions for not occurring this issue, please help.
Thanks,
Surya
So this *only* affects users who are logging in using LDAP credentials? And after restarting the Agile application service, it doesn’t happen for a while? Is there any evidence of a specific period of time that it takes for this to happen?
I would open an SR with Oracle. This should not be happening, obviously, but whether it is an issue with LDAP or within Agile, I do not know. And that a restart of Agile fixes it means that something is good (for a period of time) and then it goes south. It is usually that LDAP users always have problems (something is wrong with the link to the LDAP server) or they are always good.
Hello Surya
From what you describe, as Kevin mentions, there could be an intermittent issue with your LDAP server. By the time you restart Agile, that issue is resolved and the problem goes away
We had similar issue once couple of years back. We found that one of the LDAP nodes had an issue. So, whichever user connected to the bad LDAP node had issues logging in
Do you have a stack trace of the exception? If so, please share it
Other option you could try – whenever this issue happens, you could try doing “Refresh users from LDAP” in Java client. See if that works. if that fails, i have seen that it provides better error message
Hope this helps
Hi Kevin/Rchinnia,
Unfortunately I have no logs taken backup when this issue happened, also not checked whether this happened only for LDAP users and not tested with Non-LDAP users, I will share the details when issue happens next time.
But I think there is no problem with LDAP , because with the LDAP log in I am able to login to the Remote servers but not the AGILE.
Is only stdout.log and stderr.log is enough or any web logic server logs I need to check ?
Thanks,
Surya
Hi Surya
Please check weblogic server logs as well. If you tail all the 3 logs when the issue happens, you should see atleast in one of them. Other thing you could do is to have Show console checked in Java and try logging in when the issue happens. You could get the exception there also
Thanks
Raj