From marc.savy at redhat.com Sun Jul 3 10:54:16 2016 From: marc.savy at redhat.com (Marc Savy) Date: Sun, 3 Jul 2016 15:54:16 +0100 Subject: [Apiman-user] LIVE APIMAN deployments and Performance In-Reply-To: References: Message-ID: Hi Tomas, Disregarding recent Red Hat announcement on 3scale acquisition and knowing > that Red Hat will now be working on merging the 3scale and apiman > technologies, we are still thinking of APIMAN as the main candidate for API > management (Policy Enforcement) solution. As Eric mentioned in the blog, we (apiman team) are determined to do the very best we can for the apiman community - after all it's sizeable now :-). Do you know any LIVE deployments of APIMAN with scale larger than 200 TPS > per node? I believe so, but I can't reference any of them publicly (although, community - feel free to weigh in with your numbers!). Any idea how many APIMAN LIVE deployments are there? This is something that's notoriously difficult to do, especially as a free and open source project. We don't have any phone-home functionality, and there's not any easy way to correlate number of downloads with number of deploments. That being said, a good number of folk have reached out to us saying they are using it and/or prototyping. Could you point me to some performance benchmarks of APIMAN, are there any? That's hopefully something I'll be working on, it's also quite a ticky area to get right (particularly as lots of people do it wrong[1]!). Community feedback thus far is that they've found performance good and that the main impact is (as you would expect) is how slow your policies are - e.g. if your custom policy reaches out to a DB on every request, then it'll be slow. Naturally this is an area that's important to us, and we'll be working on improving it - often by harnessing the strengths of other projects such as Vert.x. Regards, Marc [1] https://www.youtube.com/watch?v=lJ8ydIuPFeU On 30 June 2016 at 06:58, Tomas ?uklys wrote: > Hi APIMAN Gurus, > > Disregarding recent Red Hat announcement on 3scale acquisition and knowing > that Red Hat will now be working on merging the 3scale and apiman > technologies, we are still thinking of APIMAN as the main candidate for API > management (Policy Enforcement) solution. > > Do you know any LIVE deployments of APIMAN with scale larger than 200 TPS > per node? > > Any idea how many APIMAN LIVE deployments are there? > > Could you point me to some performance benchmarks of APIMAN, are there any? > > Is APIMAN stable enough for going to PRODUCTION? > > > Thanks in advance! > > Best regards, > Tomas Zuklys > > _______________________________________________ > 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/20160703/513354a8/attachment-0001.html From tomas.zuklys at gmail.com Mon Jul 4 08:14:24 2016 From: tomas.zuklys at gmail.com (=?UTF-8?Q?Tomas_=C5=BDuklys?=) Date: Mon, 4 Jul 2016 15:14:24 +0300 Subject: [Apiman-user] LIVE APIMAN deployments and Performance In-Reply-To: References: Message-ID: Thanks for the info Marc! On 3 July 2016 at 17:54, Marc Savy wrote: > Hi Tomas, > > Disregarding recent Red Hat announcement on 3scale acquisition and knowing >> that Red Hat will now be working on merging the 3scale and apiman >> technologies, we are still thinking of APIMAN as the main candidate for API >> management (Policy Enforcement) solution. > > > As Eric mentioned in the blog, we (apiman team) are determined to do the > very best we can for the apiman community - after all it's sizeable now > :-). > > Do you know any LIVE deployments of APIMAN with scale larger than 200 TPS >> per node? > > > I believe so, but I can't reference any of them publicly (although, > community - feel free to weigh in with your numbers!). > > Any idea how many APIMAN LIVE deployments are there? > > > This is something that's notoriously difficult to do, especially as a free > and open source project. We don't have any phone-home functionality, and > there's not any easy way to correlate number of downloads with number of > deploments. > > That being said, a good number of folk have reached out to us saying they > are using it and/or prototyping. > > Could you point me to some performance benchmarks of APIMAN, are there any? > > > That's hopefully something I'll be working on, it's also quite a ticky > area to get right (particularly as lots of people do it wrong[1]!). > > Community feedback thus far is that they've found performance good and > that the main impact is (as you would expect) is how slow your policies are > - e.g. if your custom policy reaches out to a DB on every request, then > it'll be slow. > > Naturally this is an area that's important to us, and we'll be working on > improving it - often by harnessing the strengths of other projects such as > Vert.x. > > Regards, > Marc > > [1] https://www.youtube.com/watch?v=lJ8ydIuPFeU > > > > On 30 June 2016 at 06:58, Tomas ?uklys wrote: > >> Hi APIMAN Gurus, >> >> Disregarding recent Red Hat announcement on 3scale acquisition and >> knowing that Red Hat will now be working on merging the 3scale and apiman >> technologies, we are still thinking of APIMAN as the main candidate for API >> management (Policy Enforcement) solution. >> >> Do you know any LIVE deployments of APIMAN with scale larger than 200 TPS >> per node? >> >> Any idea how many APIMAN LIVE deployments are there? >> >> Could you point me to some performance benchmarks of APIMAN, are there >> any? >> >> Is APIMAN stable enough for going to PRODUCTION? >> >> >> Thanks in advance! >> >> Best regards, >> Tomas Zuklys >> >> _______________________________________________ >> 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/20160704/e8dace53/attachment.html From Rushikesh.Bargaje at nttdata.com Thu Jul 7 11:05:39 2016 From: Rushikesh.Bargaje at nttdata.com (Bargaje, Rushikesh) Date: Thu, 7 Jul 2016 15:05:39 +0000 Subject: [Apiman-user] Regarding apiman deployment Message-ID: Hi, We are evaluating apiman tool. We want to deploy this tool on pivotal cloud foundry (PCF). We are not able to deploy the tool as it is on PCF We tried to build the application but it is generating multiple war files. Is there any way to deploy those war files directly on Tomcat instead of using wildfly Platform? Thanks & Regards, RUSHIKESH BARGAJE | NTT DATA Global Delivery Services Private Limited | M.+ 91 7767987295 | rushikesh.bargaje at nttdata.com | Learn more at nttdata.com/americas ______________________________________________________________________ Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20160707/9d203c42/attachment.html From Ashish.Patel at futureretail.in Fri Jul 8 00:33:08 2016 From: Ashish.Patel at futureretail.in (Ashish Patel) Date: Fri, 8 Jul 2016 10:03:08 +0530 Subject: [Apiman-user] Regarding apiman deployment In-Reply-To: References: Message-ID: <7F9CC9E7FDAD3C4E9B251D35B702CF51314ED09A06@DC-SRV-MBX-08> Hi Rushikesh, Yes, you can use tomcat for apiman evaluation. We used tomcat only - instructions from download page - http://imgur.com/rLOUZI8. So if you already have tomcat on PCF, you can refer extracting tomcat overlay zip directly. Thanks & Regards, Ashish Patel "Scientists investigate that which already is;Engineers create that which has never been." - Albert Einstein. From: apiman-user-bounces at lists.jboss.org [mailto:apiman-user-bounces at lists.jboss.org] On Behalf Of Bargaje, Rushikesh Sent: 07 July 2016 20:36 To: apiman-user at lists.jboss.org Cc: Wani, Nilesh; Bhisikar, Amit; Uikey, Nitin; Vaidya, Sagar Subject: [Apiman-user] Regarding apiman deployment Hi, We are evaluating apiman tool. We want to deploy this tool on pivotal cloud foundry (PCF). We are not able to deploy the tool as it is on PCF We tried to build the application but it is generating multiple war files. Is there any way to deploy those war files directly on Tomcat instead of using wildfly Platform? Thanks & Regards, RUSHIKESH BARGAJE | NTT DATA Global Delivery Services Private Limited | M.+ 91 7767987295 | rushikesh.bargaje at nttdata.com | Learn more at nttdata.com/americas ______________________________________________________________________ Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding. ________________________________ Disclaimer: This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not Future Group's. The recipient should check this email and attachments for the presence of viruses. Future Group accepts no liability for any damage caused by any virus transmitted by this email. Future Group may monitor and record all emails. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20160708/c5303955/attachment-0001.html From Ashish.Patel at futureretail.in Fri Jul 8 05:20:01 2016 From: Ashish.Patel at futureretail.in (Ashish Patel) Date: Fri, 8 Jul 2016 14:50:01 +0530 Subject: [Apiman-user] Regarding apiman deployment In-Reply-To: <61DB730F98162C4680731B3AE36AF95575E4A85D@MAIL703.KDS.KEANE.COM> References: <7F9CC9E7FDAD3C4E9B251D35B702CF51314ED09A06@DC-SRV-MBX-08> <61DB730F98162C4680731B3AE36AF95575E4A85D@MAIL703.KDS.KEANE.COM> Message-ID: <7F9CC9E7FDAD3C4E9B251D35B702CF51314ED09E08@DC-SRV-MBX-08> Hi Nitin, It seems you are running under container/similar infra. Try giving all ports access with in OR check in logs if any of the package service deployment has failed. Hope this helps. Thanks & Regards, Ashish Patel "Scientists investigate that which already is;Engineers create that which has never been." - Albert Einstein. From: Uikey, Nitin [mailto:Nitin.Uikey at nttdata.com] Sent: 08 July 2016 14:00 To: Ashish Patel; Bargaje, Rushikesh; apiman-user at lists.jboss.org Cc: Wani, Nilesh; Bhisikar, Amit; Vaidya, Sagar Subject: RE: Regarding apiman deployment Dear Ashish, We tried to follow the same steps as suggested in http://www.apiman.io/latest/download.html -> Tomcat 8+ and executed the following steps -> mkdir ~/apiman-1.2.7.Final cd ~/apiman-1.2.7.Final curl http://apache.mirrors.tds.net/tomcat/tomcat-8/v8.0.33/bin/apache-tomcat-8.0.33.zip -o apache-tomcat-8.0.33.zip curl http://downloads.jboss.org/apiman/1.2.7.Final/apiman-distro-tomcat8-1.2.7.Final-overlay.zip -o apiman-distro-tomcat8-1.2.7.Final-overlay.zip unzip apache-tomcat-8.0.33.zip unzip -o apiman-distro-tomcat8-1.2.7.Final-overlay.zip -d apache-tomcat-8.0.33 cd apache-tomcat-8.0.33 chmod 755 bin/catalina.sh ./bin/catalina.sh run $ cf push apiman We got following error -> Exception in thread "Thread-6" java.lang.RuntimeException: java.lang.RuntimeException: org.apache.http.conn.HttpHostConnectException: Connect to localhost:19200 [localhost/127.0.0.1] failed: Connection refused Do you have any idea about this issue? Thanks and Regards, Nitin Uikey From: Ashish Patel [mailto:Ashish.Patel at futureretail.in] Sent: 08 July 2016 10:03 To: Bargaje, Rushikesh; apiman-user at lists.jboss.org Cc: Wani, Nilesh; Bhisikar, Amit; Uikey, Nitin; Vaidya, Sagar Subject: RE: Regarding apiman deployment Hi Rushikesh, Yes, you can use tomcat for apiman evaluation. We used tomcat only - instructions from download page - http://imgur.com/rLOUZI8. So if you already have tomcat on PCF, you can refer extracting tomcat overlay zip directly. Thanks & Regards, Ashish Patel "Scientists investigate that which already is;Engineers create that which has never been." - Albert Einstein. From: apiman-user-bounces at lists.jboss.org [mailto:apiman-user-bounces at lists.jboss.org] On Behalf Of Bargaje, Rushikesh Sent: 07 July 2016 20:36 To: apiman-user at lists.jboss.org Cc: Wani, Nilesh; Bhisikar, Amit; Uikey, Nitin; Vaidya, Sagar Subject: [Apiman-user] Regarding apiman deployment Hi, We are evaluating apiman tool. We want to deploy this tool on pivotal cloud foundry (PCF). We are not able to deploy the tool as it is on PCF We tried to build the application but it is generating multiple war files. Is there any way to deploy those war files directly on Tomcat instead of using wildfly Platform? Thanks & Regards, RUSHIKESH BARGAJE | NTT DATA Global Delivery Services Private Limited | M.+ 91 7767987295 | rushikesh.bargaje at nttdata.com | Learn more at nttdata.com/americas ______________________________________________________________________ Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding. ________________________________ Disclaimer: This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not Future Group's. The recipient should check this email and attachments for the presence of viruses. Future Group accepts no liability for any damage caused by any virus transmitted by this email. Future Group may monitor and record all emails. ______________________________________________________________________ Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding. ________________________________ Disclaimer: This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not Future Group's. The recipient should check this email and attachments for the presence of viruses. Future Group accepts no liability for any damage caused by any virus transmitted by this email. Future Group may monitor and record all emails. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20160708/30dd3229/attachment.html From Nitin.Uikey at nttdata.com Fri Jul 8 04:30:23 2016 From: Nitin.Uikey at nttdata.com (Uikey, Nitin) Date: Fri, 8 Jul 2016 08:30:23 +0000 Subject: [Apiman-user] Regarding apiman deployment In-Reply-To: <7F9CC9E7FDAD3C4E9B251D35B702CF51314ED09A06@DC-SRV-MBX-08> References: <7F9CC9E7FDAD3C4E9B251D35B702CF51314ED09A06@DC-SRV-MBX-08> Message-ID: <61DB730F98162C4680731B3AE36AF95575E4A85D@MAIL703.KDS.KEANE.COM> Dear Ashish, We tried to follow the same steps as suggested in http://www.apiman.io/latest/download.html -> Tomcat 8+ and executed the following steps -> mkdir ~/apiman-1.2.7.Final cd ~/apiman-1.2.7.Final curl http://apache.mirrors.tds.net/tomcat/tomcat-8/v8.0.33/bin/apache-tomcat-8.0.33.zip -o apache-tomcat-8.0.33.zip curl http://downloads.jboss.org/apiman/1.2.7.Final/apiman-distro-tomcat8-1.2.7.Final-overlay.zip -o apiman-distro-tomcat8-1.2.7.Final-overlay.zip unzip apache-tomcat-8.0.33.zip unzip -o apiman-distro-tomcat8-1.2.7.Final-overlay.zip -d apache-tomcat-8.0.33 cd apache-tomcat-8.0.33 chmod 755 bin/catalina.sh ./bin/catalina.sh run $ cf push apiman We got following error -> Exception in thread "Thread-6" java.lang.RuntimeException: java.lang.RuntimeException: org.apache.http.conn.HttpHostConnectException: Connect to localhost:19200 [localhost/127.0.0.1] failed: Connection refused Do you have any idea about this issue? Thanks and Regards, Nitin Uikey From: Ashish Patel [mailto:Ashish.Patel at futureretail.in] Sent: 08 July 2016 10:03 To: Bargaje, Rushikesh; apiman-user at lists.jboss.org Cc: Wani, Nilesh; Bhisikar, Amit; Uikey, Nitin; Vaidya, Sagar Subject: RE: Regarding apiman deployment Hi Rushikesh, Yes, you can use tomcat for apiman evaluation. We used tomcat only - instructions from download page - http://imgur.com/rLOUZI8. So if you already have tomcat on PCF, you can refer extracting tomcat overlay zip directly. Thanks & Regards, Ashish Patel "Scientists investigate that which already is;Engineers create that which has never been." - Albert Einstein. From: apiman-user-bounces at lists.jboss.org [mailto:apiman-user-bounces at lists.jboss.org] On Behalf Of Bargaje, Rushikesh Sent: 07 July 2016 20:36 To: apiman-user at lists.jboss.org Cc: Wani, Nilesh; Bhisikar, Amit; Uikey, Nitin; Vaidya, Sagar Subject: [Apiman-user] Regarding apiman deployment Hi, We are evaluating apiman tool. We want to deploy this tool on pivotal cloud foundry (PCF). We are not able to deploy the tool as it is on PCF We tried to build the application but it is generating multiple war files. Is there any way to deploy those war files directly on Tomcat instead of using wildfly Platform? Thanks & Regards, RUSHIKESH BARGAJE | NTT DATA Global Delivery Services Private Limited | M.+ 91 7767987295 | rushikesh.bargaje at nttdata.com | Learn more at nttdata.com/americas ______________________________________________________________________ Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding. ________________________________ Disclaimer: This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not Future Group's. The recipient should check this email and attachments for the presence of viruses. Future Group accepts no liability for any damage caused by any virus transmitted by this email. Future Group may monitor and record all emails. ______________________________________________________________________ Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20160708/44f0e4ce/attachment-0001.html From eric.wittmann at redhat.com Mon Jul 11 07:20:54 2016 From: eric.wittmann at redhat.com (Eric Wittmann) Date: Mon, 11 Jul 2016 07:20:54 -0400 Subject: [Apiman-user] Regarding apiman deployment In-Reply-To: <7F9CC9E7FDAD3C4E9B251D35B702CF51314ED09E08@DC-SRV-MBX-08> References: <7F9CC9E7FDAD3C4E9B251D35B702CF51314ED09A06@DC-SRV-MBX-08> <61DB730F98162C4680731B3AE36AF95575E4A85D@MAIL703.KDS.KEANE.COM> <7F9CC9E7FDAD3C4E9B251D35B702CF51314ED09E08@DC-SRV-MBX-08> Message-ID: <33512d0d-a29c-9433-0731-e89487c8f5b0@redhat.com> There is a local instance of elasticsearch that gets started up as part of the apiman quickstart - that is what should be running on port 19200. If you're getting this error on startup, one of these problems may be occurring: * Port 19200 is blocked somehow * Elasticsearch failed to start * Apiman is trying to access Elasticsearch before it has fully started up Perhaps post your full tomcat startup log? -Eric On 7/8/2016 5:20 AM, Ashish Patel wrote: > Hi Nitin, > > > > It seems you are running under container/similar infra. Try giving all > ports access with in OR check in logs if any of the package service > deployment has failed. > > > > Hope this helps. > > > > Thanks & Regards, > > Ashish Patel > > > > "Scientists investigate that which already is;Engineers create that > which has never been." - Albert Einstein. > > > > > > *From:*Uikey, Nitin [mailto:Nitin.Uikey at nttdata.com] > *Sent:* 08 July 2016 14:00 > *To:* Ashish Patel; Bargaje, Rushikesh; apiman-user at lists.jboss.org > *Cc:* Wani, Nilesh; Bhisikar, Amit; Vaidya, Sagar > *Subject:* RE: Regarding apiman deployment > > > > Dear Ashish, > > > > We tried to follow the same steps as suggested in > http://www.apiman.io/latest/download.html -> Tomcat 8+ and executed the > following steps -> > > > > mkdir ~/apiman-1.2.7.Final > > cd ~/apiman-1.2.7.Final > > curl > http://apache.mirrors.tds.net/tomcat/tomcat-8/v8.0.33/bin/apache-tomcat-8.0.33.zip > -o apache-tomcat-8.0.33.zip > > curl > http://downloads.jboss.org/apiman/1.2.7.Final/apiman-distro-tomcat8-1.2.7.Final-overlay.zip > -o apiman-distro-tomcat8-1.2.7.Final-overlay.zip > > unzip apache-tomcat-8.0.33.zip > > unzip -o apiman-distro-tomcat8-1.2.7.Final-overlay.zip -d > apache-tomcat-8.0.33 > > cd apache-tomcat-8.0.33 > > chmod 755 bin/catalina.sh > > ./bin/catalina.sh run > > > > $ cf push apiman > > > > We got following error -> > > > > Exception in thread "Thread-6" java.lang.RuntimeException: > java.lang.RuntimeException: > org.apache.http.conn.HttpHostConnectException: Connect to > localhost:19200 [localhost/127.0.0.1] failed: Connection refused > > > > Do you have any idea about this issue? > > > > Thanks and Regards, > > Nitin Uikey > > > > > > *From:*Ashish Patel [mailto:Ashish.Patel at futureretail.in] > *Sent:* 08 July 2016 10:03 > *To:* Bargaje, Rushikesh; apiman-user at lists.jboss.org > *Cc:* Wani, Nilesh; Bhisikar, Amit; Uikey, Nitin; Vaidya, Sagar > *Subject:* RE: Regarding apiman deployment > > > > Hi Rushikesh, > > > > Yes, you can use tomcat for apiman evaluation. We used tomcat only - > instructions from download page - http://imgur.com/rLOUZI8. > > > > So if you already have tomcat on PCF, you can refer extracting tomcat > overlay zip directly. > > > > Thanks & Regards, > > Ashish Patel > > > > "Scientists investigate that which already is;Engineers create that > which has never been." - Albert Einstein. > > > > *From:*apiman-user-bounces at lists.jboss.org > [mailto:apiman-user-bounces at lists.jboss.org] *On Behalf Of *Bargaje, > Rushikesh > *Sent:* 07 July 2016 20:36 > *To:* apiman-user at lists.jboss.org > *Cc:* Wani, Nilesh; Bhisikar, Amit; Uikey, Nitin; Vaidya, Sagar > *Subject:* [Apiman-user] Regarding apiman deployment > > > > Hi, > > > > We are evaluating apiman tool. > > We want to deploy this tool on pivotal cloud foundry (PCF). > We are not able to deploy the tool as it is on PCF > > We tried to build the application but it is generating multiple war files. > > Is there any way to deploy those war files directly on Tomcat instead of > using wildfly Platform? > > > > > > Thanks & Regards, > > *RUSHIKESH BARGAJE* | NTT DATA Global Delivery Services Private Limited > | M.+ 91 7767987295 | rushikesh.bargaje at nttdata.com > | Learn more at nttdata.com/americas > > > > > ______________________________________________________________________ > Disclaimer: This email and any attachments are sent in strictest confidence > for the sole use of the addressee and may contain legally privileged, > confidential, and proprietary data. If you are not the intended recipient, > please advise the sender by replying promptly to this email and then delete > and destroy this email and any attachments without any further use, copying > or forwarding. > > > > ------------------------------------------------------------------------ > > Disclaimer: This message may contain privileged and confidential > information and is solely for the use of intended recipient. The views > expressed in this email are those of the sender and not Future Group's. > The recipient should check this email and attachments for the presence > of viruses. Future Group accepts no liability for any damage caused by > any virus transmitted by this email. Future Group may monitor and record > all emails. > > > ______________________________________________________________________ > Disclaimer: This email and any attachments are sent in strictest confidence > for the sole use of the addressee and may contain legally privileged, > confidential, and proprietary data. If you are not the intended recipient, > please advise the sender by replying promptly to this email and then delete > and destroy this email and any attachments without any further use, copying > or forwarding. > > > ------------------------------------------------------------------------ > Disclaimer: This message may contain privileged and confidential > information and is solely for the use of intended recipient. The views > expressed in this email are those of the sender and not Future Group's. > The recipient should check this email and attachments for the presence > of viruses. Future Group accepts no liability for any damage caused by > any virus transmitted by this email. Future Group may monitor and record > all emails. > > > _______________________________________________ > Apiman-user mailing list > Apiman-user at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/apiman-user > From Sagar.Vaidya at nttdata.com Mon Jul 11 09:52:05 2016 From: Sagar.Vaidya at nttdata.com (Vaidya, Sagar) Date: Mon, 11 Jul 2016 13:52:05 +0000 Subject: [Apiman-user] Regarding apiman deployment In-Reply-To: <33512d0d-a29c-9433-0731-e89487c8f5b0@redhat.com> References: <7F9CC9E7FDAD3C4E9B251D35B702CF51314ED09A06@DC-SRV-MBX-08> <61DB730F98162C4680731B3AE36AF95575E4A85D@MAIL703.KDS.KEANE.COM> <7F9CC9E7FDAD3C4E9B251D35B702CF51314ED09E08@DC-SRV-MBX-08> <33512d0d-a29c-9433-0731-e89487c8f5b0@redhat.com> Message-ID: Hi Eric, I have attached the startup log in the mail after deploying apiman on aws server. I followed the steps given in http://www.apiman.io/latest/download.html -> Tomcat 8+. Thanks and Regards, Sagar Vaidya -----Original Message----- From: Eric Wittmann [mailto:eric.wittmann at redhat.com] Sent: 11 July 2016 16:51 To: Ashish Patel; Uikey, Nitin; Bargaje, Rushikesh; apiman-user at lists.jboss.org Cc: Wani, Nilesh; Bhisikar, Amit; Vaidya, Sagar Subject: Re: [Apiman-user] Regarding apiman deployment There is a local instance of elasticsearch that gets started up as part of the apiman quickstart - that is what should be running on port 19200. If you're getting this error on startup, one of these problems may be occurring: * Port 19200 is blocked somehow * Elasticsearch failed to start * Apiman is trying to access Elasticsearch before it has fully started up Perhaps post your full tomcat startup log? -Eric On 7/8/2016 5:20 AM, Ashish Patel wrote: > Hi Nitin, > > > > It seems you are running under container/similar infra. Try giving all > ports access with in OR check in logs if any of the package service > deployment has failed. > > > > Hope this helps. > > > > Thanks & Regards, > > Ashish Patel > > > > "Scientists investigate that which already is;Engineers create that > which has never been." - Albert Einstein. > > > > > > *From:*Uikey, Nitin [mailto:Nitin.Uikey at nttdata.com] > *Sent:* 08 July 2016 14:00 > *To:* Ashish Patel; Bargaje, Rushikesh; apiman-user at lists.jboss.org > *Cc:* Wani, Nilesh; Bhisikar, Amit; Vaidya, Sagar > *Subject:* RE: Regarding apiman deployment > > > > Dear Ashish, > > > > We tried to follow the same steps as suggested in > http://www.apiman.io/latest/download.html -> Tomcat 8+ and executed > the following steps -> > > > > mkdir ~/apiman-1.2.7.Final > > cd ~/apiman-1.2.7.Final > > curl > http://apache.mirrors.tds.net/tomcat/tomcat-8/v8.0.33/bin/apache-tomca > t-8.0.33.zip > -o apache-tomcat-8.0.33.zip > > curl > http://downloads.jboss.org/apiman/1.2.7.Final/apiman-distro-tomcat8-1. > 2.7.Final-overlay.zip -o apiman-distro-tomcat8-1.2.7.Final-overlay.zip > > unzip apache-tomcat-8.0.33.zip > > unzip -o apiman-distro-tomcat8-1.2.7.Final-overlay.zip -d > apache-tomcat-8.0.33 > > cd apache-tomcat-8.0.33 > > chmod 755 bin/catalina.sh > > ./bin/catalina.sh run > > > > $ cf push apiman > > > > We got following error -> > > > > Exception in thread "Thread-6" java.lang.RuntimeException: > java.lang.RuntimeException: > org.apache.http.conn.HttpHostConnectException: Connect to > localhost:19200 [localhost/127.0.0.1] failed: Connection refused > > > > Do you have any idea about this issue? > > > > Thanks and Regards, > > Nitin Uikey > > > > > > *From:*Ashish Patel [mailto:Ashish.Patel at futureretail.in] > *Sent:* 08 July 2016 10:03 > *To:* Bargaje, Rushikesh; apiman-user at lists.jboss.org > *Cc:* Wani, Nilesh; Bhisikar, Amit; Uikey, Nitin; Vaidya, Sagar > *Subject:* RE: Regarding apiman deployment > > > > Hi Rushikesh, > > > > Yes, you can use tomcat for apiman evaluation. We used tomcat only - > instructions from download page - http://imgur.com/rLOUZI8. > > > > So if you already have tomcat on PCF, you can refer extracting tomcat > overlay zip directly. > > > > Thanks & Regards, > > Ashish Patel > > > > "Scientists investigate that which already is;Engineers create that > which has never been." - Albert Einstein. > > > > *From:*apiman-user-bounces at lists.jboss.org > [mailto:apiman-user-bounces at lists.jboss.org] *On Behalf Of *Bargaje, > Rushikesh > *Sent:* 07 July 2016 20:36 > *To:* apiman-user at lists.jboss.org > *Cc:* Wani, Nilesh; Bhisikar, Amit; Uikey, Nitin; Vaidya, Sagar > *Subject:* [Apiman-user] Regarding apiman deployment > > > > Hi, > > > > We are evaluating apiman tool. > > We want to deploy this tool on pivotal cloud foundry (PCF). > We are not able to deploy the tool as it is on PCF > > We tried to build the application but it is generating multiple war files. > > Is there any way to deploy those war files directly on Tomcat instead > of using wildfly Platform? > > > > > > Thanks & Regards, > > *RUSHIKESH BARGAJE* | NTT DATA Global Delivery Services Private > Limited > | M.+ 91 7767987295 | rushikesh.bargaje at nttdata.com > | Learn more at > nttdata.com/americas > > > > > ______________________________________________________________________ > Disclaimer: This email and any attachments are sent in strictest > confidence for the sole use of the addressee and may contain legally > privileged, confidential, and proprietary data. If you are not the > intended recipient, please advise the sender by replying promptly to > this email and then delete and destroy this email and any attachments > without any further use, copying or forwarding. > > > > ---------------------------------------------------------------------- > -- > > Disclaimer: This message may contain privileged and confidential > information and is solely for the use of intended recipient. The views > expressed in this email are those of the sender and not Future Group's. > The recipient should check this email and attachments for the presence > of viruses. Future Group accepts no liability for any damage caused by > any virus transmitted by this email. Future Group may monitor and > record all emails. > > > ______________________________________________________________________ > Disclaimer: This email and any attachments are sent in strictest > confidence for the sole use of the addressee and may contain legally > privileged, confidential, and proprietary data. If you are not the > intended recipient, please advise the sender by replying promptly to > this email and then delete and destroy this email and any attachments > without any further use, copying or forwarding. > > > ---------------------------------------------------------------------- > -- > Disclaimer: This message may contain privileged and confidential > information and is solely for the use of intended recipient. The views > expressed in this email are those of the sender and not Future Group's. > The recipient should check this email and attachments for the presence > of viruses. Future Group accepts no liability for any damage caused by > any virus transmitted by this email. Future Group may monitor and > record all emails. > > > _______________________________________________ > Apiman-user mailing list > Apiman-user at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/apiman-user > ______________________________________________________________________ Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: apiman-tomcat-log.txt Url: http://lists.jboss.org/pipermail/apiman-user/attachments/20160711/ca60fef1/attachment-0001.txt From eric.wittmann at redhat.com Mon Jul 11 10:52:47 2016 From: eric.wittmann at redhat.com (Eric Wittmann) Date: Mon, 11 Jul 2016 10:52:47 -0400 Subject: [Apiman-user] Regarding apiman deployment In-Reply-To: References: <7F9CC9E7FDAD3C4E9B251D35B702CF51314ED09A06@DC-SRV-MBX-08> <61DB730F98162C4680731B3AE36AF95575E4A85D@MAIL703.KDS.KEANE.COM> <7F9CC9E7FDAD3C4E9B251D35B702CF51314ED09E08@DC-SRV-MBX-08> <33512d0d-a29c-9433-0731-e89487c8f5b0@redhat.com> Message-ID: I don't see any red flags in the startup log, but the stdout messages don't appear to be included. Once you start up apiman, are you able to access elasticsearch on localhost:19200? -Eric On 7/11/2016 9:52 AM, Vaidya, Sagar wrote: > Hi Eric, > > I have attached the startup log in the mail after deploying apiman on aws server. I followed the steps given in http://www.apiman.io/latest/download.html -> Tomcat 8+. > > Thanks and Regards, > Sagar Vaidya > > -----Original Message----- > From: Eric Wittmann [mailto:eric.wittmann at redhat.com] > Sent: 11 July 2016 16:51 > To: Ashish Patel; Uikey, Nitin; Bargaje, Rushikesh; apiman-user at lists.jboss.org > Cc: Wani, Nilesh; Bhisikar, Amit; Vaidya, Sagar > Subject: Re: [Apiman-user] Regarding apiman deployment > > There is a local instance of elasticsearch that gets started up as part of the apiman quickstart - that is what should be running on port 19200. > If you're getting this error on startup, one of these problems may be > occurring: > > * Port 19200 is blocked somehow > * Elasticsearch failed to start > * Apiman is trying to access Elasticsearch before it has fully started up > > Perhaps post your full tomcat startup log? > > -Eric > > On 7/8/2016 5:20 AM, Ashish Patel wrote: >> Hi Nitin, >> >> >> >> It seems you are running under container/similar infra. Try giving all >> ports access with in OR check in logs if any of the package service >> deployment has failed. >> >> >> >> Hope this helps. >> >> >> >> Thanks & Regards, >> >> Ashish Patel >> >> >> >> "Scientists investigate that which already is;Engineers create that >> which has never been." - Albert Einstein. >> >> >> >> >> >> *From:*Uikey, Nitin [mailto:Nitin.Uikey at nttdata.com] >> *Sent:* 08 July 2016 14:00 >> *To:* Ashish Patel; Bargaje, Rushikesh; apiman-user at lists.jboss.org >> *Cc:* Wani, Nilesh; Bhisikar, Amit; Vaidya, Sagar >> *Subject:* RE: Regarding apiman deployment >> >> >> >> Dear Ashish, >> >> >> >> We tried to follow the same steps as suggested in >> http://www.apiman.io/latest/download.html -> Tomcat 8+ and executed >> the following steps -> >> >> >> >> mkdir ~/apiman-1.2.7.Final >> >> cd ~/apiman-1.2.7.Final >> >> curl >> http://apache.mirrors.tds.net/tomcat/tomcat-8/v8.0.33/bin/apache-tomca >> t-8.0.33.zip >> -o apache-tomcat-8.0.33.zip >> >> curl >> http://downloads.jboss.org/apiman/1.2.7.Final/apiman-distro-tomcat8-1. >> 2.7.Final-overlay.zip -o apiman-distro-tomcat8-1.2.7.Final-overlay.zip >> >> unzip apache-tomcat-8.0.33.zip >> >> unzip -o apiman-distro-tomcat8-1.2.7.Final-overlay.zip -d >> apache-tomcat-8.0.33 >> >> cd apache-tomcat-8.0.33 >> >> chmod 755 bin/catalina.sh >> >> ./bin/catalina.sh run >> >> >> >> $ cf push apiman >> >> >> >> We got following error -> >> >> >> >> Exception in thread "Thread-6" java.lang.RuntimeException: >> java.lang.RuntimeException: >> org.apache.http.conn.HttpHostConnectException: Connect to >> localhost:19200 [localhost/127.0.0.1] failed: Connection refused >> >> >> >> Do you have any idea about this issue? >> >> >> >> Thanks and Regards, >> >> Nitin Uikey >> >> >> >> >> >> *From:*Ashish Patel [mailto:Ashish.Patel at futureretail.in] >> *Sent:* 08 July 2016 10:03 >> *To:* Bargaje, Rushikesh; apiman-user at lists.jboss.org >> *Cc:* Wani, Nilesh; Bhisikar, Amit; Uikey, Nitin; Vaidya, Sagar >> *Subject:* RE: Regarding apiman deployment >> >> >> >> Hi Rushikesh, >> >> >> >> Yes, you can use tomcat for apiman evaluation. We used tomcat only - >> instructions from download page - http://imgur.com/rLOUZI8. >> >> >> >> So if you already have tomcat on PCF, you can refer extracting tomcat >> overlay zip directly. >> >> >> >> Thanks & Regards, >> >> Ashish Patel >> >> >> >> "Scientists investigate that which already is;Engineers create that >> which has never been." - Albert Einstein. >> >> >> >> *From:*apiman-user-bounces at lists.jboss.org >> [mailto:apiman-user-bounces at lists.jboss.org] *On Behalf Of *Bargaje, >> Rushikesh >> *Sent:* 07 July 2016 20:36 >> *To:* apiman-user at lists.jboss.org >> *Cc:* Wani, Nilesh; Bhisikar, Amit; Uikey, Nitin; Vaidya, Sagar >> *Subject:* [Apiman-user] Regarding apiman deployment >> >> >> >> Hi, >> >> >> >> We are evaluating apiman tool. >> >> We want to deploy this tool on pivotal cloud foundry (PCF). >> We are not able to deploy the tool as it is on PCF >> >> We tried to build the application but it is generating multiple war files. >> >> Is there any way to deploy those war files directly on Tomcat instead >> of using wildfly Platform? >> >> >> >> >> >> Thanks & Regards, >> >> *RUSHIKESH BARGAJE* | NTT DATA Global Delivery Services Private >> Limited >> | M.+ 91 7767987295 | rushikesh.bargaje at nttdata.com >> | Learn more at >> nttdata.com/americas >> >> >> >> >> ______________________________________________________________________ >> Disclaimer: This email and any attachments are sent in strictest >> confidence for the sole use of the addressee and may contain legally >> privileged, confidential, and proprietary data. If you are not the >> intended recipient, please advise the sender by replying promptly to >> this email and then delete and destroy this email and any attachments >> without any further use, copying or forwarding. >> >> >> >> ---------------------------------------------------------------------- >> -- >> >> Disclaimer: This message may contain privileged and confidential >> information and is solely for the use of intended recipient. The views >> expressed in this email are those of the sender and not Future Group's. >> The recipient should check this email and attachments for the presence >> of viruses. Future Group accepts no liability for any damage caused by >> any virus transmitted by this email. Future Group may monitor and >> record all emails. >> >> >> ______________________________________________________________________ >> Disclaimer: This email and any attachments are sent in strictest >> confidence for the sole use of the addressee and may contain legally >> privileged, confidential, and proprietary data. If you are not the >> intended recipient, please advise the sender by replying promptly to >> this email and then delete and destroy this email and any attachments >> without any further use, copying or forwarding. >> >> >> ---------------------------------------------------------------------- >> -- >> Disclaimer: This message may contain privileged and confidential >> information and is solely for the use of intended recipient. The views >> expressed in this email are those of the sender and not Future Group's. >> The recipient should check this email and attachments for the presence >> of viruses. Future Group accepts no liability for any damage caused by >> any virus transmitted by this email. Future Group may monitor and >> record all emails. >> >> >> _______________________________________________ >> Apiman-user mailing list >> Apiman-user at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/apiman-user >> > > ______________________________________________________________________ > Disclaimer: This email and any attachments are sent in strictest confidence > for the sole use of the addressee and may contain legally privileged, > confidential, and proprietary data. If you are not the intended recipient, > please advise the sender by replying promptly to this email and then delete > and destroy this email and any attachments without any further use, copying > or forwarding. > From tomas.zuklys at gmail.com Wed Jul 13 04:36:22 2016 From: tomas.zuklys at gmail.com (=?UTF-8?Q?Tomas_=C5=BDuklys?=) Date: Wed, 13 Jul 2016 11:36:22 +0300 Subject: [Apiman-user] Where should I register issues? Message-ID: Hi, Could you tell me where APIMAN issues should be registered? As I undertstand, official bug tracking system (the one that is provided in APIMAN web page) is: https://issues.jboss.org/projects/APIMAN However, people also register tickets in github where the source code is: https://github.com/apiman So where should I register tickets: - jboss ? - github ? - both ? Best regards, Tomas -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20160713/d647282c/attachment.html From jcechace at gmail.com Wed Jul 13 06:01:08 2016 From: jcechace at gmail.com (=?UTF-8?B?SmFrdWIgxIxlY2jDocSNZWs=?=) Date: Wed, 13 Jul 2016 12:01:08 +0200 Subject: [Apiman-user] Where should I register issues? In-Reply-To: References: Message-ID: Hello Tomas, https://issues.jboss.org/projects/APIMAN is the right place to submit discovered issues for sure. - Jakub. On Wed, Jul 13, 2016 at 10:36 AM, Tomas ?uklys wrote: > Hi, > > Could you tell me where APIMAN issues should be registered? > > As I undertstand, official bug tracking system (the one that is provided > in APIMAN web page) is: https://issues.jboss.org/projects/APIMAN > > However, people also register tickets in github where the source code is: > https://github.com/apiman > > So where should I register tickets: > - jboss ? > - github ? > - both ? > > Best regards, > Tomas > > _______________________________________________ > 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/20160713/6a231887/attachment.html From tomas.zuklys at gmail.com Wed Jul 13 07:33:31 2016 From: tomas.zuklys at gmail.com (=?UTF-8?Q?Tomas_=C5=BDuklys?=) Date: Wed, 13 Jul 2016 14:33:31 +0300 Subject: [Apiman-user] Where should I register issues? In-Reply-To: References: Message-ID: Thanks Jakub. On 13 July 2016 at 13:01, Jakub ?ech??ek wrote: > Hello Tomas, > > https://issues.jboss.org/projects/APIMAN is the right place to submit > discovered issues for sure. > > > - Jakub. > > > > > On Wed, Jul 13, 2016 at 10:36 AM, Tomas ?uklys > wrote: > >> Hi, >> >> Could you tell me where APIMAN issues should be registered? >> >> As I undertstand, official bug tracking system (the one that is provided >> in APIMAN web page) is: https://issues.jboss.org/projects/APIMAN >> >> However, people also register tickets in github where the source code is: >> https://github.com/apiman >> >> So where should I register tickets: >> - jboss ? >> - github ? >> - both ? >> >> Best regards, >> Tomas >> >> _______________________________________________ >> 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/20160713/2e1cea48/attachment.html From eric.wittmann at redhat.com Wed Jul 13 07:48:00 2016 From: eric.wittmann at redhat.com (Eric Wittmann) Date: Wed, 13 Jul 2016 14:48:00 +0300 Subject: [Apiman-user] Where should I register issues? In-Reply-To: References: Message-ID: <46511bee-594b-f2d0-cf69-5e370d493926@redhat.com> +1 I didn't realize you could turn off the github "Issues" feature for repositories! So I have done that to avoid future confusion. :) -Eric On 7/13/2016 1:01 PM, Jakub ?ech??ek wrote: > Hello Tomas, > > https://issues.jboss.org/projects/APIMAN is the right place to submit > discovered issues for sure. > > > - Jakub. > > > > > On Wed, Jul 13, 2016 at 10:36 AM, Tomas ?uklys > wrote: > > Hi, > > Could you tell me where APIMAN issues should be registered? > > As I undertstand, official bug tracking system (the one that is > provided in APIMAN web page) is: > https://issues.jboss.org/projects/APIMAN > > However, people also register tickets in github where the source > code is: https://github.com/apiman > > So where should I register tickets: > - jboss ? > - github ? > - both ? > > Best regards, > Tomas > > _______________________________________________ > 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 > From tomas.zuklys at gmail.com Fri Jul 15 08:19:27 2016 From: tomas.zuklys at gmail.com (=?UTF-8?Q?Tomas_=C5=BDuklys?=) Date: Fri, 15 Jul 2016 15:19:27 +0300 Subject: [Apiman-user] Comercial support Message-ID: Hi, As far as I know, Red Hat does not provide commercial support for APIMAN. Is any kind of commercial support possible for current APIMAN? 24x7? 8x5? Other? Best regards, Tomas Zuklys -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20160715/b457d085/attachment.html From eric.wittmann at redhat.com Fri Jul 15 09:07:21 2016 From: eric.wittmann at redhat.com (Eric Wittmann) Date: Fri, 15 Jul 2016 09:07:21 -0400 Subject: [Apiman-user] Comercial support In-Reply-To: References: Message-ID: Apiman is purely an open source project, and as such does not offer commercial support. Red Hat's business model is to create subscription based, commercially supported products based on open source upstream projects such as apiman. To that end, we were actively working towards creating a supported product based on apiman. However, recently Red Hat acquired the API Management company 3scale, which has resulted in a change of product direction. You can read more here if you haven't yet: http://www.apiman.io/blog/apiman/3scale/2016/06/22/redhat-3scale-apiman.html We are currently working through how best to combine our efforts (3scale and apiman) in a way that best supports both communities. I should have some more specifics for the apiman community soon (hopefully next week). Of course it goes without saying that the apiman team is incredibly grateful for the wonderful open source community that has grown up around the project, and we are committed to supporting it as best we can. -Eric On 7/15/2016 8:19 AM, Tomas ?uklys wrote: > Hi, > > As far as I know, Red Hat does not provide commercial support for APIMAN. > > Is any kind of commercial support possible for current APIMAN? > 24x7? > 8x5? > Other? > > Best regards, > Tomas Zuklys > > > > > > _______________________________________________ > Apiman-user mailing list > Apiman-user at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/apiman-user > From tomas.zuklys at gmail.com Fri Jul 15 09:21:49 2016 From: tomas.zuklys at gmail.com (=?UTF-8?Q?Tomas_=C5=BDuklys?=) Date: Fri, 15 Jul 2016 16:21:49 +0300 Subject: [Apiman-user] Comercial support In-Reply-To: References: Message-ID: Thanks for the info Eric. On 15 July 2016 at 16:07, Eric Wittmann wrote: > Apiman is purely an open source project, and as such does not offer > commercial support. Red Hat's business model is to create subscription > based, commercially supported products based on open source upstream > projects such as apiman. > > To that end, we were actively working towards creating a supported product > based on apiman. However, recently Red Hat acquired the API Management > company 3scale, which has resulted in a change of product direction. You > can read more here if you haven't yet: > > > http://www.apiman.io/blog/apiman/3scale/2016/06/22/redhat-3scale-apiman.html > > We are currently working through how best to combine our efforts (3scale > and apiman) in a way that best supports both communities. I should have > some more specifics for the apiman community soon (hopefully next week). > > Of course it goes without saying that the apiman team is incredibly > grateful for the wonderful open source community that has grown up around > the project, and we are committed to supporting it as best we can. > > -Eric > > > > On 7/15/2016 8:19 AM, Tomas ?uklys wrote: > >> Hi, >> >> As far as I know, Red Hat does not provide commercial support for APIMAN. >> >> Is any kind of commercial support possible for current APIMAN? >> 24x7? >> 8x5? >> Other? >> >> Best regards, >> Tomas Zuklys >> >> >> >> >> >> _______________________________________________ >> 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/20160715/a448856a/attachment.html From junior.jairo1 at gmail.com Fri Jul 22 07:22:44 2016 From: junior.jairo1 at gmail.com (Jairo Junior) Date: Fri, 22 Jul 2016 11:22:44 +0000 Subject: [Apiman-user] 401 on a CORS preflight request Message-ID: I've been trying to setup apiman + keycloak-oauth-plugin + keycloak + keycloak.js with a client-side angularjs app and a REST API. It's a scenario very similar to https://github.com/keycloak/keycloak/tree/master/examples/demo-template/angular-product-app, but with apiman and CORS. My test are going well with curl, but using my javascript app the browser it is performing a CORS preflight OPTIONS request without authorization header. OPTIONS request works well with authorization header using curl, therefore, I'm not sure whether the browser should include authorization header or apiman should allows CORS preflight requests (OPTIONS) without authorization header. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20160722/fb345c83/attachment.html From eric.wittmann at redhat.com Fri Jul 22 07:29:53 2016 From: eric.wittmann at redhat.com (Eric Wittmann) Date: Fri, 22 Jul 2016 07:29:53 -0400 Subject: [Apiman-user] 401 on a CORS preflight request In-Reply-To: References: Message-ID: <3724e831-5086-42bd-4979-d349d372c87b@redhat.com> Apiman should allow OPTIONS requests without requiring authorization. What is your setup/configuration (which app server, etc)? Also what apiman REST endpoints are you trying to access? -Eric On 7/22/2016 7:22 AM, Jairo Junior wrote: > I've been trying to setup apiman + keycloak-oauth-plugin + keycloak + > keycloak.js with a client-side angularjs app and a REST API. It's a > scenario very similar to > https://github.com/keycloak/keycloak/tree/master/examples/demo-template/angular-product-app, > but with apiman and CORS. > > My test are going well with curl, but using my javascript app the > browser it is performing a CORS preflight OPTIONS request without > authorization header. > > OPTIONS request works well with authorization header using curl, > therefore, I'm not sure whether the browser should include authorization > header or apiman should allows CORS preflight requests (OPTIONS) without > authorization header. > > > _______________________________________________ > Apiman-user mailing list > Apiman-user at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/apiman-user > From junior.jairo1 at gmail.com Fri Jul 22 07:55:20 2016 From: junior.jairo1 at gmail.com (Jairo Junior) Date: Fri, 22 Jul 2016 11:55:20 +0000 Subject: [Apiman-user] 401 on a CORS preflight request In-Reply-To: <3724e831-5086-42bd-4979-d349d372c87b@redhat.com> References: <3724e831-5086-42bd-4979-d349d372c87b@redhat.com> Message-ID: EAP 7.0 + apiman 1.2.7 overlay, but I've also tried with docker image apiman/on-wildfly10:1.2.7.Final /apiman-gateway/org/service/1.0 with Keycloak OAuth Policy On Fri, Jul 22, 2016 at 8:29 AM Eric Wittmann wrote: > Apiman should allow OPTIONS requests without requiring authorization. > What is your setup/configuration (which app server, etc)? Also what > apiman REST endpoints are you trying to access? > > -Eric > > On 7/22/2016 7:22 AM, Jairo Junior wrote: > > I've been trying to setup apiman + keycloak-oauth-plugin + keycloak + > > keycloak.js with a client-side angularjs app and a REST API. It's a > > scenario very similar to > > > https://github.com/keycloak/keycloak/tree/master/examples/demo-template/angular-product-app > , > > but with apiman and CORS. > > > > My test are going well with curl, but using my javascript app the > > browser it is performing a CORS preflight OPTIONS request without > > authorization header. > > > > OPTIONS request works well with authorization header using curl, > > therefore, I'm not sure whether the browser should include authorization > > header or apiman should allows CORS preflight requests (OPTIONS) without > > authorization header. > > > > > > _______________________________________________ > > 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/20160722/a4af1ae8/attachment.html From eric.wittmann at redhat.com Fri Jul 22 08:15:18 2016 From: eric.wittmann at redhat.com (Eric Wittmann) Date: Fri, 22 Jul 2016 08:15:18 -0400 Subject: [Apiman-user] 401 on a CORS preflight request In-Reply-To: References: <3724e831-5086-42bd-4979-d349d372c87b@redhat.com> Message-ID: <384d9f56-b22e-3feb-0be5-31a7341c0b94@redhat.com> Thanks for the info. You've hit a bug in apiman, unfortunately. I have created a ticket for this bug here: https://issues.jboss.org/browse/APIMAN-1209 You can resolve (workaround) this issue locally (without rebuilding apiman) or you can wait for us to fix the bug and release a new version. If you would like instructions on how to workaround the bug locally let me know. -Eric On 7/22/2016 7:55 AM, Jairo Junior wrote: > EAP 7.0 + apiman 1.2.7 overlay, but I've also tried with docker image > apiman/on-wildfly10:1.2.7.Final > > /apiman-gateway/org/service/1.0 with Keycloak OAuth Policy > > On Fri, Jul 22, 2016 at 8:29 AM Eric Wittmann > wrote: > > Apiman should allow OPTIONS requests without requiring authorization. > What is your setup/configuration (which app server, etc)? Also what > apiman REST endpoints are you trying to access? > > -Eric > > On 7/22/2016 7:22 AM, Jairo Junior wrote: > > I've been trying to setup apiman + keycloak-oauth-plugin + keycloak + > > keycloak.js with a client-side angularjs app and a REST API. It's a > > scenario very similar to > > > https://github.com/keycloak/keycloak/tree/master/examples/demo-template/angular-product-app, > > but with apiman and CORS. > > > > My test are going well with curl, but using my javascript app the > > browser it is performing a CORS preflight OPTIONS request without > > authorization header. > > > > OPTIONS request works well with authorization header using curl, > > therefore, I'm not sure whether the browser should include > authorization > > header or apiman should allows CORS preflight requests (OPTIONS) > without > > authorization header. > > > > > > _______________________________________________ > > Apiman-user mailing list > > Apiman-user at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/apiman-user > > > From junior.jairo1 at gmail.com Fri Jul 22 08:23:07 2016 From: junior.jairo1 at gmail.com (Jairo Junior) Date: Fri, 22 Jul 2016 12:23:07 +0000 Subject: [Apiman-user] 401 on a CORS preflight request In-Reply-To: <384d9f56-b22e-3feb-0be5-31a7341c0b94@redhat.com> References: <3724e831-5086-42bd-4979-d349d372c87b@redhat.com> <384d9f56-b22e-3feb-0be5-31a7341c0b94@redhat.com> Message-ID: I would like the workaround. =) On Fri, Jul 22, 2016 at 9:15 AM Eric Wittmann wrote: > Thanks for the info. You've hit a bug in apiman, unfortunately. I have > created a ticket for this bug here: > > https://issues.jboss.org/browse/APIMAN-1209 > > You can resolve (workaround) this issue locally (without rebuilding > apiman) or you can wait for us to fix the bug and release a new version. > If you would like instructions on how to workaround the bug locally > let me know. > > -Eric > > On 7/22/2016 7:55 AM, Jairo Junior wrote: > > EAP 7.0 + apiman 1.2.7 overlay, but I've also tried with docker image > > apiman/on-wildfly10:1.2.7.Final > > > > /apiman-gateway/org/service/1.0 with Keycloak OAuth Policy > > > > On Fri, Jul 22, 2016 at 8:29 AM Eric Wittmann > > wrote: > > > > Apiman should allow OPTIONS requests without requiring authorization. > > What is your setup/configuration (which app server, etc)? Also what > > apiman REST endpoints are you trying to access? > > > > -Eric > > > > On 7/22/2016 7:22 AM, Jairo Junior wrote: > > > I've been trying to setup apiman + keycloak-oauth-plugin + > keycloak + > > > keycloak.js with a client-side angularjs app and a REST API. It's a > > > scenario very similar to > > > > > > https://github.com/keycloak/keycloak/tree/master/examples/demo-template/angular-product-app > , > > > but with apiman and CORS. > > > > > > My test are going well with curl, but using my javascript app the > > > browser it is performing a CORS preflight OPTIONS request without > > > authorization header. > > > > > > OPTIONS request works well with authorization header using curl, > > > therefore, I'm not sure whether the browser should include > > authorization > > > header or apiman should allows CORS preflight requests (OPTIONS) > > without > > > authorization header. > > > > > > > > > _______________________________________________ > > > 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/20160722/56f16f0c/attachment.html From eric.wittmann at redhat.com Fri Jul 22 09:59:51 2016 From: eric.wittmann at redhat.com (Eric Wittmann) Date: Fri, 22 Jul 2016 09:59:51 -0400 Subject: [Apiman-user] 401 on a CORS preflight request In-Reply-To: References: <3724e831-5086-42bd-4979-d349d372c87b@redhat.com> <384d9f56-b22e-3feb-0be5-31a7341c0b94@redhat.com> Message-ID: <540045d4-da5e-7a41-d9f9-7a08f2b1a6a3@redhat.com> Sure thing! The problem is that the web.xml file in the apiman-gateway-api.war web application is too restrictive. This is what I mean: https://github.com/apiman/apiman/blob/master/gateway/platforms/war/wildfly8/api/src/main/webapp/WEB-INF/web.xml#L40-L48 That security constraint is too restrictive. The should specify which http methods to secure. Because it doesn't do this, *all* of the http methods are secured by default. Here is an example that does it correctly with respect to CORS: https://github.com/apiman/apiman/blob/master/manager/api/war/wildfly8/src/main/webapp/WEB-INF/web.xml#L74-L82 So here's what you need to do: 1) unpack WILDFLY/standalone/deployments/apiman-gateway-api.war 2) open the WEB-INF/web.xml file in a text editor 3) add the following XML markup after line 43: GET POST PUT DELETE HEAD 4) save the web.xml changes 5) re-zip everything, resulting in a new version of apiman-gateway-api.war 6) deploy the new version of apiman-gateway-api.war to Wildfly, replacing the old version 7) start wildfly 8) profit! -Eric On 7/22/2016 8:23 AM, Jairo Junior wrote: > I would like the workaround. =) > > On Fri, Jul 22, 2016 at 9:15 AM Eric Wittmann > wrote: > > Thanks for the info. You've hit a bug in apiman, unfortunately. I have > created a ticket for this bug here: > > https://issues.jboss.org/browse/APIMAN-1209 > > You can resolve (workaround) this issue locally (without rebuilding > apiman) or you can wait for us to fix the bug and release a new version. > If you would like instructions on how to workaround the bug locally > let me know. > > -Eric > > On 7/22/2016 7:55 AM, Jairo Junior wrote: > > EAP 7.0 + apiman 1.2.7 overlay, but I've also tried with docker image > > apiman/on-wildfly10:1.2.7.Final > > > > /apiman-gateway/org/service/1.0 with Keycloak OAuth Policy > > > > On Fri, Jul 22, 2016 at 8:29 AM Eric Wittmann > > > >> wrote: > > > > Apiman should allow OPTIONS requests without requiring > authorization. > > What is your setup/configuration (which app server, etc)? > Also what > > apiman REST endpoints are you trying to access? > > > > -Eric > > > > On 7/22/2016 7:22 AM, Jairo Junior wrote: > > > I've been trying to setup apiman + keycloak-oauth-plugin + > keycloak + > > > keycloak.js with a client-side angularjs app and a REST API. > It's a > > > scenario very similar to > > > > > > https://github.com/keycloak/keycloak/tree/master/examples/demo-template/angular-product-app, > > > but with apiman and CORS. > > > > > > My test are going well with curl, but using my javascript > app the > > > browser it is performing a CORS preflight OPTIONS request > without > > > authorization header. > > > > > > OPTIONS request works well with authorization header using curl, > > > therefore, I'm not sure whether the browser should include > > authorization > > > header or apiman should allows CORS preflight requests (OPTIONS) > > without > > > authorization header. > > > > > > > > > _______________________________________________ > > > Apiman-user mailing list > > > Apiman-user at lists.jboss.org > > > > > > https://lists.jboss.org/mailman/listinfo/apiman-user > > > > > > From junior.jairo1 at gmail.com Fri Jul 22 11:02:39 2016 From: junior.jairo1 at gmail.com (Jairo Junior) Date: Fri, 22 Jul 2016 15:02:39 +0000 Subject: [Apiman-user] 401 on a CORS preflight request In-Reply-To: <540045d4-da5e-7a41-d9f9-7a08f2b1a6a3@redhat.com> References: <3724e831-5086-42bd-4979-d349d372c87b@redhat.com> <384d9f56-b22e-3feb-0be5-31a7341c0b94@redhat.com> <540045d4-da5e-7a41-d9f9-7a08f2b1a6a3@redhat.com> Message-ID: Had to create a new version of my API and re-publish, but it worked. Thank you. On Fri, Jul 22, 2016 at 10:59 AM Eric Wittmann wrote: > Sure thing! The problem is that the web.xml file in the > apiman-gateway-api.war web application is too restrictive. This is what > I mean: > > > https://github.com/apiman/apiman/blob/master/gateway/platforms/war/wildfly8/api/src/main/webapp/WEB-INF/web.xml#L40-L48 > > That security constraint is too restrictive. The > should specify which http methods to secure. > Because it doesn't do this, *all* of the http methods are secured by > default. Here is an example that does it correctly with respect to CORS: > > > https://github.com/apiman/apiman/blob/master/manager/api/war/wildfly8/src/main/webapp/WEB-INF/web.xml#L74-L82 > > So here's what you need to do: > > 1) unpack WILDFLY/standalone/deployments/apiman-gateway-api.war > 2) open the WEB-INF/web.xml file in a text editor > 3) add the following XML markup after line 43: > > GET > POST > PUT > DELETE > HEAD > > 4) save the web.xml changes > 5) re-zip everything, resulting in a new version of > apiman-gateway-api.war > 6) deploy the new version of apiman-gateway-api.war to Wildfly, > replacing the old version > 7) start wildfly > 8) profit! > > -Eric > > On 7/22/2016 8:23 AM, Jairo Junior wrote: > > I would like the workaround. =) > > > > On Fri, Jul 22, 2016 at 9:15 AM Eric Wittmann > > wrote: > > > > Thanks for the info. You've hit a bug in apiman, unfortunately. I > have > > created a ticket for this bug here: > > > > https://issues.jboss.org/browse/APIMAN-1209 > > > > You can resolve (workaround) this issue locally (without rebuilding > > apiman) or you can wait for us to fix the bug and release a new > version. > > If you would like instructions on how to workaround the bug locally > > let me know. > > > > -Eric > > > > On 7/22/2016 7:55 AM, Jairo Junior wrote: > > > EAP 7.0 + apiman 1.2.7 overlay, but I've also tried with docker > image > > > apiman/on-wildfly10:1.2.7.Final > > > > > > /apiman-gateway/org/service/1.0 with Keycloak OAuth Policy > > > > > > On Fri, Jul 22, 2016 at 8:29 AM Eric Wittmann > > > > > > >> wrote: > > > > > > Apiman should allow OPTIONS requests without requiring > > authorization. > > > What is your setup/configuration (which app server, etc)? > > Also what > > > apiman REST endpoints are you trying to access? > > > > > > -Eric > > > > > > On 7/22/2016 7:22 AM, Jairo Junior wrote: > > > > I've been trying to setup apiman + keycloak-oauth-plugin + > > keycloak + > > > > keycloak.js with a client-side angularjs app and a REST API. > > It's a > > > > scenario very similar to > > > > > > > > > > https://github.com/keycloak/keycloak/tree/master/examples/demo-template/angular-product-app > , > > > > but with apiman and CORS. > > > > > > > > My test are going well with curl, but using my javascript > > app the > > > > browser it is performing a CORS preflight OPTIONS request > > without > > > > authorization header. > > > > > > > > OPTIONS request works well with authorization header using > curl, > > > > therefore, I'm not sure whether the browser should include > > > authorization > > > > header or apiman should allows CORS preflight requests > (OPTIONS) > > > without > > > > authorization header. > > > > > > > > > > > > _______________________________________________ > > > > 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/20160722/cab4e81c/attachment-0001.html From junior.jairo1 at gmail.com Mon Jul 25 09:14:33 2016 From: junior.jairo1 at gmail.com (Jairo Junior) Date: Mon, 25 Jul 2016 13:14:33 +0000 Subject: [Apiman-user] Content-type header included in gateway DELETE requests to endpoint Message-ID: A client-side javascript app is performing the following request: *DELETE /apiman-gateway/org/service/1.1/resource/7 HTTP/1.1Host: 172.17.0.1:8080 User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0Accept: application/json, text/plain, */*Accept-Language: en-US,en;q=0.5Accept-Encoding: gzip, deflateAuthorization: Bearer $ACCESS_TOKENReferer: http://172.17.0.1:3000/ Origin: http://172.17.0.1:3000 Connection: keep-alive* But the gateway is performing the following request to the endpoint: *DELETE /service/rest/resource/7 HTTP/1.1User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)Origin: http://172.17.0.1:3000 Accept-Language: en-US,en;q=0.5Accept-Encoding: gzip, deflateConnection: keep-aliveAuthorization: Bearer $ACCESS_TOKENAccept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/msword, application/vnd.ms-powerpoint, */*Referer: http://172.17.0.1:3000/ Host: 172.17.0.1:8280 Content-Type: application/x-www-form-* *urlencodedContent-Length: 0* Resulting in a 415 Unsupported Media Type at the endpoint. GET, POST and PUT requests are OK. Only using CORS Policy for this endpoint: *Access-Control-Allow-Origin: *Access-Control-Allow-Credentials: trueAccess-Control-Allow-Headers: accept, authrotization, content-typeAccess-Control-Allow-Methods: GET, POST, PUT, DELETEAccess-Control-Max-Age: 3600* -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20160725/a814c67e/attachment.html From eric.wittmann at redhat.com Mon Jul 25 09:49:20 2016 From: eric.wittmann at redhat.com (Eric Wittmann) Date: Mon, 25 Jul 2016 09:49:20 -0400 Subject: [Apiman-user] Content-type header included in gateway DELETE requests to endpoint In-Reply-To: References: Message-ID: <5c9c76cf-a037-0e22-d3a5-7de4080f6b33@redhat.com> JIRA issue created. In case you want to track it: https://issues.jboss.org/browse/APIMAN-1210 -Eric On 7/25/2016 9:14 AM, Jairo Junior wrote: > A client-side javascript app is performing the following request: > > /DELETE /apiman-gateway/org/service/1.1/resource/7 HTTP/1.1 > Host: 172.17.0.1:8080 > User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:47.0) > Gecko/20100101 Firefox/47.0 > Accept: application/json, text/plain, */* > Accept-Language: en-US,en;q=0.5 > Accept-Encoding: gzip, deflate > Authorization: Bearer $ACCESS_TOKEN > Referer: http://172.17.0.1:3000/ > Origin: http://172.17.0.1:3000 > Connection: keep-alive > > / > But the gateway is performing the following request to the endpoint: > > /DELETE /service/rest/resource/7 HTTP/1.1 > User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) > Origin: http://172.17.0.1:3000 > Accept-Language: en-US,en;q=0.5 > Accept-Encoding: gzip, deflate > Connection: keep-alive > Authorization: Bearer $ACCESS_TOKEN > Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, > application/vnd.ms-excel, application/msword, > application/vnd.ms-powerpoint, */* > Referer: http://172.17.0.1:3000/ > Host: 172.17.0.1:8280 > Content-Type: application/x-www-form-//urlencoded > Content-Length: 0 > > / > Resulting in a 415 Unsupported Media Type at the endpoint. > > GET, POST and PUT requests are OK. > > Only using CORS Policy for this endpoint: > > /Access-Control-Allow-Origin: * > Access-Control-Allow-Credentials: true > Access-Control-Allow-Headers: accept, authrotization, content-type > Access-Control-Allow-Methods: GET, POST, PUT, DELETE > Access-Control-Max-Age: 3600/ > > > _______________________________________________ > Apiman-user mailing list > Apiman-user at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/apiman-user > From junior.jairo1 at gmail.com Mon Jul 25 10:06:27 2016 From: junior.jairo1 at gmail.com (Jairo Junior) Date: Mon, 25 Jul 2016 14:06:27 +0000 Subject: [Apiman-user] Content-type header included in gateway DELETE requests to endpoint In-Reply-To: <5c9c76cf-a037-0e22-d3a5-7de4080f6b33@redhat.com> References: <5c9c76cf-a037-0e22-d3a5-7de4080f6b33@redhat.com> Message-ID: Thanks again. On Mon, Jul 25, 2016 at 10:49 AM Eric Wittmann wrote: > JIRA issue created. In case you want to track it: > > https://issues.jboss.org/browse/APIMAN-1210 > > -Eric > > On 7/25/2016 9:14 AM, Jairo Junior wrote: > > A client-side javascript app is performing the following request: > > > > /DELETE /apiman-gateway/org/service/1.1/resource/7 HTTP/1.1 > > Host: 172.17.0.1:8080 > > User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:47.0) > > Gecko/20100101 Firefox/47.0 > > Accept: application/json, text/plain, */* > > Accept-Language: en-US,en;q=0.5 > > Accept-Encoding: gzip, deflate > > Authorization: Bearer $ACCESS_TOKEN > > Referer: http://172.17.0.1:3000/ > > Origin: http://172.17.0.1:3000 > > Connection: keep-alive > > > > / > > But the gateway is performing the following request to the endpoint: > > > > /DELETE /service/rest/resource/7 HTTP/1.1 > > User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) > > Origin: http://172.17.0.1:3000 > > Accept-Language: en-US,en;q=0.5 > > Accept-Encoding: gzip, deflate > > Connection: keep-alive > > Authorization: Bearer $ACCESS_TOKEN > > Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, > > application/vnd.ms-excel, application/msword, > > application/vnd.ms-powerpoint, */* > > Referer: http://172.17.0.1:3000/ > > Host: 172.17.0.1:8280 > > Content-Type: application/x-www-form-//urlencoded > > Content-Length: 0 > > > > / > > Resulting in a 415 Unsupported Media Type at the endpoint. > > > > GET, POST and PUT requests are OK. > > > > Only using CORS Policy for this endpoint: > > > > /Access-Control-Allow-Origin: * > > Access-Control-Allow-Credentials: true > > Access-Control-Allow-Headers: accept, authrotization, content-type > > Access-Control-Allow-Methods: GET, POST, PUT, DELETE > > Access-Control-Max-Age: 3600/ > > > > > > _______________________________________________ > > 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/20160725/5c31d96d/attachment.html From eric.wittmann at redhat.com Tue Jul 26 08:53:34 2016 From: eric.wittmann at redhat.com (Eric Wittmann) Date: Tue, 26 Jul 2016 08:53:34 -0400 Subject: [Apiman-user] Content-type header included in gateway DELETE requests to endpoint In-Reply-To: References: <5c9c76cf-a037-0e22-d3a5-7de4080f6b33@redhat.com> Message-ID: Question: what is the consequence of this problem? It turns out that fixing this issue may require fairly extensive changes to how apiman proxies the request to the back end API. The http client[1] we are using for this is adding the content length and content type automatically for DELETE (as well as PUT and POST) if they are missing. It's doing this because it claims the HTTP spec is ambiguous on whether DELETE can have a body. So how high a priority is this? Is it causing a specific problem for you, or is it simply something you noticed? -Eric [1] http://square.github.io/okhttp/ On 7/25/2016 10:06 AM, Jairo Junior wrote: > Thanks again. > > On Mon, Jul 25, 2016 at 10:49 AM Eric Wittmann > wrote: > > JIRA issue created. In case you want to track it: > > https://issues.jboss.org/browse/APIMAN-1210 > > -Eric > > On 7/25/2016 9:14 AM, Jairo Junior wrote: > > A client-side javascript app is performing the following request: > > > > /DELETE /apiman-gateway/org/service/1.1/resource/7 HTTP/1.1 > > Host: 172.17.0.1:8080 > > > User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:47.0) > > Gecko/20100101 Firefox/47.0 > > Accept: application/json, text/plain, */* > > Accept-Language: en-US,en;q=0.5 > > Accept-Encoding: gzip, deflate > > Authorization: Bearer $ACCESS_TOKEN > > Referer: http://172.17.0.1:3000/ > > Origin: http://172.17.0.1:3000 > > Connection: keep-alive > > > > / > > But the gateway is performing the following request to the endpoint: > > > > /DELETE /service/rest/resource/7 HTTP/1.1 > > User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) > > Origin: http://172.17.0.1:3000 > > Accept-Language: en-US,en;q=0.5 > > Accept-Encoding: gzip, deflate > > Connection: keep-alive > > Authorization: Bearer $ACCESS_TOKEN > > Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, > > application/vnd.ms-excel, application/msword, > > application/vnd.ms-powerpoint, */* > > Referer: http://172.17.0.1:3000/ > > Host: 172.17.0.1:8280 > > > Content-Type: application/x-www-form-//urlencoded > > Content-Length: 0 > > > > / > > Resulting in a 415 Unsupported Media Type at the endpoint. > > > > GET, POST and PUT requests are OK. > > > > Only using CORS Policy for this endpoint: > > > > /Access-Control-Allow-Origin: * > > Access-Control-Allow-Credentials: true > > Access-Control-Allow-Headers: accept, authrotization, content-type > > Access-Control-Allow-Methods: GET, POST, PUT, DELETE > > Access-Control-Max-Age: 3600/ > > > > > > _______________________________________________ > > Apiman-user mailing list > > Apiman-user at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/apiman-user > > > From junior.jairo1 at gmail.com Tue Jul 26 09:30:31 2016 From: junior.jairo1 at gmail.com (Jairo Junior) Date: Tue, 26 Jul 2016 13:30:31 +0000 Subject: [Apiman-user] Content-type header included in gateway DELETE requests to endpoint In-Reply-To: References: <5c9c76cf-a037-0e22-d3a5-7de4080f6b33@redhat.com> Message-ID: It results in a "415 Unsupported Media Type" at the endpoint, since it wasn't designed to consume application/x-www-form-urlencoded. I have experience with some ESB's, and, in most cases, when you have a proxy that is "too smart" it may break your endpoint behavior. And when we are talking about REST APIs, where we are using HTTP as both a transport and application protocol, any apiman interference may break behavior. It's OK for new APIs, but it's very bad for legacy. IMHO, if the gateway is deliberately including headers, there won't be any guarantees that the endpoint will be prepared for this. There is a general discussion in Microservices community regarding Smart Pipe X Dumb Pipe that is very relevant to what we are discussing here. Also, I thinkg okhttp is the best alternative when you're developing a client, but is it good to proxy requests? Have you considered Apache HTTP Client + PoolingHttpClientConnectionManager. It has some nice features like "per route" connection pooling that will probably be killing for a Gateway. On Tue, Jul 26, 2016 at 9:53 AM Eric Wittmann wrote: > Question: what is the consequence of this problem? > > It turns out that fixing this issue may require fairly extensive changes > to how apiman proxies the request to the back end API. The > http client[1] we are using for this is adding the content length and > content type automatically for DELETE (as well as PUT and POST) if they > are missing. It's doing this because it claims the HTTP spec is > ambiguous on whether DELETE can have a body. > > So how high a priority is this? Is it causing a specific problem for > you, or is it simply something you noticed? > > -Eric > > [1] http://square.github.io/okhttp/ > > > On 7/25/2016 10:06 AM, Jairo Junior wrote: > > Thanks again. > > > > On Mon, Jul 25, 2016 at 10:49 AM Eric Wittmann > > wrote: > > > > JIRA issue created. In case you want to track it: > > > > https://issues.jboss.org/browse/APIMAN-1210 > > > > -Eric > > > > On 7/25/2016 9:14 AM, Jairo Junior wrote: > > > A client-side javascript app is performing the following request: > > > > > > /DELETE /apiman-gateway/org/service/1.1/resource/7 HTTP/1.1 > > > Host: 172.17.0.1:8080 > > > > > User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:47.0) > > > Gecko/20100101 Firefox/47.0 > > > Accept: application/json, text/plain, */* > > > Accept-Language: en-US,en;q=0.5 > > > Accept-Encoding: gzip, deflate > > > Authorization: Bearer $ACCESS_TOKEN > > > Referer: http://172.17.0.1:3000/ > > > Origin: http://172.17.0.1:3000 > > > Connection: keep-alive > > > > > > / > > > But the gateway is performing the following request to the > endpoint: > > > > > > /DELETE /service/rest/resource/7 HTTP/1.1 > > > User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) > > > Origin: http://172.17.0.1:3000 > > > Accept-Language: en-US,en;q=0.5 > > > Accept-Encoding: gzip, deflate > > > Connection: keep-alive > > > Authorization: Bearer $ACCESS_TOKEN > > > Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, > > > application/vnd.ms-excel, application/msword, > > > application/vnd.ms-powerpoint, */* > > > Referer: http://172.17.0.1:3000/ > > > Host: 172.17.0.1:8280 > > > > > Content-Type: application/x-www-form-//urlencoded > > > Content-Length: 0 > > > > > > / > > > Resulting in a 415 Unsupported Media Type at the endpoint. > > > > > > GET, POST and PUT requests are OK. > > > > > > Only using CORS Policy for this endpoint: > > > > > > /Access-Control-Allow-Origin: * > > > Access-Control-Allow-Credentials: true > > > Access-Control-Allow-Headers: accept, authrotization, content-type > > > Access-Control-Allow-Methods: GET, POST, PUT, DELETE > > > Access-Control-Max-Age: 3600/ > > > > > > > > > _______________________________________________ > > > 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/20160726/5a65317f/attachment-0001.html From eric.wittmann at redhat.com Tue Jul 26 09:49:35 2016 From: eric.wittmann at redhat.com (Eric Wittmann) Date: Tue, 26 Jul 2016 09:49:35 -0400 Subject: [Apiman-user] Content-type header included in gateway DELETE requests to endpoint In-Reply-To: References: <5c9c76cf-a037-0e22-d3a5-7de4080f6b33@redhat.com> Message-ID: <22492219-ae7a-d372-1644-3e9cbffbe75c@redhat.com> OK thanks for the info - very helpful. Regarding OK vs Apache - there is a design reason why OK is being used vs. Apache that is perhaps not that interesting to get into. It has to do with the way in which we stream the body of the request (and response). I agree with the assessment of smart vs. dumb proxies - the apiman gateway should definitely not be adding anything to the conversation that wasn't configured via one of the policies. I definitely consider this a bug, but I think it may require a fairly substantial rewrite of the http connector to fix it. :( I'm not against doing it, but I was hoping for a quick fix. -Eric On 7/26/2016 9:30 AM, Jairo Junior wrote: > It results in a "415 Unsupported Media Type" at the endpoint, since it > wasn't designed to consume application/x-www-form-urlencoded. > > I have experience with some ESB's, and, in most cases, when you have a > proxy that is "too smart" it may break your endpoint behavior. And when > we are talking about REST APIs, where we are using HTTP as both a > transport and application protocol, any apiman interference may break > behavior. It's OK for new APIs, but it's very bad for legacy. > > IMHO, if the gateway is deliberately including headers, there won't be > any guarantees that the endpoint will be prepared for this. There is a > general discussion in Microservices community regarding Smart Pipe X > Dumb Pipe that is very relevant to what we are discussing here. > > Also, I thinkg okhttp is the best alternative when you're developing a > client, but is it good to proxy requests? Have you considered Apache > HTTP Client + PoolingHttpClientConnectionManager. It has some nice > features like "per route" connection pooling that will probably be > killing for a Gateway. > > > > > On Tue, Jul 26, 2016 at 9:53 AM Eric Wittmann > wrote: > > Question: what is the consequence of this problem? > > It turns out that fixing this issue may require fairly extensive changes > to how apiman proxies the request to the back end API. The > http client[1] we are using for this is adding the content length and > content type automatically for DELETE (as well as PUT and POST) if they > are missing. It's doing this because it claims the HTTP spec is > ambiguous on whether DELETE can have a body. > > So how high a priority is this? Is it causing a specific problem for > you, or is it simply something you noticed? > > -Eric > > [1] http://square.github.io/okhttp/ > > > On 7/25/2016 10:06 AM, Jairo Junior wrote: > > Thanks again. > > > > On Mon, Jul 25, 2016 at 10:49 AM Eric Wittmann > > > >> wrote: > > > > JIRA issue created. In case you want to track it: > > > > https://issues.jboss.org/browse/APIMAN-1210 > > > > -Eric > > > > On 7/25/2016 9:14 AM, Jairo Junior wrote: > > > A client-side javascript app is performing the following > request: > > > > > > /DELETE /apiman-gateway/org/service/1.1/resource/7 HTTP/1.1 > > > Host: 172.17.0.1:8080 > > > > > > User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:47.0) > > > Gecko/20100101 Firefox/47.0 > > > Accept: application/json, text/plain, */* > > > Accept-Language: en-US,en;q=0.5 > > > Accept-Encoding: gzip, deflate > > > Authorization: Bearer $ACCESS_TOKEN > > > Referer: http://172.17.0.1:3000/ > > > Origin: http://172.17.0.1:3000 > > > Connection: keep-alive > > > > > > / > > > But the gateway is performing the following request to the > endpoint: > > > > > > /DELETE /service/rest/resource/7 HTTP/1.1 > > > User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT > 5.1; SV1) > > > Origin: http://172.17.0.1:3000 > > > Accept-Language: en-US,en;q=0.5 > > > Accept-Encoding: gzip, deflate > > > Connection: keep-alive > > > Authorization: Bearer $ACCESS_TOKEN > > > Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, > > > application/vnd.ms-excel, application/msword, > > > application/vnd.ms-powerpoint, */* > > > Referer: http://172.17.0.1:3000/ > > > Host: 172.17.0.1:8280 > > > > > > Content-Type: application/x-www-form-//urlencoded > > > Content-Length: 0 > > > > > > / > > > Resulting in a 415 Unsupported Media Type at the endpoint. > > > > > > GET, POST and PUT requests are OK. > > > > > > Only using CORS Policy for this endpoint: > > > > > > /Access-Control-Allow-Origin: * > > > Access-Control-Allow-Credentials: true > > > Access-Control-Allow-Headers: accept, authrotization, > content-type > > > Access-Control-Allow-Methods: GET, POST, PUT, DELETE > > > Access-Control-Max-Age: 3600/ > > > > > > > > > _______________________________________________ > > > Apiman-user mailing list > > > Apiman-user at lists.jboss.org > > > > > > https://lists.jboss.org/mailman/listinfo/apiman-user > > > > > > From junior.jairo1 at gmail.com Tue Jul 26 17:53:07 2016 From: junior.jairo1 at gmail.com (Jairo Junior) Date: Tue, 26 Jul 2016 21:53:07 +0000 Subject: [Apiman-user] Content-type header included in gateway DELETE requests to endpoint In-Reply-To: <22492219-ae7a-d372-1644-3e9cbffbe75c@redhat.com> References: <5c9c76cf-a037-0e22-d3a5-7de4080f6b33@redhat.com> <22492219-ae7a-d372-1644-3e9cbffbe75c@redhat.com> Message-ID: I see. I was introduced to apiman's codebase last week, so, it's just a rookie's opinion here. Glad I could help and thanks for the fast feedbacks. =) On Tue, Jul 26, 2016 at 10:49 AM Eric Wittmann wrote: > OK thanks for the info - very helpful. > > Regarding OK vs Apache - there is a design reason why OK is being used > vs. Apache that is perhaps not that interesting to get into. It has to > do with the way in which we stream the body of the request (and response). > > I agree with the assessment of smart vs. dumb proxies - the apiman > gateway should definitely not be adding anything to the conversation > that wasn't configured via one of the policies. I definitely consider > this a bug, but I think it may require a fairly substantial rewrite of > the http connector to fix it. :( I'm not against doing it, but I was > hoping for a quick fix. > > -Eric > > > On 7/26/2016 9:30 AM, Jairo Junior wrote: > > It results in a "415 Unsupported Media Type" at the endpoint, since it > > wasn't designed to consume application/x-www-form-urlencoded. > > > > I have experience with some ESB's, and, in most cases, when you have a > > proxy that is "too smart" it may break your endpoint behavior. And when > > we are talking about REST APIs, where we are using HTTP as both a > > transport and application protocol, any apiman interference may break > > behavior. It's OK for new APIs, but it's very bad for legacy. > > > > IMHO, if the gateway is deliberately including headers, there won't be > > any guarantees that the endpoint will be prepared for this. There is a > > general discussion in Microservices community regarding Smart Pipe X > > Dumb Pipe that is very relevant to what we are discussing here. > > > > Also, I thinkg okhttp is the best alternative when you're developing a > > client, but is it good to proxy requests? Have you considered Apache > > HTTP Client + PoolingHttpClientConnectionManager. It has some nice > > features like "per route" connection pooling that will probably be > > killing for a Gateway. > > > > > > > > > > On Tue, Jul 26, 2016 at 9:53 AM Eric Wittmann > > wrote: > > > > Question: what is the consequence of this problem? > > > > It turns out that fixing this issue may require fairly extensive > changes > > to how apiman proxies the request to the back end API. The > > http client[1] we are using for this is adding the content length and > > content type automatically for DELETE (as well as PUT and POST) if > they > > are missing. It's doing this because it claims the HTTP spec is > > ambiguous on whether DELETE can have a body. > > > > So how high a priority is this? Is it causing a specific problem for > > you, or is it simply something you noticed? > > > > -Eric > > > > [1] http://square.github.io/okhttp/ > > > > > > On 7/25/2016 10:06 AM, Jairo Junior wrote: > > > Thanks again. > > > > > > On Mon, Jul 25, 2016 at 10:49 AM Eric Wittmann > > > > > > >> wrote: > > > > > > JIRA issue created. In case you want to track it: > > > > > > https://issues.jboss.org/browse/APIMAN-1210 > > > > > > -Eric > > > > > > On 7/25/2016 9:14 AM, Jairo Junior wrote: > > > > A client-side javascript app is performing the following > > request: > > > > > > > > /DELETE /apiman-gateway/org/service/1.1/resource/7 HTTP/1.1 > > > > Host: 172.17.0.1:8080 > > > > > > > > > User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:47.0) > > > > Gecko/20100101 Firefox/47.0 > > > > Accept: application/json, text/plain, */* > > > > Accept-Language: en-US,en;q=0.5 > > > > Accept-Encoding: gzip, deflate > > > > Authorization: Bearer $ACCESS_TOKEN > > > > Referer: http://172.17.0.1:3000/ > > > > Origin: http://172.17.0.1:3000 > > > > Connection: keep-alive > > > > > > > > / > > > > But the gateway is performing the following request to the > > endpoint: > > > > > > > > /DELETE /service/rest/resource/7 HTTP/1.1 > > > > User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT > > 5.1; SV1) > > > > Origin: http://172.17.0.1:3000 > > > > Accept-Language: en-US,en;q=0.5 > > > > Accept-Encoding: gzip, deflate > > > > Connection: keep-alive > > > > Authorization: Bearer $ACCESS_TOKEN > > > > Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, > > > > application/vnd.ms-excel, application/msword, > > > > application/vnd.ms-powerpoint, */* > > > > Referer: http://172.17.0.1:3000/ > > > > Host: 172.17.0.1:8280 > > > > > > > > > Content-Type: application/x-www-form-//urlencoded > > > > Content-Length: 0 > > > > > > > > / > > > > Resulting in a 415 Unsupported Media Type at the endpoint. > > > > > > > > GET, POST and PUT requests are OK. > > > > > > > > Only using CORS Policy for this endpoint: > > > > > > > > /Access-Control-Allow-Origin: * > > > > Access-Control-Allow-Credentials: true > > > > Access-Control-Allow-Headers: accept, authrotization, > > content-type > > > > Access-Control-Allow-Methods: GET, POST, PUT, DELETE > > > > Access-Control-Max-Age: 3600/ > > > > > > > > > > > > _______________________________________________ > > > > 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/20160726/eba193d3/attachment.html