I can see the similarities to the second link you sent. However I am not sure it relates since this same application shut down cleanly previously when running earlier TomEE snapshots with AMQ 5.8. I am not sure if I should also post something over on the AMQ list to see if they have any ideas or if this is just an issue with the TomEE/AMQ integration related to the version bump and should be kept here. The exceptions do not seem to cause any problems apart from adding a lot of static to the logs when shutting down so thankfully this is more of an annoyance than breaking change for me.
Trevor Stevens [email protected] On Nov 8, 2013, at 7:07 PM, Howard W. Smith, Jr. <[email protected]> wrote: > i just searched google for the following exception, > > On Fri, Nov 8, 2013 at 11:11 AM, Trevor Stevens <[email protected]> wrote: > >> 08-Nov-2013 10:48:42.526 WARNING [ActiveMQ Connection Executor: >> vm://localhost#0] >> org.apache.geronimo.connector.outbound.GeronimoConnectionEventListener.connectionErrorOccurred >> connectionErrorOccurred called with null >> javax.jms.JMSException: peer (vm://localhost#1) stopped. >> > > and found this[1] (which was discussed in 2011). does your > app/requirement/use-case resemble something discussed there? your error > occurs on shutdown, but in that discussion/thread, it seems to occur on hot > deploy or autodeploy. I would assume that autodeploy equals/includes > (undeploy and) restart. > > also, found this[2], which was discussed in 2007 (the error or similar > error has been around). sometimes, i open up and read some topics on > activemq list, and I have seen some mention this bug-fix broke another > bug-fix. i think i hear that on this list, too. all good though, right? :) > > [1] > http://activemq.2283324.n4.nabble.com/right-config-for-activeMQ-to-handle-persisted-messages-through-Oracle-td4119713.html > > [2] http://marc.info/?l=activemq-users&m=119524994715950
