Back to bug 1036624
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Boleslaw Dawidowicz | 2013-12-10 08:20:11 UTC | CC | mposolda | |
| Link ID | JBoss Issue Tracker GTNPORTAL-3342 | |||
| Status | NEW | ASSIGNED | ||
| Target Release | --- | 6.1.1 | ||
| CC | bdawidow | |||
| Assignee | prabhat.jha | mposolda | ||
| Target Milestone | --- | ER01 | ||
| Peter Palaga | 2013-12-10 08:20:55 UTC | CC | ppalaga | |
| Target Milestone | ER01 | DR02 | ||
| Peter Palaga | 2013-12-11 17:27:47 UTC | Status | ASSIGNED | ON_QA |
| Dominik Pospisil | 2014-01-31 14:22:05 UTC | Status | ON_QA | ASSIGNED |
| Dominik Pospisil | 2014-01-31 15:04:07 UTC | Status | ASSIGNED | VERIFIED |
| Jared MORGAN | 2014-02-11 00:50:43 UTC | Doc Text | Cause: The SecureRandom is portal service used for generating random numbers for "security" purposes. The bootstrap of this service needs generation of seed | |
| Doc Text | , which might be quite expensive task in some environments. This is an issue especially in environments with more portal containers because SecureRandom was started separately for each portal container (So for example | |||
| Doc Text | , if you have deployment with 5 portal containers | |||
| Doc Text | , there are 5 SecureRandom instances which needs to be bootstrapped at portal startup) Consequence: Startup of portal might take quite a big amount of time due to this Fix: SecureRandom service has been configured to be shared between all portal | |||
| Doc Text | containers (So for example if we have 5 portal containers, we would still have just 1 instance of SecureRandom service) Result: Improvement in startup time for environments with many portal containers | |||
| Doc Text | Cause: The SecureRandom is portal service used for generating random numbers for "security" purposes. The bootstrap of this service needs generation of seed, which might be quite expensive task in some environments. This is an issue especially in environments with more portal containers because SecureRandom was started separately for each portal container (So for example, if you have deployment with 5 portal containers, there are 5 SecureRandom instances which needs to be bootstrapped at portal startup) Consequence: Startup of portal might take quite a big amount of time due to this Fix: SecureRandom service has been configured to be shared between all portal containers (So for example if we have 5 portal containers, we would still have just 1 instance of SecureRandom service) Result: Improvement in startup time for environments with many portal containers | The SecureRandom service is a portal service used for generating random numbers for security purposes. The service requires a seed for each instance of the service. It was discovered that because a separate SecureRandom service was required for each portal instance, installations containing many portal instances may have been experiencing slower boot times as a result of individual seed creation for each SecureRandom bootstrap. The fix implements SecureRandom as a shared service between all portal instances, which results in an improved startup time for installations containing many portal instances. | ||
| PnT Account Manager | 2019-01-01 03:40:51 UTC | QA Contact | dpospisi | tkyjovsk |
Back to bug 1036624