You could use a broker plugin nd override the addconnection method, to do a
different check.
That exception implements part of the jms spec so it may be better to
understand nd tackle the root cause.
If you really need to change behaviour the broker plugin is the way to go.
On 21 Apr 2011 19:43, "teapot" <jijun.w...@oracle.com> wrote:
> Gary:
>
> We already have code on the client site(where connection is initiated) to
> handle the exception. But the same message also showed up on server log
and
> we would like to filter it out.
>
> Our AMQ broker is configured and started via spring
> bean(org.apache.activemq.xbean.BrokerFactoryBean). Is there any place to
add
> a plugin exception handler for javax.jms.InvalidClientIDException. The
> http://activemq.apache.org/configurable-ioexception-handling.html only
deals
> with IOException.
>
> Thanks.
>
> --
> View this message in context:
http://activemq.2283324.n4.nabble.com/How-to-catch-javax-jms-InvalidClientIDException-from-AMQ-tp3458347p3466613.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
