This content has been marked as final.
Show 4 replies
-
1. Re: SEC_ERROR_BAD_DATABASE
807567 Oct 6, 2003 5:26 PM (in response to 807567)we are facing the same problem. The error keeps popping up under heavy load or when we shutdown one of our 2 webservers and go with only one.
Diane, were you able to get to the bottom of this problem.? -
2. Re: SEC_ERROR_BAD_DATABASE
807567 Jan 14, 2004 2:29 AM (in response to 807567)We are seeing the same thing in a websphere/j2ee environment. We were thinking maybe a rainbow issue, any ideas?? -
3. Re: SEC_ERROR_BAD_DATABASE
807567 Jan 14, 2004 2:32 AM (in response to 807567)Error receiving connection (SEC_ERROR_BAD_DATABASE - Problem using certificate or key database)
This is our log error, we then back up an actuate queue waiting for requests to be answered and loose stability. -
4. Re: SEC_ERROR_BAD_DATABASE
807567 Feb 9, 2004 5:22 PM (in response to 807567)Try to add a TMP file env. variable in the iWS start up script.
e.g. TMP=/tmp/abc; export TMP
make sure this file is web server user (e.g. nobody or nsuser) writeable.
Then restart the web server.
It will allow the NSS to create a temp disk file when the in memory cache is all used up during heavy loads with all the user certificates. We have seen it throws this error during heavy loads, e.g. 1000+ users with digital certificate authentication. Then you will need to restart the web server to make it work again.