I think we discussed this already a while back but can't remember whether it was in here or in our chat channel.
The latency you mention is rather tied to OPSS than WLS itself and I'm not aware that you can fiddle with that. OPSS does cache its data...prime example 2412508.1 or 1588912.1
Thanks, Christian. I navigated to 1588912.1 and found this note (see below) at the bottom, along with the suggested workaround, which is basically to restart the entire WLS domain. Since that is not really a great option for us, I'll live with the delay. THANK YOU for the reply.
Note: Due to the OPSS policies caching at WebLogic Domain layer, it might take some time for the policies modification to be effective. If you want to avoid this delay, stop and restart the complete WebLogic Domain
Yeah I didn't want to suggest restarting it all - alas that's what it seems to come down to.