Hi all, Our setup is:
- ActiveMQ 5.3 running standalone - Web app under Tomcat 6.0.20 as producer. - A separate thread acts as a consumer. - Producer & consumer configured by attached JNDI props file. - Java 6 First we had a problem with ActiveMQ+Tomcat freezing that we solved by turning of producer workflow control in the broker's activemq.xml. Then we lost messages due to jvm bind errors when threads were concurrently sending messages. We could solve this, too, by using PooledConnectionFactory. However, we did this in the code which is bad because the app ist distributed to users who run it in app servers and want to use different JMS implementations, so we must avoid dependencies on any JMS implementation. We'd be very grateful for a hint on how to configure the use of PooledConnectionFactory. Can this be done per jndi.properties or do we need an activemq.xml file instead? We've been looking for a solution quite a while but are a bit at a loss now. Thanks in advance for any help, Michael http://old.nabble.com/file/p27847333/jndi.properties jndi.properties -- View this message in context: http://old.nabble.com/Configuring-connection-factory-class-in-standalone-client-tp27847333p27847333.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
