10.5 Integration server is giving 500 status code

Recently we have migrated out Integration server from 10.1 to 10.5, post that we started our rest API testing and we are facing some unusual behaviour. Every 30-35 mins IS server is giving 500 http error code. And we could see below error in WMError log in the backend.

at com.webmethods.portal.portlet.wm_xt_staticrole.provider.StaticRoleProvider.isMemberOfRole(StaticRoleProvider.java:365)
at com.webmethods.portal.service.dir.impl.DirPrincipalProvider.groupRoleQuickLookup(DirPrincipalProvider.java:398)
at com.webmethods.portal.service.dir.impl.DirPrincipalProvider.getRoleMembership(DirPrincipalProvider.java:335)
at com.webmethods.portal.mech.dir.impl.PrincipalMechanics.getRoleMembership(PrincipalMechanics.java:180)
at com.webmethods.portal.bizPolicy.command.dir.GetRoleMembership._getRoleMembership(GetRoleMembership.java:162)
at com.webmethods.portal.bizPolicy.command.dir.GetRoleMembership.getRoleMembership(GetRoleMembership.java:136)
at com.webmethods.portal.bizPolicy.biz.dir.impl.PrincipalBizPolicy.getRoleMembership(PrincipalBizPolicy.java:97)
at com.webmethods.sc.directory.impl.DirectorySession.getRoleMembership(DirectorySession.java:396)
at com.wm.app.b2b.server.cds.CDSUserManager.hasMember(CDSUserManager.java:284)
at com.wm.app.b2b.server.cds.CDSUser.hasMember(CDSUser.java:85)
at com.wm.app.b2b.server.ACLGroup.matches(ACLGroup.java:280)
at com.wm.app.b2b.server.ACLGroup.allow(ACLGroup.java:205)
at com.wm.app.b2b.server.ACLManager.allow(ACLManager.java:455)
at com.wm.app.b2b.server.ACLManager.allow(ACLManager.java:445)
at com.wm.app.b2b.server.cds.CDSUser.isAdministrator(CDSUser.java:95)
at com.wm.app.b2b.server.InvokeState.setSessionUser(InvokeState.java:1020)
at com.wm.app.b2b.server.HTTPState.processHeader(HTTPState.java:353)
at com.wm.app.b2b.server.Dispatch.processHeader(Dispatch.java:275)
at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:407)
at com.wm.util.pool.PooledThread.run(PooledThread.java:134)
at java.lang.Thread.run(Thread.java:748

Could somone help me resolve this issue.

Thanks in advance.

Hi Shabeer,

unfortunately the stack trace is incomplete.

Can you provide the complete stack trace please?
Please check the session log as well as the server.log if there are more informations.

Check the ACL definition associated with your REST service as well as the CentralUsers Management configuration in IS.

Regards,
Holger

Hi Holger von Thomsen ,

Could you please let me know what stack you are looking for.

Regards,
Shabeer Honnur

Hi Shabeer,

the first line of the stack trace usually indicates the Error or Exception which has caused the stack trace to be logged.

One more thing to check:
Were the databases updated to current schema version during the migration?

Regards,
Holger