[Apiman-user] Response when gateway cannot connect to the API implementation

[Marc Savy]

Thanks for the feedback. I'll create an issue for this and look to improve
the behaviour further for the next release.

On 4 May 2017 at 22:28, Scott Elliott <scottpelliott at gmail.com> wrote:

> I tested the 1.3.0 EAP7 overlay.  At least there's a message now:
>
> { "responseCode": 500, "message", "io.apiman.gateway.engine.
> beans.exceptions.ConnectionException: Not connected.", ...
>
> Then a stack trace.
>
>
> On Thu, May 4, 2017 at 3:41 PM Eric Wittmann <eric.wittmann at redhat.com>
> wrote:
>
>> +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.
>>
>> -Eric
>>
>> On Thu, May 4, 2017 at 1:48 PM, Scott Elliott <scottpelliott at 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 at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/apiman-user
>>>
>>>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170505/2d79985a/attachment-0001.html