My Oracle Support Banner

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

Last updated on MARCH 23, 2019

Applies to:

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


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:$WorkWithListener@5d555d55] [userId: <anonymous>] [ecid: <ECID>] [APP: soa-infra] [dcid:<DCID>] Self Container id expired <SCID>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] [] [] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: <ECID> [APP: soa-infra] [dcid: <DCID>] CUBE_GENERIC_TIMER timed out at 2010-11-04 14:03:48.03


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.