Question
Virtusa
US
Last activity: 25 Oct 2016 8:10 EDT
REST Integration is failing after Generate Records
Create Rest Integration wizard is failing after Generate Records step
Error " Generation process has been cancelled and all created records have been removed"
Pegasystems Inc.
US
Hi Khareem,
Thanks for sending me the log snippet. Would it be possible to attach the log here because the i do not see the caused by?
Hi Khareem,
Thanks for sending me the log snippet. Would it be possible to attach the log here because the i do not see the caused by?
2016-06-06 12:16:28,811 [.PRPCWorkManager : 1] [ STANDARD] [ ] [ectDevUtils:01.01.01] ( internal.util.PRServiceUtils) ERROR kshai11 - Rule Generator thrown exception:
com.pega.pegarules.pub.PRRuntimeException: Definition required to conform to AEXP-FW-Ent-Int-REST-GS-LylOffrV1-OLETSvc-.request instance created 20160224T111059.623 GMT.
.pyPageClass: The Page Class value AEXP-FW-Ent-Int-REST-GS-LylOffrV1-OLETSvc-Inqnn828831595 has been changed to AEXP-FW-Ent-Int-REST-GS-LylOffrV1-OLETSvc-Request
at com.pega.pegarules.integration.config.internal.mapping.RuleGeneratorCommon.createOneProperty(RuleGeneratorCommon.java:3180)
at com.pega.pegarules.integration.config.internal.mapping.RuleGeneratorCommon.createPropertyRules(RuleGeneratorCommon.java:3054)
at com.pega.pegarules.integration.config.internal.mapping.RuleGeneratorREST.generateAndSaveRuleInstances(RuleGeneratorREST.java:891)
at com.pega.pegarules.integration.config.internal.mapping.RuleGeneratorREST.generateRules(RuleGeneratorREST.java:163)
at com.pega.pegarules.integration.engine.internal.util.PRServiceUtils.generateRulesFromMetadata(PRServiceUtils.java:1678)
at com.pega.pegarules.integration.engine.internal.util.PRServiceUtils.generateRulesFromMetadata(PRServiceUtils.java:1706)
at com.pegarules.generated.activity.ra_action_pygeneraterulesfrommetadataasync_90350a212c6cdc08be679680c2693d97.step1_circum0(ra_action_pygeneraterulesfrommetadataasync_90350a212c6cdc08be679680c2693d97.java:160)
at com.pegarules.generated.activity.ra_action_pygeneraterulesfrommetadataasync_90350a212c6cdc08be679680c2693d97.perform(ra_action_pygeneraterulesfrommetadataasync_90350a212c6cdc08be679680c2693d97.java:69)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(ThreadRunner.java:641)
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivities(ThreadRunner.java:568)
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivities(PRThreadImpl.java:427)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.executeBatchTask(QueueProcessor.java:256)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:319)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:913)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1177)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:926)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:825)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:646)
at com.pega.pegarules.session.internal.async.Agent.runBatchTask(Agent.java:816)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.AsyncServant.processAsyncTask(AsyncServant.java:229)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.AsyncServant.invoke(AsyncServant.java:166)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:315)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:263)
at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.invokeEngine(EngineBean.java:225)
at sun.reflect.GeneratedMethodAccessor68.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:338)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:379)
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:216)
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingException(AppServerBridgeToPega.java:238)
at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.invokeEngine(EngineBeanBoot.java:168)
at com.pega.pegarules.internal.etier.interfaces.EJSLocalStatelessEngineBMT_f2439d86.invokeEngine(Unknown Source)
at com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRAsync.processRequest(PRAsync.java:155)
at com.pega.pegarules.session.internal.engineinterface.etier.asynchbeans.AsyncTask.run(AsyncTask.java:64)
at com.pega.pegarules.session.internal.engineinterface.etier.asynchbeans.RunnableWrapper.run(RunnableWrapper.java:71)
at com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java:270)
at java.security.AccessController.doPrivileged(AccessController.java:359)
at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:770)
at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithExecutionContextImpl.java:222)
at com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java:159)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1662)
=-waikei
Pegasystems Inc.
US
Khareem,
Thanks for the update. I think this would require further investigation and i would recommend creating a SR.
=waikei
Pegasystems Inc.
US
Hi Khareem,
As per the information provided in your SR, it is related to “415 – Unsupported Media Type”.
This error is being thrown if there is an issue with Content-type at client/server side of the REST service and some of the scenarios are explained in this article, http://stackoverflow.com/questions/24932080/rest-webservice-returning-415-unsupported-media-type
This error related information probably you can find in the fiddler tracer if the REST service call is being made.
Hope this might be helpful to you guys in finding the root cause of your issue.
Regards,
Mahesh
Unitedhealth Group, Inc.
US
Help! I'm getting the same thing, I think.
Is the issue (for me) just that if I don't have authentication set up, the request fails (w/ an HTML result)?
But I don't want Pega to actually be making the call [at Wizard generation time], but not until I can configure the actual call...
Unitedhealth Group, Inc.
US
I'll see if I can get the logs, Paul, I don't have direct access.
This is what I think I figured out: I knew the call wouldn't work as I initially specified (I didn't *want* it to actually try, until I could configure extra headers to send - security/auditing related); so when it did try, it failed and sent back HTML err page (vs. JSON response -- don't ask me, I'm just the reporter).
When the actual call did fail (I think), the Wizard threw the exception as above, and [NPE] rolled back any created rules and terminated.
I'm not exactly sure what I did to belay that, but I succeeded in getting thru the wizard w/o an actual call to the service, then I added my custom headers and tested and succeeded and moved on.
(If I can grab the logs, I will, and add the same here; if not, know that I have now accomplished what I want, but my complaints are two-fold:
* the wizard wants to try and make the call irrespective of whether or not it should; why specify test req. data and response data (since I know the actual call will not work) if that isn't going to be used to generate the rules I need?
I'll see if I can get the logs, Paul, I don't have direct access.
This is what I think I figured out: I knew the call wouldn't work as I initially specified (I didn't *want* it to actually try, until I could configure extra headers to send - security/auditing related); so when it did try, it failed and sent back HTML err page (vs. JSON response -- don't ask me, I'm just the reporter).
When the actual call did fail (I think), the Wizard threw the exception as above, and [NPE] rolled back any created rules and terminated.
I'm not exactly sure what I did to belay that, but I succeeded in getting thru the wizard w/o an actual call to the service, then I added my custom headers and tested and succeeded and moved on.
(If I can grab the logs, I will, and add the same here; if not, know that I have now accomplished what I want, but my complaints are two-fold:
* the wizard wants to try and make the call irrespective of whether or not it should; why specify test req. data and response data (since I know the actual call will not work) if that isn't going to be used to generate the rules I need?
* also, I encountered this: if the wizard can't itself modify the application rule [at least, that's how it appears], then it won't run, even if I've already added a new RSV to the app rule, and configured this (since the rule in question is *locked*, and shouldn't be modified...); what seems to happen is the "Create" button on the final screen is simply disabled in that case -- at least, that's how it seems; so I had to run the wizard in a separate application rule and move the rules/ruleset versions manually after the fact.
Bank Sinarmas
ID
hi all
i trying to Create Rest Integration n get Error "Generation process has been cancelled and all created records have been removed"
when change the response json key its work.
Before JSON Response key is "description", when i change to "descript" or etc its work
then i test with create a property with identifier description n get error.
my assumption maybe u're json response cannot create become a property.