You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 21, 2024. It is now read-only.
Hi Xipki, i would like to implement a right pattern in case of restart hsm necessary.
I saw that, after i restarted hsm, i received this error on next use Unknwon mechanism with code: 0x0000000080000384
Which should be a right pattern ?
Is there a method to check module state ? So i could try to check state before perform operations.
If there is a specific exception, i could try to manage exception and launch reinit module (should i finalize and initialize in this case ?)
i could try to use getInfo() to detect if module state is no good ?
Should i shutdown and restart application completely ?
The text was updated successfully, but these errors were encountered:
Hi Xipki, i would like to implement a right pattern in case of restart hsm necessary.
I saw that, after i restarted hsm, i received this error on next use
Unknwon mechanism with code: 0x0000000080000384
Which should be a right pattern ?
The text was updated successfully, but these errors were encountered: