I figured it out. The short answer is no. A longer description of how the
network connectors work can be found on my blog where I dumped my notes on
the whole thing: http://www.christianposta.com/blog/?p=242
-
http://www.christianposta.com
--
View this message in context:
http://activemq.2283
One more bit of information. This problem only exists on durable
subscriptions to topics. Regular topics seem to work just fine.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/durable-subscription-reconnect-tp4593687p4601337.html
Sent from the ActiveMQ - User mailing lis
Additional piece of information: The reconnect does seem to work with queues
properly and is only a problem with topics.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/durable-subscription-reconnect-tp4593687p4600675.html
Sent from the ActiveMQ - User mailing list archive
have a peek at the source:
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/
For the process time:
Time capture at:
org.apache.activemq.broker.region.RegionBroker#send
Statistic update at:
org.apache.activemq.broker.region.RegionBroker#preProcessDispatch
Statistic impl:
or
agree, this is a problem. I think we can remove the dependency on
geronimo-jta_1.0.1B_spec from activemq-core altogether, need to do a
build to validate.
in any event, as it is already an optional dependency, there is no
good reason to include it in activemq-all.
can you raise a jira to track this.
