That's a bit strange, on 1.5.1 and 1.6 trunk I can easily reproduce it with your steps.
What I did was: 0. created TOMEE_HOME/apps dir 1. Downloaded 1.5.1-plus release 2. Changed tomee.xml to add 1-st ActiveMQ configuration 3. Ran TomEE 4. Deployed EAR 5. Ran ab -n 1000 -c 50 http://localhost:8080/frontend/backend This time I didn't get any exceptions. Strange, but the fact remains. I re-tried with following steps 1. Stopped tomee 2. Removed logs (rm -f ./logs/*) 3. Removed deployed apps (rm -Rf ./apps/*) 4. started tomee (./bin/startup.sh) 5. Deployed EAR again (./bin/tomee.sh deploy /tmp/poc-0.1.1-SNAPSHOT.ear) 6. Ran ab -n 1000 -c 50 http://localhost:8080/frontend/backend This time I got 17 Exceptions Then I tried latest nightly 1.6 build ( https://repository.apache.org/content/groups/snapshots/org/apache/openejb/apache-tomee/1.6.0-SNAPSHOT/apache-tomee-1.6.0-20130312.041113-27-plus.tar.gz) Steps were following: 0. created TOMEE_HOME/apps dir 1. Copied tomee.xml used to check 1.5.1 version 2. Started tomee (./bin/startup.sh) 3. Deployed EAR (./bin/tomee.sh deploy /tmp/poc-0.1.1-SNAPSHOT.ear) 4. Ran ab -n 1000 -c 50 http://localhost:8080/frontend/backend This time for 1.6 trunk I got 11 Exceptions. I don't know why you can't reproduce it. Maybe try couple of consequent deploys. I can reproduce this with different environments (Win7/RHEL 6.3/MacOS 10.7) with different JREs (1.6/1.7) using source TomEE distributions. Regards, Aleksey Moskvin -- View this message in context: http://openejb.979440.n4.nabble.com/ActiveMQ-1-5-1-issue-with-an-ActiveMQ-embedded-broker-tp4658482p4661555.html Sent from the OpenEJB User mailing list archive at Nabble.com.
