Page History
...
- By default a JOC Cockpit REST Web Service is configured to use up to 10 connections from the pool. As a rule of thumb 1 connection can be shared by approx. 3 simultaneous users.
- Adjust this setting to the max. number of connections required for sharing between simultaneous users of the JOC Cockpit.
- Note that connections will be disconnected and returned to the pool if they are not used for a longer time.
- Additional connections are used by JS7 Services.Consider Consider the total number of connections allowed when setting up your JS7 database.
- Some DBMS products by default limit the number of connections per user account and process. JOC Cockpit is running from a single process.
- Oracle by default limits the connections according to the formula: (1.5 * number of processes) + 22
| JOC Cockpit Component | Min. Connections | Max. Connections | Configurable | Comment | ||
|---|---|---|---|---|---|---|
| JS7 - REST Web Service API | 10 | unbounded (default: 10) | yes | Recommendation: no. of simultaneous users / 3. | ||
| 1 | 1 | no | ||||
| JS7 - Cleanup Service | 10 | 10 | no5 | unbounded (default: 5) | yes | Configuration via JS7 - Settings |
| JS7 - History Service | 1 | number of connected Controller Instances | no | Any Controllers connected to a JOC Cockpit Instance are counted. | ||
| JS7 - Monitor Service | 3 | 3 | no | 2 connections for monitoring JS7 - Monitoring. 1 connection for notifications. JS7 - Notification. | ||
| Total: 20 |
Hibernate allows one out of a number of Connection Pool implementations to be chosen.
...
Overview
Content Tools