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 » HTTP Request node returns 503 when service is running

Post new topic  Reply to topic
 HTTP Request node returns 503 when service is running « View previous topic :: View next topic » 
Author Message
deecee
PostPosted: Fri Aug 26, 2016 4:48 am    Post subject: HTTP Request node returns 503 when service is running Reply with quote

Acolyte

Joined: 11 Sep 2014
Posts: 51

Hello,
I am working on IIB 10.0.0.1
I am invoking an external web service using HTTPS.
All the certificates are in place.

When I directly invoke the external web service using SOAPUI, it returns me a result but when I invoke it from IIB, it returns service unavailable 503.

Any ideas of any configurations I am missing?
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sat Aug 27, 2016 4:52 am    Post subject: Reply with quote

Grand High Poobah

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

You need to take a user trace. This will tell you what the error may be in more details. Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
deecee
PostPosted: Mon Aug 29, 2016 12:02 am    Post subject: Reply with quote

Acolyte

Joined: 11 Sep 2014
Posts: 51

This is what I get from user trace too.

The broker has received data via HTTP from a remote server at host 'xxxx' with an HTTP status code of 503.
Back to top
View user's profile Send private message
adubya
PostPosted: Mon Aug 29, 2016 1:01 am    Post subject: Reply with quote

Partisan

Joined: 25 Aug 2011
Posts: 377
Location: GU12, UK

Check the error logs of the remote service to see why it's returning 503 ?
_________________
Independent Middleware Consultant
andy@knownentity.com
Back to top
View user's profile Send private message Send e-mail
vishBroker
PostPosted: Mon Aug 29, 2016 5:59 am    Post subject: Reply with quote

Centurion

Joined: 08 Dec 2010
Posts: 135

HTTP 503 is temporary state.
If you are able to hit it from SOAP UI but not from IIB then
1. you need to check the connectivity betweeen IIB and target server.
2. Make sure, the URL that IIB uses to hit backend is exactly the same.
3. Check the HTTP headers that are being sent from IIB.

If that does not give you any pointers - then you may want to do packet capture between IIB and backend system.
Back to top
View user's profile Send private message
deecee
PostPosted: Wed Aug 31, 2016 2:52 am    Post subject: Reply with quote

Acolyte

Joined: 11 Sep 2014
Posts: 51

Hi VishBroker,

How do I check connectivity between IIB and backend server?
And how do I check packet capture between the two systems?
Back to top
View user's profile Send private message
vishBroker
PostPosted: Wed Aug 31, 2016 8:18 am    Post subject: Reply with quote

Centurion

Joined: 08 Dec 2010
Posts: 135

deecee wrote:
Hi VishBroker,

How do I check connectivity between IIB and backend server?
And how do I check packet capture between the two systems?


The system that has broker - should be able to ping the target server.
This tells you the connectivity between IIB and backend server.

For packet capture - there are few network sniffing tools. Your network team should be able to capture it.

Have you tried to look at the HTTP headers that are being sent?

By the way -
As you are getting 503 - it seems that you are able to hit the backend

YOu need to check at the backend - what error you are getting.
+++
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.

Note: The existence of the 503 status code does not imply that a
server must use it when becoming overloaded. Some servers may wish
to simply refuse the connection.

+++
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » HTTP Request node returns 503 when service is running
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.