nkuebelbeck
VIP Member
We use BSSV as a wrapper to execute JDE BSFNS. There are some of these function that use JDE Cache. In the instance that a COK goes zombie or is recycled, the clients executing BSSV's start getting 500 errors. This is because the association of that user to its COK is gone. The bssv can be instructed to auto-reconnect, meaning get a new COK. That only works when the BSFNs called by the BSSV DO NOT USE JDE CACHE(see DOC 1202613.1)
Currently the only way to get the user back up and running is to restart the BSSV service. (pain point)
I am wondering if anyone has found away around this?
Currently the only way to get the user back up and running is to restart the BSSV service. (pain point)
I am wondering if anyone has found away around this?