Page History

...

Via the development dashboard there is an easy solution to solve this problem. Select Widgets and then select the Sessions widget. This widget shows a list of your active user sessions per branch. Here can close specific or all user sessions at once.

Reloading configuration

Via the development dashboard, a user is able to press the reload configuration button. This button restarts the entire Blueriq Runtime. All user sessions are destroyed, all Solutions are removed, the database connections are destroyed and the Blueriq Runtime restarts. During the reload, users are unable work with the Blueriq Runtime. Although it could be useful to use this function, application servers like Tomcat, JBoss or Websphere are not always able to clear the memory correctly so it is advisable to restart the application server instead of using the reload configuration function.

Advice on sizing

From our experience a single Runtime could accommodate 10 active modellers in a development environment running on 4GB of memory. When developing with more active developers it’s possible to increase the size of the memory but keep in mind that a restart of the servers will then take longer because the JVM needs to evict the allocated memory. Alternatively, if the teams are developing on completely different and isolated projects it should be considered to setup multiple Runtime environments so each team has its own Runtime environment and size it accordingly.

...