JMS 1.1 Pools Frequently Asked Questions
There are some frequently asked questions about the JMS 1.1 Pools such as when you should shut it down or how the JMS 1.1 service pools impacted when the JMS provider shuts down.
When should you shut down the JMS 1.1 pools?
|You should shut down a pool if...||then...|
|you are using JMS 1.1 services only and the pool is not in use any more.||the business process can shut down the pool once all the business processes have finished and you will not be running the business processes. You will want to disconnect from the JMS provider.|
|you are using the adapters.||Once you have shut down the adapter instance and you do not plan to use it any time soon and want to disconnect from the JMS provider, you can shut down the pool.|
|you plan to edit any of the pool parameters and none of the business processes or adapters are using the pool.||You can shut down the pool before editing parameters, as this is going to result in a new pool. Or you can change the pool name. This results in creating a new pool with a different pool name rather than using the same pool name. You can shut down the old pool at a later point of time.|
- If the JMS 1.1 adapter using a pool is enabled - If an exception occurs, the adapter and pool try to reconnect based on the retry logic. If successful, then it will re-enables or shut down. If the pool connection is shut down, it will need to be manually cleaned up. Otherwise, if the JMS provider is restarted and the adapter is enabled, then the pool will refresh.
- If the adapter has been shut down - If the adapter has been shut down and the pool is still connected (if the pool has not been manually shut down) an exception occurs or the providers goes down, then the pool will be shut down in the background but will still remain active, even though it is in a dead state. If the provider is up and the adapter is re-enabled then the pool will become active again.
How are JMS 1.1 service pools impacted when the JMS provider shuts down?
For JMS 1.1 services, if an exception occurs on the provider's side or if the provider gets shut down, the pool is shut down, and remains in a dead state (which can be manually cleaned up). Once the JMS provider is up, you can run the business process and the pool will become active again.