Hello, I have found that if the HTTPConnector times out without receiving the response from the backend API, then somewhere down the line it generates 2 error responses and this is evident from the metrics as it show 2 failures as supposed to 1 failure for the single request. So there are 2 issues, - firstly the returned error response contains 2 error XMLs appended to each other and sent to the browser and hence not a valid XML. - The metrics also shows as 2 failure response for single request. ​ I have been looking the sources but without the way to debug within running application, it quite hard to follow the flow. This can be easily simulated with setting very low timeouts (2 secs for ex) in apiman.properties. apiman-gateway.connector-factory.http.timeouts.read=2 apiman-gateway.connector-factory.http.timeouts.write=2 Could you please look at the issue and also If you could guide me how to setup debugging environment, then I can try to fix that as well. regards Balu

With regards to debugging: I assume you are using the Servlet/WAR gateway with WildFly? If so, I suggest you consult the WF debugging guides -- but, in short, you can start up the application server with --debug and connect to it remotely from your debugger (e.g. Eclipse, IntelliJ, etc). https://tools.jboss.org/blog/2015-03-17-debugging-an- externally-launched-wildfly.html Regards, Marc On 16 February 2017 at 10:34, Balu S <sbalu27(a)gmail.com&gt; wrote: > Hello, > I have found that if the HTTPConnector times out without receiving the > response from the backend API, then somewhere down the line it generates 2 > error responses and this is evident from the metrics as it show 2 failures > as supposed to 1 failure for the single request. > > So there are 2 issues, > - firstly the returned error response contains 2 error XMLs appended to > each other and sent to the browser and hence not a valid XML. > - The metrics also shows as 2 failure response for single request. > > ​ > I have been looking the sources but without the way to debug within > running application, it quite hard to follow the flow. > > This can be easily simulated with setting very low timeouts (2 secs for > ex) in apiman.properties. > > apiman-gateway.connector-factory.http.timeouts.read=2 > apiman-gateway.connector-factory.http.timeouts.write=2 > > Could you please look at the issue and also If you could guide me how to > setup debugging environment, then I can try to fix that as well. > > regards > Balu > > _______________________________________________ > Apiman-user mailing list > Apiman-user(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/apiman-user > >

You may want to consider running apiman locally on your development machine when doing debugging/reproducer work. This particular issue should be simple to reproduce locally, I should think. On 16 February 2017 at 11:14, Balu S <sbalu27(a)gmail.com&gt; wrote: > Thanks Marc. yes it is Servlet/Wildfly setup. > > The problem with my setup is am behind proxy so using the overlay zip (on > top of local wildfly installtion) generated from outside machine. So cannot > build the apiman sources from within eclipse. I shall try. > > On Thu, Feb 16, 2017 at 12:05 PM, Marc Savy <marc.savy(a)redhat.com&gt; wrote: > >> With regards to debugging: >> >> I assume you are using the Servlet/WAR gateway with WildFly? >> >> If so, I suggest you consult the WF debugging guides -- but, in short, >> you can start up the application server with --debug and connect to it >> remotely from your debugger (e.g. Eclipse, IntelliJ, etc). >> >> https://tools.jboss.org/blog/2015-03-17-debugging-an-externa >> lly-launched-wildfly.html >> >> Regards, >> Marc >> >> On 16 February 2017 at 10:34, Balu S <sbalu27(a)gmail.com&gt; wrote: >> >>> Hello, >>> I have found that if the HTTPConnector times out without receiving the >>> response from the backend API, then somewhere down the line it generates 2 >>> error responses and this is evident from the metrics as it show 2 failures >>> as supposed to 1 failure for the single request. >>> >>> So there are 2 issues, >>> - firstly the returned error response contains 2 error XMLs appended >>> to each other and sent to the browser and hence not a valid XML. >>> - The metrics also shows as 2 failure response for single request. >>> >>> ​ >>> I have been looking the sources but without the way to debug within >>> running application, it quite hard to follow the flow. >>> >>> This can be easily simulated with setting very low timeouts (2 secs for >>> ex) in apiman.properties. >>> >>> apiman-gateway.connector-factory.http.timeouts.read=2 >>> apiman-gateway.connector-factory.http.timeouts.write=2 >>> >>> Could you please look at the issue and also If you could guide me how >>> to setup debugging environment, then I can try to fix that as well. >>> >>> regards >>> Balu >>> >>> _______________________________________________ >>> Apiman-user mailing list >>> Apiman-user(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/apiman-user >>> >>> >> >

