-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
None
-
-
+
Currently the AMQ drainer pod starts a very standard and default KahaDB persistence adapter.
If however the customer runs a broker that uses the multi-KahaDB persistence adapter or that configures KahaDB to use a different journal size than the default 32 MB, then this may prevent the drainer broker from functioning properly.
The AMQ drainer should support additional non-standard persistence adapter configurations.
- is blocked by
-
CLOUD-2940 activemq openshift discovery agent does not support start/stop/start sequence
- Closed
- is related to
-
CLOUD-2895 AMQ readinessProbe only peeks in /proc/net/tcp6 when present, ignoring contents of /proc/net/tcp
- Verified
- relates to
-
CLOUD-2716 AMQ drainer pod only works with standard KahaDB configuration
- Closed