Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Direesh Aunugu (DireeshA)
Anthem

Anthem
US
DireeshA Member since 2015 5 posts
Anthem
Posted: Sep 25, 2017
Last activity: Oct 16, 2018
Posted: 25 Sep 2017 17:05 EDT
Last activity: 16 Oct 2018 12:03 EDT
Closed

NoHttpResponseException & Unexpected HTTP 403 Response code
Facing below issues, I have been trying to install package in multiple instances. Server - A has been configured on PEGA instance - 7.2.2 where as Client (B & C) has been configured on instance 7.1.n versions of pega.
1) Server - A & Client B are configured and while defining release (as part of Step- configure Applications Environment & Release Details (on Release Management Server)) facing below issue:
** Unable to check platform REST service due to com.pega.pegarules.pub.services.ConnectorException: Caught unhandled exception: java.lang.RuntimeException: org.apache.http.NoHttpResponseException: nn.nnn.nnn.nnnn:8307 failed to respond
2) Server - A & Client c are configured, facing below issue while doing test connection from Server to Client:
“Instance Connection Info :Fail: Unexpected HTTP 403 Response code the HTTP response code of 403 indicated a client error. The response data may contain a reason.”
Any help will be appreciated.


**Moderation Team has archived post**


This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

To see attachments, please log in.
Updates

Posted: 7 years ago
Posted: 26 Sep 2017 5:40 EDT
Chinmaya Hegde (ChinmayaHegde)
PEGA
Senior Principal Cloud Development Engineer
Pegasystems Inc.
IN

Hi DireeshA,

Regarding First Exception:

It might be the issue with server due to heavy load. Please retry to get the release created.

Regarding Second Exception:

Please ignore this exception. This is known issue we are working on it. You can continue with next process.

 

To see attachments, please log in.
Posted: 7 years ago
Posted: 26 Sep 2017 11:21 EDT
Direesh Aunugu (DireeshA)
Anthem

Anthem
US

Hi Chinmaya, thanks for the response. On the second exception, can you please share more details on what the issue is related to ? It does not let me proceed further. I'm not sure what do you mean by continue with next process  as it is not letting me create Application instance in server.

Is it related to underlying protocol by any chance? In this case Client is on https and when i mention https as protocol in environment section, i'm getting below error:

When https protocol is used(which is correct one):

Error: IteratePage_PegaRMF_Work_ManageEnvironments_20170926T144658_698_GMT1 1.(PegaRMF-Work-ManageEnvironments)Unable to check platform REST service due to the HTTP response code of 500 indicated a server error. The response data may contain a reason. // The body of the service's response, which is set up for mapping in the Connector rule, was empty for this service call.

When http protocol is used (which is not correct):

Error: •** Unable to check platform REST service due to com.pega.pegarules.pub.services.ConnectorException: Caught unhandled exception: java.lang.RuntimeException: org.apache.http.NoHttpResponseException: Proprietary information hidden:8307 failed to respond

I will try Exception -1 now.

 

To see attachments, please log in.
Posted: 7 years ago
Posted: 26 Sep 2017 11:56 EDT
Direesh Aunugu (DireeshA)
Anthem

Anthem
US

ChinmayaNH, I have tried Configuring Server again, This time even Exception -1 is throwing below error:

  • ** Unable to check platform REST service due to the HTTP response code of 500 indicated a server error. The response data may contain a reason. // The body of the service's response, which is set up for mapping in the Connector rule, was empty for this service call.
To see attachments, please log in.
Posted: 6 years ago
Posted: 10 Apr 2018 10:33 EDT
Marissa Rogers (MarissaRogers)
MOD
Principal Knowledge Management Specialist
Pegasystems Inc.
US
Hello!
 
Thank you for posting your query on PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s available on the top right pane of this page.
Show More
Hello!
 
Thank you for posting your query on PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s available on the top right pane of this page. Once created, please reply back here with the URL of the new post.
 
We have also sent you a private message opening up a communication channel in case you have any further questions.
 
Thanks,

Show Less
To see attachments, please log in.

Related content:

Question

Orchestrator to Development: Fail: Unexpected HTTP 403 Response code

Question

Fail: Unexpected HTTP 500 Response code -Hotelproxy Case creation

Question

Fail: Unexpected HTTP 405 Response code in 7.3.1 (Connect Rest Patch Method )

Question

Deployment Manager - Orchestrator to development FAILED Fail: Unexpected HTTP 500 Response code

Question

Mashup Loading Issue with 403 HTTP status code

Question Solved

Issue with NewCovered Harness resulting in 403 Fordbidden http response

Question Solved

Getting Fail: Unexpected HTTP 500 Response code using the REST connector and setting values on pyRequestAttachmentPage

Question

201 HTTP response code fail to interpret by Pega

Question

http response code for unsupported method in Service-REST

Question

Unable to check platform REST service due to the HTTP response code of 500 indicated a server error.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice