Server And Domain Logs Are Fill Up Extremely Fast Taking Up Disk Space

(Doc ID 886683.1)

Last updated on AUGUST 13, 2013

Applies to:

Oracle Communications Order and Service Management - Version: 2.5.2 to 7.0.3 - Release: 2.5 to 7.0.0
Information in this document applies to any platform.

Symptoms

The Weblogic Server and Domain logs are filling up rapidly and the file system is running out of disk space. The logs are filling up with the following exceptions:
####<Sep 11, 2009 6:26:59 PM EDT> <Error> <oms.core> <rsprod84>
<ttmoss_server> <Timer-3> <> <BEA1-3D507D01
CCEB087772F> <> <1252708019651> <600129> <SQL Exception 17,008 : Closed
Connection
java.sql.SQLException: Closed Connection
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:208)
at oracle.jdbc.driver.PhysicalConnection.createStatement(PhysicalConnection.java:731)
at oracle.jdbc.driver.PhysicalConnection.createStatement(PhysicalConnection.java:707)
at weblogic.jdbc.wrapper.Connection.createStatement(Connection.java:456)
at com.mslv.oms.dataaccesslayer.QueryProxy.createStatement(Unknown Source)
at com.mslv.oms.dataaccesslayer.a.execute(Unknown Source)
at com.mslv.oms.eventengine.EventDispatcherEJB.processTimeout(Unknown Source)
at
com.mslv.oms.eventengine.EventDispatcher_86q3j1_EOImpl.processTimeout(EventDispatcher_86q3j1_EOImpl.
java:503
at com.mslv.oms.poller.a.handleNotification(Unknown Source)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor$ListenerWrapper.handleNotification(DefaultMBea
nServerI
terceptor.java:1652)
at
javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.ja
va:221)
at
javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java
:184)
at javax.management.timer.Timer.sendNotification(Timer.java:1295)
at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1264)
at javax.management.timer.TimerAlarmClock.run(Timer.java:1347)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
>
####<Sep 11, 2009 6:26:59 PM EDT> <Error> <oms.core> <rsprod84>
<ttmoss_server> <Timer-3> <> <BEA1-3D507D01

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