Unfortunately, that doesn't seem to be the case. I had to restart the 2nd Jetty server and then it was able to see the find the key that was added by 1st Java jetty process.
Wasn't underlying token/device getting modified by the 1st java/Jetty process ? if so, wouldn't those created token objects be visible throughout all sessions from all others processes/applications.
We tried this scenario on SafeNet HSM instead of NSS and as expected, sessions of respective Java process does get updated. In our opinion, seems like there's something in NSS that we probably need to work with to get this to work.
Please do correct me if I'm thinking wrong. Would truly appreciate help.