Ok, here it is - http://www.4shared.com/zip/IgOJaf_C/poc.html
"mvn package" will produce an EAR and put it to the path where DEPLOY environment variable points to. To test it just make an GET HTTP request to http://localhost:8080/frontend/backend it will just send Date object to JMS topic and then output it to the console. Try doing multiple requests until you see mentioned exceptions. They come up randomly (it might take some time till they appear), so if you don't get them try to restart TomEE and perform GET requests again. Used broker configurations are: ----- First one ---------- <Resource id="ActiveMQProvider" type="ActiveMQResourceAdapter"> BrokerXmlConfig=broker:(tcp://localhost:61616) ServerUrl = vm://localhost MaximumRedeliveries 10 DataSource TransactionSupport = none </Resource> <Resource id="ActiveMQConnectionFactory" type="javax.jms.ConnectionFactory"> ResourceAdapter = ActiveMQProvider PoolMinSize = 10 PoolMaxSize = 150 </Resource> <Container id="ActiveMQMDBContainer" ctype="MESSAGE"> ResourceAdapter = ActiveMQProvider </Container> ----- Second one ---------- <Resource id="ActiveMQProvider" type="ActiveMQResourceAdapter"> BrokerXmlConfig=broker:(tcp://localhost:61616) ServerUrl = vm://localhost?jms.useAsyncSend=false&jms.alwaysSessionAsync=false&marshal=false&broker.persistent=false&jms.copyMessageOnSend=false MaximumRedeliveries 10 DataSource TransactionSupport = none </Resource> <Resource id="ActiveMQConnectionFactory" type="javax.jms.ConnectionFactory"> ResourceAdapter = ActiveMQProvider PoolMinSize = 5 PoolMaxSize = 75 </Resource> <Container id="ActiveMQMDBContainer" ctype="MESSAGE"> ResourceAdapter = ActiveMQProvider </Container> -- View this message in context: http://openejb.979440.n4.nabble.com/ActiveMQ-1-5-1-issue-with-an-ActiveMQ-embedded-broker-tp4658482p4661528.html Sent from the OpenEJB User mailing list archive at Nabble.com.
