com.sap.engine.services.dsr.res.DSRResourceBundle - Inconsistent action

[Former Member]

Hi Everybody,

We are running some stress test scripts and it seems that all users log this error in the default trace.

Does anybody have an idea about what is failing.

Br Rasmus

#1.5#000E7FB525830016000006B9000013BC0003F6FC902EE740#1115989541327#com.sap.engine.services.dsr##com.sap.engine.services.dsr#AAKONL#2099##DSV45SAP3_EPP_4118851#Guest#b557e5f0c3af11d99d9f000e7fb52583#SAPEngine_Application_Thread[impl:3]_11##0#0#Error#1#/System/Server#Java#DSR_6#com.sap.engine.services.dsr.res.DSRResourceBundle#Inconsistent action content - the record set could not be written##

#1.5#000E7FB525830016000006BA000013BC0003F6FC902EED3C#1115989541327#com.sap.engine.services.dsr##com.sap.engine.services.dsr#AAKONL#2099##DSV45SAP3_EPP_4118851#Guest#b557e5f0c3af11d99d9f000e7fb52583#SAPEngine_Application_Thread[impl:3]_11##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.dsr.InvalidActionStateException: Inconsistent action content - the record set could not be written

at com.sap.engine.services.dsr.DSRComponentImpl0.endAction(DSRComponentImpl0.java:259)

at com.sap.engine.services.dsr.DSRHandler.closeAction(DSRHandler.java:789)

at com.sap.engine.services.dsr.DSRHandler.closeAction(DSRHandler.java:763)

at com.sap.engine.services.dsr.DSRHandler.methodEnd(DSRHandler.java:412)

at com.sap.engine.library.bytecode.tracing.TracingPlugin.methodEnd(TracingPlugin.java:201)

at com.sap.engine.library.bytecode.tracing.Tracer.methodEnd(Tracer.java:152)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:93)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)

at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)

[Former Member · Accepted solution]

Come on you old sap Guru's somebody must know something about this.

[former_member239234 · Accepted solution]

What j2ee engine version you are using?

[Former Member · Accepted solution]

Java

Kernel Version 6.40

PatchLevel 87037.313

[former_member239234 · Accepted solution]

Hi Rasmus,

This exception is not critical. It just informs that a particular distributed statistical record could not be written. Reasons could be for example very big server load(which could be obtained with some stress tool - As I understand it is like your case).

Just, the library which is responsible for writing distributed statistics records, fails writing of part of the records when the load is very big.

These stacktraces are excluded from the last service packs(its logging severity is now changed to "DEBUG").

Best regards,

Aleksandar

[Former Member · Accepted solution]

Ok, thanks for your help.

I was just wondering. I would believe that it very demanding of the server to throw all these exceptions. And when adding that to an already stressed server we might have a problem.

Br Rasmus

[former_member239234 · Accepted solution]

No problem Rasmus,

After little period of time the distributed statistics is entering into selflimitation mode and those overwriting is not more the case.

That is why it is not dangerous for the j2ee engine.

I recomend upgrade of the distributed statistics at least or the whole j2ee engine to SP12(this problem is fixed little bit earlier, SP12 is now to the customers, as I know).

Best regards,

Aleksandar