My Oracle Support Banner

Unable To Successfully Destroy OWSM Engine Instance: Null (Doc ID 2201479.1)

Last updated on OCTOBER 01, 2021

Applies to:

Oracle SOA Suite - Version to [Release 12c]
Information in this document applies to any platform.


On a BPEL process that uses OWSM Policies to encrypt payload and then decrypt the information before inserting it into a DB, and while using a trigger on the DB side that encrypts a field at insert time works OK until a error is thrown on the DB side, for example, after trying to insert the same record again, after this the composite starts throwing the error "Unable to successfully destroy OWSM engine instance: null" and the only way to revert this is to
- redeploy the composite
- bounce the server

It is observed that even after redeploy the issue is not resolve since after this owsm instead of inserting the required record id insert the actual string with the encryption information found on the trace from the payload, i.e. if the encrypted value of the field (visible on EM through the console was "encrypted:xLOgXcXZnj7/04Xnk4Q8O2qRGmW/sTueK14eJbDutu0=;keyname:pii-csf-key;origin:OWSM_POC") then on the table is observed that the same value is inserted

[2016-10-06T14:48:05.261-01:00] [soa_server3] [TRACE] [] [oracle.soa.bpel.engine] [tid: [STANDBY].ExecuteThread: '35' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: ,0] [APP: soa-infra] [partition-name: DOMAIN] [tenant-name: GLOBAL] [ soa-infra] [ fabric] [ bpelprocess1_client_ep] [ BPELProcess1_pt] [oracle.soa.tracking.FlowId: ] [oracle.soa.tracking.InstanceId: ] [oracle.soa.tracking.SCAEntityId: ] [oracle.soa.tracking.FaultId: ] [composite_name: OWSM_POC!1.0] [FlowId: ] [SRC_CLASS: BaseBPELActivityWMP] [SRC_METHOD: perform] error thrown[[ faultName: {{}bindingFault}
messageType: {{}RuntimeFaultMessage}
parts: {{
summary=Unable to successfully destroy OWSM engine instance: null

The issue can be reproduced at will with the following steps:
1. Execute composite to insert a new record (id1)
2. Execute composite to insert the same record (id1) fails as expected since the record already exists
3. Execute composite to insert a new record (id2) fails again and after this never recovers until redeploy and bounce




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

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