Oracle Weblogic Server (MOSC)

MOSC Banner

Connection for pool "EBSDataSource" has been closed. Java stack trace in the OACORE error log.

edited Jan 4, 2016 10:01AM in Oracle Weblogic Server (MOSC) 1 commentAnswered

Hi ,

When we click Additional Contracts and Configuration tabs in the self service page we get "Failure of server Apache bridge error" and below is the Java error stack that we see in the OACORE log file. We see stuck threads in the log file. Please advise

####<Dec 23, 2015 5:28:34 PM EST> <Info> <JDBC> <leaapq3.ct.pb.com> <oacore_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <acb55662b15581c0:bd8de54:151cc5ce5c3:-8000-00000000000008e1> <1450909714626> <BEA-001128> <Connection for pool "EBSDataSource" has been closed.>

####<Dec 23, 2015 5:31:43 PM EST> <Info> <WorkManager> <leaapq3.ct.pb.com> <oacore_server1> <[ACTIVE] ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <acb55662b15581c0:bd8de54:151cc5ce5c3:-8000-00000000000008ea> <1450909903918> <BEA-002939> <maximum thread constraint ClusterMessaging is reached 6 times for last 479 seconds>

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center