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

 Harindra Morya (moryh)
PEGA
Principal Software Engineer, 1:1 Integrations
Pegasystems Inc.
IN
moryh Member since 2017 7 posts
PEGA
Posted: Jul 25, 2018
Last activity: Aug 22, 2018
Posted: 25 Jul 2018 14:11 EDT
Last activity: 22 Aug 2018 7:02 EDT
Closed
Solved

Resource not found error with REST service

I created a REST service with service package name "TGBHRAppsWorkOnboarding ", service version as "1" and URI Template as "MyRest/{id}". EndPoint URL generated for this service is "http://localhost:8080/prweb/PRRestService/TGBHRAppsWorkOnboarding/1/MyRest/{id}" Screenshot of rule form has been attached.

Then on Method tab i configured Get method to call activity "MyRestActivity", which has logic to fetch the case details on the basis of id received in request. And in the response tab of GET method i used XML stream rule.

When i unit tested this rest service it worked correctly.

I also tried to access above URL directly in browser and it worked correctl

Then i created a REST Connector to access the above REST service. I specified resource url as "http://localhost:8080/prweb/PRRestService/TGBHRAppsWorkOnboarding/1/MyRest/{Id}". And then click on the Test Connectivity and got HTTP status code 200 which is for success.

Then i called this connector using activity and unit tested but getting below :

Show More

I created a REST service with service package name "TGBHRAppsWorkOnboarding ", service version as "1" and URI Template as "MyRest/{id}". EndPoint URL generated for this service is "http://localhost:8080/prweb/PRRestService/TGBHRAppsWorkOnboarding/1/MyRest/{id}" Screenshot of rule form has been attached.

Then on Method tab i configured Get method to call activity "MyRestActivity", which has logic to fetch the case details on the basis of id received in request. And in the response tab of GET method i used XML stream rule.

When i unit tested this rest service it worked correctly.

I also tried to access above URL directly in browser and it worked correctl

Then i created a REST Connector to access the above REST service. I specified resource url as "http://localhost:8080/prweb/PRRestService/TGBHRAppsWorkOnboarding/1/MyRest/{Id}". And then click on the Test Connectivity and got HTTP status code 200 which is for success.

Then i called this connector using activity and unit tested but getting below :

pyStatusMessage the server responded with an HTTP 404 code, indicating that the resource does not exist.
pyHTTPResponseCode 404
pyStatusValue

Fail: The server indicated that there is no resource at the endpoint.

Then i changed logging level to debug and observed following error logs:

2018-07-25 23:26:38,323 [http-nio-8080-exec-7] [  STANDARD] [                    ] [                    ] (     services.http.HTTPService) ERROR Harinder| Proprietary information hidden  - Resource not found 
com.pega.pegarules.pub.PRException: Couldn't find Rule-Service-Rest instance for the following uri:/TGBHRAppsWorkOnboarding/1/MyRest 
	at com.pega.pegarules.integration.engine.internal.services.http.HTTPService.invoke(HTTPService.java:308) ~[printegrint.jar:?] 
	at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:331) ~[prprivate.jar:?] 
	at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:274) ~[prprivate.jar:?] 
	at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:251) ~[prprivate.jar:?] 
	at com.pega.pegarules.priv.context.JNDIEnvironment.invokeEngineInner(JNDIEnvironment.java:278) ~[prpublic.jar:?] 
	at com.pega.pegarules.priv.context.JNDIEnvironment.invokeEngine(JNDIEnvironment.java:223) ~[prpublic.jar:?] 
	at com.pega.pegarules.web.impl.WebStandardImpl.makeEtierRequest(WebStandardImpl.java:678) ~[prwebj2ee.jar:?] 
	at com.pega.pegarules.web.impl.WebStandardImpl.doPost(WebStandardImpl.java:394) ~[prwebj2ee.jar:?] 
	at sun.reflect.GeneratedMethodAccessor88.invoke(Unknown Source) ~[?:?] 
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_121] 
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_121] 
	at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:370) ~[prbootstrap-7.3.1-218.jar:7.3.1-218] 
	at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:411) ~[prbootstrap-7.3.1-218.jar:7.3.1-218] 
	at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:224) ~[prbootstrap-api-7.3.1-218.jar:7.3.1-218] 
	at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:273) ~[prbootstrap-api-7.3.1-218.jar:7.3.1-218] 
	at com.pega.pegarules.internal.web.servlet.WebStandardBoot.doPost(WebStandardBoot.java:129) ~[prbootstrap-api-7.3.1-218.jar:7.3.1-218] 
	at com.pega.pegarules.internal.web.servlet.WebStandardBoot.doGet(WebStandardBoot.java:100) ~[prbootstrap-api-7.3.1-218.jar:7.3.1-218] 
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:635) ~[servlet-api.jar:?] 
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) ~[servlet-api.jar:?] 
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) ~[catalina.jar:8.5.14] 
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[catalina.jar:8.5.14] 
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) ~[tomcat-websocket.jar:8.5.14] 
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[catalina.jar:8.5.14] 
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[catalina.jar:8.5.14] 
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198) ~[catalina.jar:8.5.14] 
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) ~[catalina.jar:8.5.14] 
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:478) ~[catalina.jar:8.5.14] 
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140) ~[catalina.jar:8.5.14] 
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:80) ~[catalina.jar:8.5.14] 
	at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:624) ~[catalina.jar:8.5.14] 
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87) ~[catalina.jar:8.5.14] 
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342) ~[catalina.jar:8.5.14] 
	at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:799) ~[tomcat-coyote.jar:8.5.14] 
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) ~[tomcat-coyote.jar:8.5.14] 
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:861) ~[tomcat-coyote.jar:8.5.14] 
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1455) ~[tomcat-coyote.jar:8.5.14] 
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) ~[tomcat-coyote.jar:8.5.14] 
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_121] 
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_121] 
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) ~[tomcat-util.jar:8.5.14] 
	at java.lang.Thread.run(Thread.java:745) [?:1.8.0_121]

