Yes I will try to add a JIRA ticket. In general, this type of thing: <send> <endpoint> <address uri="jms:/SimpleStockQuoteService?transport.jms.ConnectionFactoryJNDIName=Qu eueConnectionFactory& java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextF actory&java.naming.provider.url=tcp://localhost:61616"/> </endpoint> </send>
Seems to be making a JNDI lookup to get the connection factory for every message sent. Eventually I start getting jndi connection exceptions (like, I said, after about 1000 messages or so) In my world, messages come in via a jms queue. Messages can get published at a rate of about 25K a minute. In the ESB, messages get pulled off, some steps happen to validate, filter, transform and then messages get published to specific queues for our "subscribers" You can probably duplicate this problem by starting with sample 250 but instead of "switching" to an http call, "switch" to publishing to a different JMS queue. Load up the "incoming queue" with about 10000 messages. Start the ESB with your "switch from an incoming queue to an outgoing queue" sequence deployed and I'm guessing you'll get the same error as I'm getting after 1000 or so messages get pulled off of your incoming queue. Keith On 4/13/09 5:15 PM, "Asankha C. Perera" <[email protected]> wrote: > Hi Keith >> I wrote a spring based "jms publisher" because I could not use the synapse >> jms publishing because it seems to create a connection for every message >> sent, which runs into issues after about 1000 messages or so. >> > Can you raise a JIRA, and include all information.. if there is a known > bug we should fix it soon.. and your support would be helpful > > cheers > asankha This communication, along with any attachments, is covered by federal and state law governing electronic communications and may contain company proprietary and legally privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, use or copying of this message is strictly prohibited. If you have received this in error, please reply immediately to the sender and delete this message. Thank you.
