My Oracle Support Banner

Unable To Activate Session In Service Bus Console (Doc ID 2516342.1)

Last updated on APRIL 06, 2023

Applies to:

Oracle Service Bus - Version 12.2.1.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.1.0.0 version, OSB Core Functionality

Unable to activate session in service bus console

The console is stuck on "Progress indicator - processing... Please wait" window for ages. In the meantime the /console console becomes unresponsive for about 30~ and after it starts responding the admin server is in the Warning state with "Symtom{STUCK_THREADS,HIGH,ThreadPoolRuntime,ThreadPool has stuck threads}" information.

Restarting the servers with clearing cache, tmp and sessions did not help at all.

ERROR
-----------------------
#EM_SYSTEM_POOL#:StuckThreadDetection" #168 daemon prio=5 os_prio=0 tid=0x00007f7707abf800 nid=0x4c86 waiting on condition [0x00007f76fa325000]
  
  java.lang.Thread.State: TIMED_WAITING (sleeping)
  
  at java.lang.Thread.sleep(Native Method)
  
  at oracle.sysman.core.common.workmanager.Work.handleScheduledWork(Work.java:453)
  
  at oracle.sysman.core.common.workmanager.Work.call(Work.java:284)
  
  at oracle.sysman.core.common.workmanager.Work.call(Work.java:50)
  
  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
  
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
  
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
  
  at java.lang.Thread.run(Thread.java:748)

"[STUCK] ExecuteThread: '54' for queue: 'weblogic.kernel.Default (self-tuning)'" #131 daemon prio=1 os_prio=0 tid=0x00007f772ca26800 nid=0x4b3d in Object.wait() [0x00007f770fcb4000]
  
  java.lang.Thread.State: TIMED_WAITING (on object monitor)
  
  at java.lang.Object.wait(Native Method)
  
  at weblogic.management.provider.internal.ActivateTaskImpl.waitForCompletion(ActivateTaskImpl.java:496)
  
  - locked (a weblogic.management.provider.internal.ActivateTaskImpl)
  
  at weblogic.management.provider.internal.ActivateTaskImpl.waitForTaskCompletion(ActivateTaskImpl.java:474)
  
  at weblogic.management.provider.internal.EditAccessImpl.activateChangesAndWaitForCompletion(EditAccessImpl.java:1716)
  
  at weblogic.management.mbeanservers.edit.internal.ConfigurationManagerMBeanImpl.activate(ConfigurationManagerMBeanImpl.java:435)
  
  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 weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean.java:531)
  
  at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
  
  at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
  
  at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$21.run(WLSMBeanServerInterceptorBase.java:589)
  
  at java.security.AccessController.doPrivileged(Native Method)


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users had to restart servers.

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
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.