I am not able to understand why resource not found error is being thrown because when i am trying to access that service URL directly its working fine.

Please help to resolve this.

Thanks in Advance.


Show Less
To see attachments, please log in.
Low-Code App Development

Accepted Solution

Posted: 6 years ago
Posted: 27 Jul 2018 2:04 EDT
Joel McLeish (JoelMcLeish)
PEGA
Senior Director, Service Assurance
Pegasystems Inc.
AU

Why an activity rather than data page?

In any case, this line "/TGBHRAppsWorkOnboarding/1/MyRest&nbsp" suggests you have not set the .id of the .request page, it shows an empty character rather than the url parameter.

To see attachments, please log in.
Posted: 6 years ago
Posted: 25 Jul 2018 14:38 EDT
Naresh Anchuri (Naresh Anchuri)
Coforge DPA
Solutions Architect
Coforge DPA
IN

Hi Harindra,

Have you build the service and connector on the same pega application instance or its different instance, if they are different instance and different server then we need to mention the ip address instead of localhost.

To see attachments, please log in.
  • Sari Abdel-Latif Georges Haytove Sudipta Biswas Guojun Tao Scott Foster and 1 More

Accepted Solution

Posted: 6 years ago
Posted: 27 Jul 2018 2:04 EDT
Joel McLeish (JoelMcLeish)
PEGA
Senior Director, Service Assurance
Pegasystems Inc.
AU

Why an activity rather than data page?

In any case, this line "/TGBHRAppsWorkOnboarding/1/MyRest&nbsp" suggests you have not set the .id of the .request page, it shows an empty character rather than the url parameter.

To see attachments, please log in.
Posted: 6 years ago
Posted: 27 Jul 2018 12:51 EDT
Harindra Morya (moryh)
PEGA
Principal Software Engineer, 1:1 Integrations
Pegasystems Inc.
IN

Hi Joel

Yes i missed the step page on Connect-REST step. That step page was holding the id value. So after providing the step page i am able to access the service data corresponding to id.

Thanks for your response.

To see attachments, please log in.
Posted: 6 years ago
Posted: 21 Aug 2018 10:55 EDT
Hanga Gelencser (Hanga Gelencser)
Greenfield Technology AG
Hanga Gelencser
Greenfield Technology AG
IT

Hi,

I'm facing with the following issue:

I have a Service REST rule, where I configured the URI template ( /customer/{customerID} ), I test my service with postman, and I wanted to set custom status code, when there is no path variable given, but postman gaves me 404 status code. In Pega 7.3.0 it is working, but in 7.4 I can't reach my service from outside.

Any idea, what should be the problem?

Thanks in advance

To see attachments, please log in.
Posted: 6 years ago
Posted: 20 Aug 2018 1:25 EDT
Nikhil Bhandari (NIKUBHAN)
Ai4Process
Pega Principal Consultant
Ai4Process
GB

I am also facing a similar error. MY REST services were working fine in 7.1.8. After porting to 7.3.1 it is giving resource not found when we pass path variables as blank (which is a valid scenario since we are supporting multiple operations in the same service not all of which require the path variable). I even tried recreating the Service REST rule in 7.3.1 but still facing the same issue

To see attachments, please log in.
Posted: 6 years ago
Posted: 22 Aug 2018 7:02 EDT
Raju Botu (Raju Botu)
Aaseya IT Solutions
AVP
Aaseya IT Solutions
IN

Same issue here, before exploring further i wanted to know if any of you had found a resolution. 

Please update this thread.

To see attachments, please log in.

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