Is any way to protect broker from malicios or badly written client code that keep creating temp queues? At some point broker hits virtual memory limits and number of live threads is very high...
javax.jms.JMSException: unable to create new native thread at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49) at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1362) at org.apache.activemq.ActiveMQConnection.createTempDestination(ActiveMQConnection.java:2023) at org.apache.activemq.ActiveMQSession.createTemporaryQueue(ActiveMQSession.java:1353) -- View this message in context: http://activemq.2283324.n4.nabble.com/How-to-protect-broker-from-broker-from-exhausting-resources-requested-by-clients-creating-temp-queues-tp4660974.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.