My Oracle Support Banner

After chaning the OPSS DB on the jps-config.xml the token decryption failed. (Doc ID 2833223.1)

Last updated on MAY 15, 2023

Applies to:

Oracle Business Process Management Suite - Version 12.2.1.4.0 and later
Information in this document applies to any platform.

Symptoms

The customer re-created the OPSS DB using RCU and pointed the jps-config.xml to the new OPSS
After that the composites failed to start and the following error show up on the logs:

 
exception.code:30516
exception.type: ERROR
exception.severity: 2
exception.name: Token decryption failed.
exception.description: Could not extract information from workflow context token.
exception.fix: Ensure that the Workflow context is not corrupted and it was generated from one of the nodes in the same cluster.

at oracle.bpel.services.workflow.verification.impl.Token.encryptString(Token.java:487)
at oracle.bpel.services.workflow.verification.impl.Token.createTokenFromMap(Token.java:245)
at oracle.bpel.services.workflow.verification.impl.Token.(Token.java:169)
at oracle.bpm.services.internal.InternalBPMToken.(InternalBPMToken.java:40)
at oracle.bpm.services.internal.InternalBPMToken.(InternalBPMToken.java:103)
at oracle.bpm.services.internal.InternalBPMContext.getInternalBPMContext(InternalBPMContext.java:53)
at oracle.bpm.services.internal.InternalBPMContext.getInternalBPMContext(InternalBPMContext.java:47)
at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackUtil.registerEmailActivity(NotificationCallbackUtil.java:81)
at oracle.bpm.casemgmt.fabric.CaseManagementServiceEngine.stateChanged(CaseManagementServiceEngine.java:1449)
at oracle.integration.platform.blocks.mesh.FabricLifecycle.notifyListeners(FabricLifecycle.java:138)
at oracle.integration.platform.blocks.mesh.FabricLifecycle.setState(FabricLifecycle.java:102)
at oracle.integration.platform.blocks.mesh.MeshImpl.postDeployInit(MeshImpl.java:211)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:343)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:69)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212)
at com.sun.proxy.$Proxy528.postDeployInit(Unknown Source)
at oracle.integration.platform.kernel.FabricKernelInitializerServlet$2.run(FabricKernelInitializerServlet.java:1339)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:184)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:209)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:655)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:633)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:39)
Caused by: java.security.PrivilegedActionException: ORABPEL-35012

exception.code:35012
exception.type: ERROR
exception.severity: 2
exception.name: Unable to fetch/generate encryption key.
exception.description: Unable to fetch/generate encryption key.
exception.fix: Check installation/post-installation steps for errors. Check for errors during SOA server startup.

Changes

 The customer re-created the OPSS DB using RCU and pointed the jps-config.xml to the new OPSS

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.