Hi all, I'm experiencing some reliability issues with ActiveMQ in G 2.1.4 in combination with the application I'm working on now. Basically I see the same three issues described in GERONIMO-4257[0]. Unfortunately I can't reproduce the issues reliably, but still I'm not comfortable to put G into production at its current state.
[0] https://issues.apache.org/jira/browse/GERONIMO-4257 As a stop gap solution before G 2.2 is stable I'm considering upgrading ActiveMQ in G 2.1.4. Running with a stand alone broker using ActiveMQ 5.2 seems to better, but I'm not entirely confident that we won't run into any unintended classpath issues while still having ActiveMQ 4.1.2-G20090207 deployed in the application server. Further It'd be convenient to have the 5.2 broker deployed in the application server. What I hope to elicit from you on this list is some feedback, is it reasonable, etc... So, here's my plan: undeploy org.apache.geronimo.plugins/activemq-console-jetty/2.1.4/car undeploy org.apache.geronimo.configs/activemq-ra/2.1.4/car undeploy org.apache.geronimo.configs/activemq-broker/2.1.4/car install-library org.apache.activemq/activemq-core/5.2.0/jar install-library org.apache.activemq/activeio-core/3.1.0/jar install-library org.apache.activemq/activemq-rar/5.2.0/jar # Seems like openejb depends on activemq-broker so i now need to # create a plugin that artifact-aliases ...configs/activemq-broker/2.1.4/car # and starts a 5.2.0 broker. deploy said module #Is there a uninstall-library command, or is "rm -rf whatever" fine? rm -rf $G/repository/org/apache/activemq/activemq-core/4.1.2-G20090207 rm -rf $G/repository/org/apache/activemq/activeio-core/3.0.1 That's pretty much it. Are there any glaring omissions in this plan? Anyone else done anything similar before? Is it reasonable? Any feedback much appreciated. Thanks! -- Fredrik Jonson
