have a look at one of the test cases for this feature from trunk and do a compare and contrast or try and munge it into something that demonstrates your behavior. see: http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/ProducerFlowControlSendFailTest.java?view=markup
2009/10/30 moreno9000 <moreno.ma...@italtel.it>: > > Is my issue similar to this one? > > https://issues.apache.org/activemq/browse/AMQ-1022 AMQ-1022 > > In 1022, error was due to a "permission (to write on a queue) problem", > in my case error is due to a "queue full problem", > but in both cases producer receives an exception only in an asynchronous way > (exceptionListener). > > Moreno > > > > > brett.humphreys wrote: >> >> Moreno, >> Your issue is that you're using async send. I believe this is the default >> sending type for performance reasons. However with async send, it puts >> your send in a queue and performs the send out of the calling thread. >> >> What you need to do is explicitly disable async send on your producer (or >> via the URI used to create the connection. More info is here: >> http://activemq.apache.org/async-sends.html >> >> Once you turn this off on the connection your producer is created from, >> you'll get exceptions in the thread that is calling send(). With async >> send, you get better performance but you need to use an ExceptionListener >> to determine if you get exceptions on your send. >> >> Hope that helps Moreno. >> > > > > > -- > View this message in context: > http://old.nabble.com/sendFailIfNoSpace%3Dtrue%2C-no-JMSException-for-Producer-tp26094263p26130457.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
