Questions About ISS Config Option "iss.autoprovision.user.exclude.list"
Last updated on APRIL 30, 2018
Applies to:Oracle Communications Indexing and Search Service - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Questions about ISS Config Option "iss.autoprovision.user.exclude.list"
Q1: What is the distinction between the ability to exclude a user from auto-provisioning (with "iss.autoprovision.user.exclude.list" option) versus the ER 22806058 to exclude indexing on a per account basis?
Q2. After excluding a user account using the "iss.autoprovision.user.exclude.list" config parameter, setting the account to status "I" and then deleting it, why has this user account been auto-provisioned again?
was set to:
iss.autoprovision.user.exclude.list = jsmith
Then did: issadmin.sh refresh
Then did: /var/tmp$ issadmin.sh --setstate I --user jsmith
Thursday, February 15, 2018 12:06:52 PM PST
Thursday, February 15, 2018 12:07:10 PM PST
/var/tmp$ issadmin.sh --deleteaccount --user jsmith
Thursday, February 15, 2018 12:07:44 PM PST
Thursday, February 15, 2018 12:10:38 PM PST
Now there are no connections from ISS for that account and the CPU is getting better. BUT...
Why did this go back into the B state?
/opt/sun/comms/jiss/etc$ issadmin.sh --listbrief | grep jsmith
B jsmith u30443 mail.abc.com h1 20180215201703 20180215201629 -1 IMAPonly
After setting it to status "I" again:
/opt/sun/comms/jiss/etc$ issadmin.sh --setstate I --user jsmith
Thursday, February 15, 2018 12:59:46 PM PST
Thursday, February 15, 2018 01:04:32 PM PST
and then observed this in the /gcs/app/mail/glassfish3/glassfish/domains/domain1/logs/server.log log:
What happens to these events for a user in state I? Are they dropped?
Q4. This user (jsmith) is in the "I" state now, but of course the backend is still sending events and there is a max 5000 in the queue for a user...(i.e. iss.jmqconsumer.queue.limit (default: 5000) - JMQConsumer event queue limit. )
Is that a per-user max 5000? Is that 5000 for this user interfering with other users?
Q5. We are getting errors about that user being at that max because it isn't processing the events because the user is in "I" state.
What other problems are being caused on the ISS side because of that user being at thatQ 5000 max?
Q6. Is there a work-around option to make the backend Messaging Server not send events to ISS for this user?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms