Error while reading messagelist from data buffer

[chandrababu_katta]

Hi,

We are getting an error "Error while reading messagelist from data buffer", while processing an Idoc in SAP MII. Our MII version is 15.0, the scheduler jobs showing the status "Pending".

Below is the complete error message

......................................................

Error while reading messagelist from data buffer [EXCEPTION] com.microsoft.sqlserver.jdbc.SQLServerException: The result set has no current row. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:190) at com.microsoft.sqlserver.jdbc.SQLServerResultSet.verifyResultSetHasCurrentRow(SQLServerResultSet.java:483) at com.microsoft.sqlserver.jdbc.SQLServerResultSet.getterGetColumn(SQLServerResultSet.java:2047) at com.microsoft.sqlserver.jdbc.SQLServerResultSet.getValue(SQLServerResultSet.java:2082) at com.microsoft.sqlserver.jdbc.SQLServerResultSet.getValue(SQLServerResultSet.java:2067) at com.microsoft.sqlserver.jdbc.SQLServerResultSet.getLong(SQLServerResultSet.java:2328) at com.sap.sql.jdbc.basic.BasicResultSet.getLong(BasicResultSet.java:89) at com.sap.sql.jdbc.mss.MssInetResultSet.getInt(MssInetResultSet.java:63) at com.sap.sql.jdbc.direct.DirectResultSet.getInt(DirectResultSet.java:233) at com.sap.sql.jdbc.common.dispatch.IntegerResultColumn.getInt(IntegerResultColumn.java:23) at com.sap.sql.jdbc.common.CommonResultSet.getInt(CommonResultSet.java:391) at com.sap.engine.services.dbpool.wrappers.ResultSetWrapper.getInt(ResultSetWrapper.java:343) at com.sap.xmii.databuffer.sqlj.JCoDAO.getCategoryType(JCoDAO.java:2885) at com.sap.xmii.databuffer.sqlj.JCoDAO.readMessages(JCoDAO.java:586) at com.sap.xmii.databuffer.sqlj.JCoDAO.readMessages(JCoDAO.java:550) at com.sap.xmii.databuffer.sqlj.JCoDAO.readMessageList(JCoDAO.java:534) at com.sap.xmii.databuffer.util.JCoDataBufferManager.readMessageFromBuffer(JCoDataBufferManager.java:50) at com.sap.xmii.bls.executables.actions.sap.DataBufferActions.dataBufferQuery(DataBufferActions.java:126) at sun.reflect.GeneratedMethodAccessor1105.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:837) at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:203) at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:86) at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:199) at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50) at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:172) at com.sap.xmii.bls.executables.sequences.RootNode.execute(RootNode.java:39) at com.sap.xmii.bls.engine.TransactionInstance.execute(TransactionInstance.java:1250) at com.sap.xmii.bls.engine.TransactionInstance.run(TransactionInstance.java:808) at com.sap.xmii.scheduler.XacuteWorker$1.run(XacuteWorker.java:245) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:394) at com.sap.xmii.scheduler.XacuteWorker.execute(XacuteWorker.java:242) at com.sap.xmii.ejb.JobBean.onMessage(JobBean.java:89) at sun.reflect.GeneratedMethodAccessor1076.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MessageListenerType.invoke(Interceptors_MessageListenerType.java:86) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at sun.reflect.GeneratedMethodAccessor431.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sap.engine.services.ejb3.util.BeanMethods.executeReflectMethod(BeanMethods.java:314) at com.sap.engine.services.ejb3.jacc.ExecuteMethodPrivilegedAction.run(ExecuteMethodPrivilegedAction.java:38) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:394) at com.sap.engine.services.ejb3.jacc.ContainerJ2EESecurityProviderBaseImpl.doAs(ContainerJ2EESecurityProviderBaseImpl.java:262) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_RunAs.invoke(Interceptors_RunAs.java:24) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Lock.invoke(Interceptors_Lock.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:172) at com.sap.engine.services.ejb3.runtime.impl.MDBProxyInvocationHandler.invoke(MDBProxyInvocationHandler.java:142) at com.sun.proxy.$Proxy4130.onMessage(Unknown Source) at com.sap.jms.client.session.JMSSession.deliverMessage(JMSSession.java:1075) at com.sap.jms.client.session.JMSSession.run(JMSSession.java:898) at com.sap.jms.resourceadapter.RaServerSession.run(RaServerSession.java:139) at com.sap.engine.services.connector.jca15.work.TaskImpl.run(TaskImpl.java:410) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

[adnanmaqbool]

Hi chandrababu.katta

I am also facing the same issue. Are you able to resolve the problem. Can you please share the solution for others also.

Thanks

[oppancs]

Dear Chandrababu,

Firstly I would suggest you to go to the transaction what you run and check the setting (if it is correct) of parameter "MessageCategory" of action "QueryDataBuffer".

Probably you have one scheduled message dispatcher transaction dispatching both type of messages. But different transactions saving into a custom action queue for inbound and outbound messages.

Another reason can be long running threads that can cause Pending status.

In order to resolve the issue stop the scheduler for all jobs and then re-enable them, afterwards, longrunning threads can disappeared and sub transactions start running.

After that please pay close attention to the threads on the SAP MMC and memory usage. In case issue persists you can restart the whole application server to clear the memory and threads.

Regards,
Barnabás Paksi