SAML_SSO: java.lang.IllegalArgumentException: Ids should not be null

0
ERROR - SAML_SSO: java.lang.IllegalArgumentException: Ids should not be null 2022-03-11T00:00:13.507679 [APP/PROC/WEB/0]       at com.mendix.basis.component.InternalCoreBase.retrieveId(InternalCoreBase.java:771) 2022-03-11T00:00:13.507688 [APP/PROC/WEB/0]       at com.mendix.basis.session.PersistentSession.<init>(PersistentSession.scala:29) 2022-03-11T00:00:13.507691 [APP/PROC/WEB/0]       at com.mendix.basis.session.PersistentSession.<init>(PersistentSession.scala:37) 2022-03-11T00:00:13.507705 [APP/PROC/WEB/0]       at com.mendix.basis.session.SessionFactory$.createPersistentSession(SessionFactory.scala:80) 2022-03-11T00:00:13.507710 [APP/PROC/WEB/0]       at com.mendix.basis.session.SessionManagerBase.getSessionById(SessionManagerBase.java:234) 2022-03-11T00:00:13.507791 [APP/PROC/WEB/0]       at com.mendix.basis.component.InternalCoreBase.getSessionById(InternalCoreBase.java:217) 2022-03-11T00:00:13.507814 [APP/PROC/WEB/0]       at com.mendix.core.Core.getSessionById(Core.java:1468) 2022-03-11T00:00:13.507819 [APP/PROC/WEB/0]       at saml20.implementation.security.SessionManager.evaluateActiveSessions(SessionManager.java:554) 2022-03-11T00:00:13.507836 [APP/PROC/WEB/0]       at saml20.implementation.security.SessionManager$1.run(SessionManager.java:164) 2022-03-11T00:00:13.507839 [APP/PROC/WEB/0]       at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) 2022-03-11T00:00:13.507884 [APP/PROC/WEB/0]       at java.base/java.util.concurrent.FutureTask.runAndReset(Unknown Source) 2022-03-11T00:00:13.507900 [APP/PROC/WEB/0]       at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) 2022-03-11T00:00:13.507907 [APP/PROC/WEB/0]       at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 2022-03-11T00:00:13.507946 [APP/PROC/WEB/0]       at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 2022-03-11T00:00:13.507954 [APP/PROC/WEB/0]       at java.base/java.lang.Thread.run(Unknown Source)
asked
2 answers
2

Hi, Not sure if it is still relevant.  

 I also encounter the same issue. But as you see the stacktrace it says evaluateActiveSessions and this run in a thread to find an active session of a user.  

If someone deletes an application User manually from DB directly while the user is still login (Ofcourse don't do that with Mendix Live DB) It tries to find this session id for a user does not present in DB.  

I restored this user manually again and restarted the application.
So in short Restart of application helped to stop this thread running in the loop.  

answered
0

I had this issue well. My case was that I renamed a column in the domain model so the template didn't know to what column to map the data to. The solution was to run the Mx Model Reflection again and correct the mapping in the template.

answered