<div dir="ltr">I tested the 1.3.0 EAP7 overlay. At least there's a message now:<div><br></div><div>{ "responseCode": 500, "message", "io.apiman.gateway.engine.beans.exceptions.ConnectionException: Not connected.", ...</div><div><br></div><div>Then a stack trace.</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, May 4, 2017 at 3:41 PM Eric Wittmann <<a href="mailto:eric.wittmann@redhat.com">eric.wittmann@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">+1 good point. Can you perhaps open a JIRA ticket? That would be super helpful and would allow you to automatically track progress on the issue.</div><div dir="ltr"><div><br></div><div>-Eric</div><div><br></div></div><div class="gmail_extra"><div class="gmail_quote">On Thu, May 4, 2017 at 1:48 PM, Scott Elliott <span dir="ltr"><<a href="mailto:scottpelliott@gmail.com" target="_blank">scottpelliott@gmail.com</a>></span> wrote:<br></div></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Right now, when the APIMAN gateway cannot connect to the API implementation's endpoint, the response code is 500, the message is null, and there is a stack trace. It's not a very useful response for the caller, and it's not really an internal problem with the gateway. It would be better if another response code were used (502? 503?) and a useful message were returned instead of a stack trace.</div>
<br>_______________________________________________<br>
Apiman-user mailing list<br>
<a href="mailto:Apiman-user@lists.jboss.org" target="_blank">Apiman-user@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/apiman-user" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/apiman-user</a><br>
<br></blockquote></div></div></blockquote></div>