Question
Novitates Technology Solutions PVT LTD
IN
Last activity: 24 Jun 2024 10:16 EDT
Service Rest Integration Connectivity Issue
We are facing an issue when attempting all service rest api even Pega OOTB API to fetch case information using the Pega OOTB cases service REST endpoint in Pega version 7.2. Instead of receiving the expected response, we are consistently receiving a 500 Internal Server Error.
Analysis:
1.Pega service rule/ Service package is not getting picked while sending the request to pega.
2.There is no specific error found in tracer as well as in logs.
3.validated web.xml file as well and didn't find any constraints configuration which is blocking/ restricting any external request while executing the service.
4.validated pega server logs and found few entries for the services execution which has return code 500.
Accepted Solution
Updated: 24 Jun 2024 10:16 EDT
Eclatprime Digital Private Limited
SG
all 500 errors are app server related i hope some where the traffic is failing to reach the target.
can you once check if there are any firewalls that are blocking the response or request reaching to the target.
Also you said about rule being not picked can you try revalidate and save or i suggest sometimes a clear cache restart will solve this problems
clear the app cache clear the db cache do a clean resart of node and then try to run the api
i strongly fee there is some firewall that is blocking and causing this issue
Eclatprime Digital Private Limited
IN
@KumarMalakala It happens sometime while accessing this API . Once try doing few changes which i can tell but before that can u please inform which method u r accessing here if its GET then. 1. Check the security authentication behind the scene on service REST which you are using and how pega used it.
2. 500 error is Pure internal network error which means there is some n/w loss in between the service request and response.
3. If you are observing service package is not getting picked check the Ruleset in which the service and service package add same that to application definition also.
Accepted Solution
Updated: 24 Jun 2024 10:16 EDT
Eclatprime Digital Private Limited
SG
all 500 errors are app server related i hope some where the traffic is failing to reach the target.
can you once check if there are any firewalls that are blocking the response or request reaching to the target.
Also you said about rule being not picked can you try revalidate and save or i suggest sometimes a clear cache restart will solve this problems
clear the app cache clear the db cache do a clean resart of node and then try to run the api
i strongly fee there is some firewall that is blocking and causing this issue