I will have to use this machine where it can connect to API. The problem is there is "npm install" during the build process as am behind proxy it fails during the execution. What does the npm install do in apimanager-ui-war..How do I skip it ? regards Balu On Thu, Feb 16, 2017 at 2:04 PM, Marc Savy <marc.savy(a)redhat.com&gt; wrote: > You may want to consider running apiman locally on your development > machine when doing debugging/reproducer work. This particular issue should > be simple to reproduce locally, I should think. > > On 16 February 2017 at 11:14, Balu S <sbalu27(a)gmail.com&gt; wrote: > >> Thanks Marc. yes it is Servlet/Wildfly setup. >> >> The problem with my setup is am behind proxy so using the overlay zip >> (on top of local wildfly installtion) generated from outside machine. So >> cannot build the apiman sources from within eclipse. I shall try. >> >> On Thu, Feb 16, 2017 at 12:05 PM, Marc Savy <marc.savy(a)redhat.com&gt; >> wrote: >> >>> With regards to debugging: >>> >>> I assume you are using the Servlet/WAR gateway with WildFly? >>> >>> If so, I suggest you consult the WF debugging guides -- but, in short, >>> you can start up the application server with --debug and connect to it >>> remotely from your debugger (e.g. Eclipse, IntelliJ, etc). >>> >>> https://tools.jboss.org/blog/2015-03-17-debugging-an-externa >>> lly-launched-wildfly.html >>> >>> Regards, >>> Marc >>> >>> On 16 February 2017 at 10:34, Balu S <sbalu27(a)gmail.com&gt; wrote: >>> >>>> Hello, >>>> I have found that if the HTTPConnector times out without receiving the >>>> response from the backend API, then somewhere down the line it generates 2 >>>> error responses and this is evident from the metrics as it show 2 failures >>>> as supposed to 1 failure for the single request. >>>> >>>> So there are 2 issues, >>>> - firstly the returned error response contains 2 error XMLs appended >>>> to each other and sent to the browser and hence not a valid XML. >>>> - The metrics also shows as 2 failure response for single request. >>>> >>>> ​ >>>> I have been looking the sources but without the way to debug within >>>> running application, it quite hard to follow the flow. >>>> >>>> This can be easily simulated with setting very low timeouts (2 secs >>>> for ex) in apiman.properties. >>>> >>>> apiman-gateway.connector-factory.http.timeouts.read=2 >>>> apiman-gateway.connector-factory.http.timeouts.write=2 >>>> >>>> Could you please look at the issue and also If you could guide me how >>>> to setup debugging environment, then I can try to fix that as well. >>>> >>>> regards >>>> Balu >>>> >>>> _______________________________________________ >>>> Apiman-user mailing list >>>> Apiman-user(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/apiman-user >>>> >>>> >>> >> >

I fixed this on master. It only affects the Servlet version (Vert.x was OK). On 17 February 2017 at 17:23, Marc Savy <marc.savy(a)redhat.com&gt; wrote: > If you want to build apiman quickly you can use (NB: skips tests which > don't presently work when run in parallel): > > - mvn clean install -DskipTests=true -Dmvn.skip.test=true -T1C > > On 17 February 2017 at 14:53, Balu S <sbalu27(a)gmail.com&gt; wrote: > >> I will have to use this machine where it can connect to API. The problem >> is there is "npm install" during the build process as am behind proxy it >> fails during the execution. >> >> What does the npm install do in apimanager-ui-war..How do I skip it ? >> >> regards >> Balu >> >> On Thu, Feb 16, 2017 at 2:04 PM, Marc Savy <marc.savy(a)redhat.com&gt; wrote: >> >>> You may want to consider running apiman locally on your development >>> machine when doing debugging/reproducer work. This particular issue should >>> be simple to reproduce locally, I should think. >>> >>> On 16 February 2017 at 11:14, Balu S <sbalu27(a)gmail.com&gt; wrote: >>> >>>> Thanks Marc. yes it is Servlet/Wildfly setup. >>>> >>>> The problem with my setup is am behind proxy so using the overlay zip >>>> (on top of local wildfly installtion) generated from outside machine. So >>>> cannot build the apiman sources from within eclipse. I shall try. >>>> >>>> On Thu, Feb 16, 2017 at 12:05 PM, Marc Savy <marc.savy(a)redhat.com&gt; >>>> wrote: >>>> >>>>> With regards to debugging: >>>>> >>>>> I assume you are using the Servlet/WAR gateway with WildFly? >>>>> >>>>> If so, I suggest you consult the WF debugging guides -- but, in >>>>> short, you can start up the application server with --debug and connect to >>>>> it remotely from your debugger (e.g. Eclipse, IntelliJ, etc). >>>>> >>>>> https://tools.jboss.org/blog/2015-03-17-debugging-an-externa >>>>> lly-launched-wildfly.html >>>>> >>>>> Regards, >>>>> Marc >>>>> >>>>> On 16 February 2017 at 10:34, Balu S <sbalu27(a)gmail.com&gt; wrote: >>>>> >>>>>> Hello, >>>>>> I have found that if the HTTPConnector times out without receiving >>>>>> the response from the backend API, then somewhere down the line it >>>>>> generates 2 error responses and this is evident from the metrics as it show >>>>>> 2 failures as supposed to 1 failure for the single request. >>>>>> >>>>>> So there are 2 issues, >>>>>> - firstly the returned error response contains 2 error XMLs >>>>>> appended to each other and sent to the browser and hence not a valid XML. >>>>>> - The metrics also shows as 2 failure response for single request. >>>>>> >>>>>> ​ >>>>>> I have been looking the sources but without the way to debug within >>>>>> running application, it quite hard to follow the flow. >>>>>> >>>>>> This can be easily simulated with setting very low timeouts (2 secs >>>>>> for ex) in apiman.properties. >>>>>> >>>>>> apiman-gateway.connector-factory.http.timeouts.read=2 >>>>>> apiman-gateway.connector-factory.http.timeouts.write=2 >>>>>> >>>>>> Could you please look at the issue and also If you could guide me >>>>>> how to setup debugging environment, then I can try to fix that as well. >>>>>> >>>>>> regards >>>>>> Balu >>>>>> >>>>>> _______________________________________________ >>>>>> Apiman-user mailing list >>>>>> Apiman-user(a)lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/apiman-user >>>>>> >>>>>> >>>>> >>>> >>> >> >