Hi Scott,

Which implementation are you using?

We actually just quietly released 1.3.0.Final (will be officially released once I finish the rafts of new documentation, website, blog, etc). 

Perhaps you can quickly replicate the scenario to see if the error still occurs in the same manner, else I'll try to improve it for the next release.

WF10
http://downloads.jboss.org/apiman/1.3.0.Final/apiman-distro-wildfly10-1.3.0.Final-overlay.zip

Vert.x Gateway
http://downloads.jboss.org/apiman/1.3.0.Final/apiman-distro-vertx-1.3.0.Final.zip

Regards,
Marc

On 4 May 2017 at 18:48, Scott Elliott <scottpelliott@gmail.com> wrote:
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.

_______________________________________________
Apiman-user mailing list
Apiman-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/apiman-user