Default Trace is logging huge on our Portal System

[Former Member]

Hi all,

We are experiencing huge logging on our Portal server. This is a NetWeaver 7.0 SP15 Java only system. The default trace is filled with this notification and it logs about 10MB every few minutes.

#1.#005056A13EB0002700124860000027D90004617318B4F29F#1233046870487#com.sap.engine.services.connector.resource.impl.MCEventHandler##com.sap.engine.services.connector.resource.impl.MCEventHandler####n/a##f3ffb870e86b11dd9c7b005056a13eb0#SAPEngine_System_Thread[impl:5]_71##0#0#Debug##Java###>>> com.sap.engine.services.connector.resource.impl.MCEventHandler@75f975f9 --> 57(locTrSupp:false).cleanup({0}), shared: {1},  destroyed {2}, invoked from: {3}#4#true#false#false#java.lang.Exception
        at java.lang.Throwable.<init>(Throwable.java:58)
        at com.sap.engine.services.connector.Log.getStackTrace(Log.java:61)
        at com.sap.engine.services.connector.resource.impl.MCEventHandler.cleanup(MCEventHandler.java:358)
        at com.sap.engine.services.connector.resource.impl.MCEventHandler.dissociateAfterLocalTransaction(MCEventHandler.java:815)
        at com.sap.engine.services.connector.resource.impl.MCEventHandler.localTransactionCommitted(MCEventHandler.java:508)
        at com.sap.engine.services.dbpool.spi.LocalTXManagedConnectionImpl.clientCommit(LocalTXManagedConnectionImpl.java:585)
        at com.sap.engine.services.dbpool.cci.ConnectionHandle.commit(ConnectionHandle.java:206)
        at com.sap.caf.eu.gp.base.db.TransactionController.updateTransaction(TransactionController.java:215)
        at com.sap.caf.eu.gp.base.db.TransactionController.closeTransaction(TransactionController.java:147)
        at com.sap.caf.eu.gp.base.db.TransactionController.closeTransaction(TransactionController.java:133)
        at com.sap.caf.eu.gp.model.co.execute.impl.CallableObjectExecutorPersistenceImpl.closeTransaction(CallableObjectExecutorPersistenceImpl.java:139)
        at com.sap.caf.eu.gp.model.co.execute.impl.CallableObjectExecutorPersistenceImpl.readOverdueTasks(CallableObjectExecutorPersistenceImpl.java:621)
        at com.sap.caf.eu.gp.model.co.execute.impl.CallableObjectExecutorTimeoutProcessor.process(CallableObjectExecutorTimeoutProcessor.java:158)
        at com.sap.caf.eu.gp.model.co.execute.impl.CallableObjectExecutorTimeoutProcessor.run(CallableObjectExecutorTimeoutProcessor.java:205)
        at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
        at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
        at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)

How can we solve this?

Best regards,

Jan

[Former Member]

There is nothing wrong with sapmnt.

[hofmann]

Then deactivate the Guided Procedures applications in the NWA.

br,

Tobias

[Former Member]

Any suggestions? Or is it better to post this thread in the Portal subforums?

Best regards,

Jan

[hofmann]

Hi,

verify that the share sapmnt is available (
<server>\sapmnt). If this share isn't available, the Guided Procedures will create a huge amount of logs (and eventually crash your system).

br,

Tobias