<p>One of our weblogic 8.1s has suddenly started logging giant amounts of logs and filling the disk.</p>

<p>The logs giving us hassle resides in </p>

<pre><code>mydrive:\bea\weblogic81\common\nodemanager\NodeManagerLogs\generatedManagedServer1\managedserveroutput.log
</code></pre>

<p>and the entries in the logfile is just the some kind of entries repeated again and again. Stuff like</p>

<pre><code>19:21:24,470 DEBUG [StdRowLockSemaphore] Lock 'TRIGGER_ACCESS' returned by: LLL-SCHEDULER_QuartzSchedulerThread
19:21:31,923 DEBUG [StdRowLockSemaphore] Lock 'STATE_ACCESS' is deLLLred by: QuartzScheduler_LLL-SCHEDULER-NACDLLLF011219763113220_ClusterManager
19:21:31,923 DEBUG [StdRowLockSemaphore] Lock 'STATE_ACCESS' is being obtained: QuartzScheduler_LLL-SCHEDULER-NACDLLLF011219763113220_ClusterManager
19:21:31,923 DEBUG [StdRowLockSemaphore] Lock 'STATE_ACCESS' given to: QuartzScheduler_LLL-SCHEDULER-NACDLLLF011219763113220_ClusterManager
19:21:31,923 DEBUG [StdRowLockSemaphore] Lock 'TRIGGER_ACCESS' is deLLLred by: QuartzScheduler_LLL-SCHEDULER-NACDLLLF011219763113220_ClusterManager
</code></pre>

<p>...</p>

<pre><code>19:17:46,798 DEBUG [CascadingAction] cascading to saveOrUpdate: mypackage.config.common.Share
19:17:46,798 DEBUG [DefaultSaveOrUpdateEventListener] reassociated uninitialized proxy
19:17:46,798 DEBUG [Cascade] done processing cascade ACTION_SAVE_UPDATE for: mypackage.config.common.FileLocation
19:17:46,798 DEBUG [Cascade] processing cascade ACTION_SAVE_UPDATE for: mypackage.config.common.FileLocation
19:17:46,798 DEBUG [CascadingAction] cascading to saveOrUpdate: mypackage.config.common.Share
19:17:46,798 DEBUG [DefaultSaveOrUpdateEventListener] reassociated uninitialized proxy
</code></pre>

<p>I can't find any debug settings set anywhere.
I've looked in the Remote Start classpath and Arguments for the managed server.</p>

<p>Can anyone point me in the direction to gain control over this logfile?</p>

[{'answer_id': 29825, 'author': 'urini', 'author_id': 373, 'author_profile': 'https://Stackoverflow.com/users/373', 'pm_score': 2, 'selected': False, 'text': '<p>One option is to use serialization. Here\'s a blog post explaining it:</p>\n\n<p><a href="http://weblogs.java.net/blog/emcmanus/archive/2007/04/cloning_java_ob.html" rel="nofollow noreferrer">http://weblogs.java.net/blog/emcmanus/archive/2007/04/cloning_java_ob.html</a></p>\n'}, {'answer_id': 29826, 'author': 'Gishu', 'author_id': 1695, 'author_profile': 'https://Stackoverflow.com/users/1695', 'pm_score': 3, 'selected': True, 'text': "<p>Turn that into a spec:<br>\n-that objects need to implement an interface in order to be allowed into the collection\nSomething like <code>ArrayList&lt;ICloneable&gt;()</code></p>\n\n<p>Then you can be assured that you always do a deep copy - the interface should have a method that is guaranteed to return a deep copy.  </p>\n\n<p>I think that's the best you can do.  </p>\n"}, {'answer_id': 29828, 'author': 'Sergio Acosta', 'author_id': 2954, 'author_profile': 'https://Stackoverflow.com/users/2954', 'pm_score': 1, 'selected': False, 'text': '<p>I suppose it is an ovbious answer:</p>\n\n<p>Make a requisite for the classes stored in the collection to be cloneable. You could check that at insertion time or at retrieval time, whatever makes more sense, and throw an exception.</p>\n\n<p>Or if the item is not cloneable, just fail back to the return by reference option.</p>\n'}]
['https://Stackoverflow.com/questions/29822', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/86/']