Explanation for Messages "Cube_generic_timer Timed Out" & "Self Container Id Expired" (Doc ID 1275808.1)

Last updated on APRIL 18, 2011

Applies to:

Oracle SOA Platform - Version: 11.1.1.3.0 and later   [Release: 11gR1 and later ]
Information in this document applies to any platform.

Goal

To understand the meaning of messages,"Cube_generic_timer Timed Out" & "Self Container Id Expired" found in the SOA Server logs


[2010-11-08T09:49:35.717-05:00] [soa_server1] [WARNING] [] [oracle.soa.mediator.dispatch.db] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@5d555d55] [userId: <anonymous>] [ecid: 0000IkNv6G0EwG15zv4EyW1Coim^000000,1:17291] [APP: soa-infra] [dcid: e9e1d2b01118b09d:7f4c72de:12c17efcd2b:-7ffd-0000000000000002] Self Container id expired :891970D0E83911DFBFE079FD6A1F00BA last renewal time :2010-11-08 09:49:33.254 before expiry interval:300000 ms but not removing it.


[2010-11-04T14:03:48.030-04:00] [soa_server1] [NOTIFICATION] [] [oracle.bpm.analytics.cubes] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IkO3kiyEwG15zv4EyW1Coim^0000RQ,0] [APP: soa-infra] [dcid: e9e1d2b01118b09d:7f4c72de:12c17efcd2b:-7ffd-000000000000107d] CUBE_GENERIC_TIMER timed out at 2010-11-04 14:03:48.03


Solution

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