Skip to Content
0
Former Member
Jul 27, 2005 at 01:20 PM

JMS and BufferUnderflowException

28 Views

Hi!

when using JMS i find everynow and then a strange BufferUnderflowException in the defaultTrace which looks like this:

#1.5#001143D58F14006D000000150000568D0003FCE139143C66#1122469185600#com.sap.jms##com.sap.jms.server.destinationcontainer.agent.QueueAgent.run() instance=default#J2EE_GUEST#0##<serverreplaced>_XID_70#Guest#dea1b340fe9d11d9a536001143d58f14#SAPEngine_Application_Thread[impl:3]_109##0#0#Error##Plain###com.sap.jms.protocol.BufferUnderflowException: BufferUnderflow

at com.sap.jms.protocol.PacketImpl.checkUnderflow(PacketImpl.java:352)

at com.sap.jms.protocol.PacketImpl.getByte(PacketImpl.java:379)

at com.sap.jms.protocol.message.MessageRequest.getJMSDeliveryMode(MessageRequest.java:679)

at com.sap.jms.protocol.message.MessageRequest.getMessageFilterProperties(MessageRequest.java:941)

at com.sap.jms.server.destinationcontainer.messagequeue.selector.Interpretator.setMessage(Interpretator.java:83)

at com.sap.jms.server.destinationcontainer.messagequeue.selector.MessageSelector.matches(MessageSelector.java:84)

at com.sap.jms.server.destinationcontainer.messagequeue.impl.ptp.MessageRepositoryImpl.retrieveMessagesFromMasterQueueFixedPriority(MessageRepositoryImpl.java:779)

at com.sap.jms.server.destinationcontainer.messagequeue.impl.ptp.MessageRepositoryImpl.fillUpSelectorWorklist(MessageRepositoryImpl.java:966)

at com.sap.jms.server.destinationcontainer.messagequeue.impl.ptp.BrowserViewImpl.getCurrentItem(BrowserViewImpl.java:235)

at com.sap.jms.server.destinationcontainer.messagequeue.impl.ptp.BrowserViewImpl.peek(BrowserViewImpl.java:73)

at com.sap.jms.server.destinationcontainer.agent.QueueAgent.processConsumer(QueueAgent.java:120)

at com.sap.jms.server.destinationcontainer.agent.QueueAgent.run(QueueAgent.java:93)

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)

In my application i have trouble with the JMS communication where it seems that now all messages are being received which have been sent. Could the above mentioned exception cause this ?