SOA Suite: T3:AIA 12C:Failed To Create "java:comp/env/ejb/local/bpel/CubeDeliveryBean

(Doc ID 2383204.1)

Last updated on APRIL 12, 2018

Applies to:

Oracle SOA Suite - Version 12.2.1.1.0 and later
Information in this document applies to any platform.

Symptoms

On :SOA 12.2.1.1.0

In the cluster environment, the SOA composite uses the FIFO recequencer Mediator. When the SOA servers get restarted, the soa instance stuck at Mediator with the running instance.

Log files do not provide too much information.

From the query:
select to_char(sysdate,'YYYY-MM-DD HH24:MI:SS') time,decode

(gs.status,0,'READY',1,'LOCKED',3,'ERRORED',4,'TIMED_OUT',6,'GROUP_ERROR',null
)

GROUP_STATUS,decode

(m.status,0,'READY',2,'PROCESSED',3,'ERRORED',4,'TIMED_OUT',5,'ABORTED',null)

MSG_STATUS,count(*), gs.component_dn from mediator_group_status gs,

mediator_resequencer_message m where m.group_id = gs.group_id group by
gs.status,

m.status, gs.component_dn order by gs.component_dn, gs.status;

For the succsessful instance, the MSG_STATUS is marked as PROCESSED, but for the stuck running instance, it is marked as READY, never changed to PROCESSED.

This query:

select group_id,status,container_id, creation_date, last_received_time from

mediator_group_status;

shows the container_id using the soa server name. In the cluster environment, when the 1st data is processed, container_id=soa_server1. After shutdown both soa_servers, if restarted only soa server2 and used the same data, then it
can not find soa_server1, which seems the problem.

If submit with the different data (such as GROUP_2 or GROUP_3), then it works fine.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms