ERROR: IdentityResourceV3.queryCollection caught exception

Troubleshooting
, ,
#1

Venkata Kishore Babu Bellam

On ForgeRock Access Management Under a realm we have a OUD Identity store, when searching identities getting “Internal Server Error” along with seeing below error message in logs.

o.f.o.c.r.IdentityResourceV3: 2022-05-09 12:38:15,262: Thread[http-nio-8080-exec-5]: TransactionId[5da8cc57-3591-4b1d-885c-8f95db52977d-53879]

ERROR: IdentityResourceV3.queryCollection caught exception

java.lang.NullPointerException: null

I have compared Identity Store with a working not seen any real differences. Any Idea how to fix this issue

image|0x0
image|0x03199×955 126 KB

Venkata Kishore Babu Bellam

1 Like
#2

Hi Venkata, were you able to solve this issue? I’m having the same happening on one of our environments.

Regards,
LG

#3

What error do you get if you look at your Browsers developer tools when you access that page?

What should occur is a call to:
https://openam.example.com/am/json/realms/root/realms/alpha/users?_queryFilter=true&_pageSize=10&_fields=cn,mail,username,inetUserStatus

What you can do with this is if as an example you get a 500 back, then with Message Debug enabled on AM, check your Audit logs. From there the Audit log will have a transaction ID for that request , then check your debug logs for that transaction, this will be all of the request that caused that failure.

What you may see is something like “no operation connections to datastore exist” which means AM can’t connect to DS-Userstore. There could be other issues, like This request ask for ALL users, by default you may only allow say 1000 results.

What’s nice about the transactionid as well is the SAME id will also be in your DS audit logs as well if you need to find out more if it’s a failed search.

If you need help understanding where Audit and debug logs are see:

1 Like