HI Manu, I too have noticed the same and having incorrect endpoints or destination would keep printing error messages in the log. This at times easily fill out the available space of the server in which ESB is running. IMO there is currently no way to control this, but may be possible to do as you have suggested.
Shazni Nazeer Mob : +94 777737331 LinkedIn : http://lk.linkedin.com/in/shazninazeer Blog : http://shazninazeer.blogspot.com On Wed, May 4, 2016 at 10:55 PM, Manuranga Perera <[email protected]> wrote: > 1. Misconfigured endpoints make server continually print logs [1]. > Printing ones should be enough. I think it should be possible to do this > form ESB code (axis2). Should I open a public JIRA? > > 2. In the case of messages with wrong content type it might not be > possible to do this form ESB code. Is there a way to make an exponential > back-off? > > [1] ERROR {org.apache.axis2.transport.jms.ServiceTaskManager} - Error > acquiring a JMS connection to MyQ using JNDI properties : {...} > > -- > With regards, > *Manu*ranga Perera. > > phone : 071 7 70 20 50 > mail : [email protected] >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
