[jira] Resolved: (AMQ-673) A way to Pool embedded brokers so that if multiple spring contexts are being used which define an embedded broker, only the first one starts up the broker.

[ https://issues.apache.org/activemq/browse/AMQ-673?page=all ] Hiram Chirino resolved AMQ-673: --- Resolution: Fixed If you now use: broker1 and broker2 will be the same bean instance. if the config value was diffe

[jira] Assigned: (AMQ-673) A way to Pool embedded brokers so that if multiple spring contexts are being used which define an embedded broker, only the first one starts up the broker.

[ https://issues.apache.org/activemq/browse/AMQ-673?page=all ] Hiram Chirino reassigned AMQ-673: - Assign To: Hiram Chirino > A way to Pool embedded brokers so that if multiple spring contexts are being > used which define an embedded broker, only the fi

[jira] Created: (AMQ-673) A way to Pool embedded brokers so that if multiple spring contexts are being used which define an embedded broker, only the first one starts up the broker.

A way to Pool embedded brokers so that if multiple spring contexts are being used which define an embedded broker, only the first one starts up the broker. --

[jira] Commented: (AMQ-660) Add support for MaxDB

[ https://issues.apache.org/activemq/browse/AMQ-660?page=comments#action_35951 ] Johan Hallgren commented on AMQ-660: OK, I got an answer back from one of the MaxDB devs. Apparently, the issue is a known bug, that is fixed in the latest 7.5 version of i