ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Unable to identify the error in consuming the rest service

Post new topic  Reply to topic
 Unable to identify the error in consuming the rest service « View previous topic :: View next topic » 
Author Message
ajaykumar.maram
PostPosted: Thu Apr 27, 2017 5:05 am    Post subject: Unable to identify the error in consuming the rest service Reply with quote

Novice

Joined: 10 Jul 2015
Posts: 20

Hi All,

I'm trying to consume an third party REST service in IIB using http request node. My flow is like "HttpInput - Http Request - Http Replay" nodes.
When I'm doing this I'm facing a time out exception. The service I'm consuming is as follows:

https://api.uber.com/v1/estimates/price?start_latitude=17.4460062&start_longitude=78.38374209999999&end_latitude=17.4507085&end_longitude=78.3762057

Can any one tell me what was the issue since I'm not finding any error in logs even.
Below are the things I did as of now:
1. Since it an HTTPS service I've added the certificate to my trust store to avoid handshake exceptions.
2. I've increased time limit to avoid time out.

Please provide some suggestions to overcome the issue.Thanks in advance.
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Apr 28, 2017 4:29 am    Post subject: Re: Unable to identify the error in consuming the rest servi Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

ajaykumar.maram wrote:
Can any one tell me what was the issue since I'm not finding any error in logs even.


If you're getting a timeout error and you've (inexplicably) got no actual user code in your flow then the obvious conclusion is that the Uber API isn't responding.

Which explains why there are no errors in your logs.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
ajaykumar.maram
PostPosted: Fri Apr 28, 2017 4:40 am    Post subject: Reply with quote

Novice

Joined: 10 Jul 2015
Posts: 20

Quote:
If you're getting a timeout error and you've (inexplicably) got no actual user code in your flow then the obvious conclusion is that the Uber API isn't responding.


Thanks for the response vitor. The API is working fine. I've tested that API using postman and soapUI.
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Apr 28, 2017 5:37 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

ajaykumar.maram wrote:
Quote:
If you're getting a timeout error and you've (inexplicably) got no actual user code in your flow then the obvious conclusion is that the Uber API isn't responding.


Thanks for the response vitor. The API is working fine. I've tested that API using postman and soapUI.


Then you're down to running a user trace and seeing where it stalls.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
ajaykumar.maram
PostPosted: Sat Apr 29, 2017 3:55 am    Post subject: Reply with quote

Novice

Joined: 10 Jul 2015
Posts: 20

Quote:
Then you're down to running a user trace and seeing where it stalls


The Request is not going out from HTTP Request Node.
Another thing is that till now I'm using IIB 10.0v and now I updated the version with fix-8. In this I'm using Rest Request and able to get the response using the same API.

Still I want to know what is the mistake I'm doing in IIB 10.0v
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sat Apr 29, 2017 4:31 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

ajaykumar.maram wrote:
Quote:
Then you're down to running a user trace and seeing where it stalls


The Request is not going out from HTTP Request Node.
Another thing is that till now I'm using IIB 10.0v and now I updated the version with fix-8. In this I'm using Rest Request and able to get the response using the same API.

Still I want to know what is the mistake I'm doing in IIB 10.0v

Possibly none. Could be a product defect that got fixed since...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Unable to identify the error in consuming the rest service
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.