cancel
Showing results for 
Search instead for 
Did you mean: 

JMS underflow errors

Former Member
0 Kudos

Hi,

We have an application with multiple queues performing various tasks as messages flow through the system.

All appears to be working fine. However, the logs are filled with errors.

These are of the format:

PacketImpl.checkUnderflow(). Try to read 1, bytes from position: 599

m_start position is: 0. m_position is: 599. Payload start is: 14. The messsage size is: 599

m_buffer size is: 599

There are countless instances of this type of error for each message on each queue.

Would anyone know what is causing this?

We think that with the huge amount of logging being performed (perhaps unnecessarily?) it is having an effect on performance when sending thousands of messages through the system.

Any assistance would be gratefully received.

Regards,

Gerry

Accepted Solutions (0)

Answers (1)

Answers (1)

ekaterinamitova
Advisor
Advisor
0 Kudos

Hi Gerry,

Can you tell me the version of your system? You can check the severity of the JMS logs, the default is ERROR, but I suppose that your severity is set to DEBUG and that's why you can see these errors.

Best regards,

Ekaterina

Former Member
0 Kudos

Hi Ekaterina,

Thanks for replying.

We're using Netweaver CE 7.1 SP3

Looking at the log configuration in NWA I see that the /System/Server (and all child categories) are set to Info.

I was guessing that category /System/Server/MessagingSystem might have be the category to set and switched it to Fatal. That didn't help as the errors were still coming through.

Is it ok to turn down logging and ignore these errors? Or should we find the cause and correct it? Is it a configuration issue?

Thanks,

Gerry

ekaterinamitova
Advisor
Advisor
0 Kudos

Hi Gerry,

I don't think that this is a configuration issue. Can you send me the whole trace file. We'll check it and send you back a reply.

Thank you.

Best regards,

Ekaterina

Former Member
0 Kudos

Hi Ekaterina,

I will run some files though the queues and send the logs.

In the meantime, there looks to be another issue.

We deployed our app with a jms-resources.xml defining all queues, topics and connection factories.

Part of the config was:

	<connection-factory>
		<name>jms/dts/queueConnectionFactory</name>
		<sap-local-factory-type>
			<type>javax.jms.XAQueueConnectionFactory</type>
			<virtual-provider>default</virtual-provider>
		</sap-local-factory-type>
	</connection-factory>
	<connection-factory>
		<name>jms/dts/topicConnectionFactory</name>
		<sap-local-factory-type>
			<type>javax.jms.XATopicConnectionFactory</type>
			<virtual-provider>default</virtual-provider>
		</sap-local-factory-type>
	</connection-factory>

However, browsing the jms resources on NWA, we see that both connection factories are no longer XA. If I try to manually create an XA factory it is reset to a non-XA factory.

How can we define an XA connection factory?

Many Thanks,

Gerry

Former Member
0 Kudos

Hi Ekaterina,

I've found the logging location for com/sap/jms and it was set to severity error.

It points me towards log\defaultTrace_00.trc but I don't see the messages in this file that I see ont eh log viewer on NWA.

However, I do see several MB of this (see below) in the log/system/server_00.0 log. Not sure how much of this I should send you so I've just included a snippet. If you need more it might be best to email the files.

Also, the logs are parameterised. Where would I look for the actual data for this? Would I need to send that as well?

Thanks,

Gerry

#1.5 #02004C4F4F500026000020F200000DA80087E01467F41A0A#1215086031163#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52592#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053a]###b2bf526048e011dd9c9e02004c4f4f50#Thread[Managed_Application_Thread_7,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###PacketImpl.checkUnderflow(). Try to read  {0},  bytes from position: {1}#2#1#204305#
#1.5 #02004C4F4F500026000020F300000DA80087E01467F41A0A#1215086031163#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52592#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053a]###b2bf526048e011dd9c9e02004c4f4f50#Thread[Managed_Application_Thread_7,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_start position is: {0}. m_position is: {1}. Payload start is: {2}. The messsage size is: {3} #4#0#204305#14#204305#
#1.5 #02004C4F4F500026000020F400000DA80087E01467F41A0A#1215086031163#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52592#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053a]###b2bf526048e011dd9c9e02004c4f4f50#Thread[Managed_Application_Thread_7,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_buffer size is: {0}#1#204305#
#1.5 #02004C4F4F50003100001E7800000DA80087E01467F24932#1215086031257#/System/Server#amt-sybex.com/dts-core-sda#com.sap.engine.services.ts#Guest#52564#SAP J2EE Engine JTA Transaction : [03a5bffffffa60052ffffffee]###d3ebe7f048e011ddb88e02004c4f4f50#Thread[Managed_Application_Thread_18,5,Managed_Application_Thread]##0#0#Error#1#com.sap.engine.services.ts#Java#ts_0003#com.sap.engine.services.ts.exceptions.TSResourceBundle#Status of ( {0} ) should be active, but it is {1}.#2#SAP J2EE Engine JTA Transaction : [03a5bffffffa60052ffffffee]#STATUS_MARKED_ROLLBACK = 1#
#1.5 #02004C4F4F500025000024CC00000DA80087E01467F429AA#1215086031272#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52593#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053b]###b2888af048e011dd979f02004c4f4f50#Thread[Managed_Application_Thread_6,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###PacketImpl.checkUnderflow(). Try to read  {0},  bytes from position: {1}#2#1#5056#
#1.5 #02004C4F4F500025000024CD00000DA80087E01467F429AA#1215086031272#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52593#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053b]###b2888af048e011dd979f02004c4f4f50#Thread[Managed_Application_Thread_6,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_start position is: {0}. m_position is: {1}. Payload start is: {2}. The messsage size is: {3} #4#0#5056#14#5056#
#1.5 #02004C4F4F500025000024CE00000DA80087E01467F429AA#1215086031272#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52593#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053b]###b2888af048e011dd979f02004c4f4f50#Thread[Managed_Application_Thread_6,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_buffer size is: {0}#1#5056#
#1.5 #02004C4F4F500025000024CF00000DA80087E01467F429AA#1215086031272#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52593#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053b]###b2888af048e011dd979f02004c4f4f50#Thread[Managed_Application_Thread_6,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###PacketImpl.checkUnderflow(). Try to read  {0},  bytes from position: {1}#2#1#5056#
#1.5 #02004C4F4F500025000024D000000DA80087E01467F429AA#1215086031272#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52593#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053b]###b2888af048e011dd979f02004c4f4f50#Thread[Managed_Application_Thread_6,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_start position is: {0}. m_position is: {1}. Payload start is: {2}. The messsage size is: {3} #4#0#5056#14#5056#
#1.5 #02004C4F4F500025000024D100000DA80087E01467F429AA#1215086031272#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52593#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053b]###b2888af048e011dd979f02004c4f4f50#Thread[Managed_Application_Thread_6,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_buffer size is: {0}#1#5056#
#1.5 #02004C4F4F50003100001E7D00000DA80087E01467F24932#1215086031272#/System/Server##com.sap.jms.resourceadapter.RaServerSession#Guest#52564#SAP J2EE Engine JTA Transaction : [03a5bffffffa60052ffffffee]###d3ebe7f048e011ddb88e02004c4f4f50#Thread[Managed_Application_Thread_18,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms#Plain###Application exception happened while invoking onMessage() method. It was caught and suppressed in the ServerSession. For more details see the trace file#
#1.5 #02004C4F4F50003100001E7E00000DA80087E01467F43D32#1215086031272#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52594#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053c]###d3ebe7f048e011ddb88e02004c4f4f50#Thread[Managed_Application_Thread_18,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###PacketImpl.checkUnderflow(). Try to read  {0},  bytes from position: {1}#2#1#14730#
#1.5 #02004C4F4F50003100001E7F00000DA80087E01467F43D32#1215086031272#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52594#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053c]###d3ebe7f048e011ddb88e02004c4f4f50#Thread[Managed_Application_Thread_18,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_start position is: {0}. m_position is: {1}. Payload start is: {2}. The messsage size is: {3} #4#0#14730#14#14730#
#1.5 #02004C4F4F50003100001E8000000DA80087E01467F43D32#1215086031272#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52594#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053c]###d3ebe7f048e011ddb88e02004c4f4f50#Thread[Managed_Application_Thread_18,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_buffer size is: {0}#1#14730#
#1.5 #02004C4F4F50003100001E8100000DA80087E01467F43D32#1215086031272#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52594#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053c]###d3ebe7f048e011ddb88e02004c4f4f50#Thread[Managed_Application_Thread_18,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###PacketImpl.checkUnderflow(). Try to read  {0},  bytes from position: {1}#2#1#14730#
#1.5 #02004C4F4F50003100001E8200000DA80087E01467F43D32#1215086031272#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52594#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053c]###d3ebe7f048e011ddb88e02004c4f4f50#Thread[Managed_Application_Thread_18,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_start position is: {0}. m_position is: {1}. Payload start is: {2}. The messsage size is: {3} #4#0#14730#14#14730#
#1.5 #02004C4F4F50003100001E8300000DA80087E01467F43D32#1215086031272#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52594#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053c]###d3ebe7f048e011ddb88e02004c4f4f50#Thread[Managed_Application_Thread_18,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_buffer size is: {0}#1#14730#
#1.5 #02004C4F4F500029000022DA00000DA80087E01467F4588A#1215086031288#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52595#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053d]###b2cff43048e011dd986e02004c4f4f50#Thread[Managed_Application_Thread_11,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###PacketImpl.checkUnderflow(). Try to read  {0},  bytes from position: {1}#2#1#6891#
#1.5 #02004C4F4F500029000022DB00000DA80087E01467F4588A#1215086031288#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52595#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053d]###b2cff43048e011dd986e02004c4f4f50#Thread[Managed_Application_Thread_11,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_start position is: {0}. m_position is: {1}. Payload start is: {2}. The messsage size is: {3} #4#0#6891#14#6891#
#1.5 #02004C4F4F500029000022DC00000DA80087E01467F4588A#1215086031288#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52595#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053d]###b2cff43048e011dd986e02004c4f4f50#Thread[Managed_Application_Thread_11,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_buffer size is: {0}#1#6891#
#1.5 #02004C4F4F500029000022DD00000DA80087E01467F4588A#1215086031288#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52595#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053d]###b2cff43048e011dd986e02004c4f4f50#Thread[Managed_Application_Thread_11,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###PacketImpl.checkUnderflow(). Try to read  {0},  bytes from position: {1}#2#1#6891#
#1.5 #02004C4F4F500029000022DE00000DA80087E01467F4588A#1215086031288#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52595#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053d]###b2cff43048e011dd986e02004c4f4f50#Thread[Managed_Application_Thread_11,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_start position is: {0}. m_position is: {1}. Payload start is: {2}. The messsage size is: {3} #4#0#6891#14#6891#
#1.5 #02004C4F4F500029000022DF00000DA80087E01467F4588A#1215086031288#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52595#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053d]###b2cff43048e011dd986e02004c4f4f50#Thread[Managed_Application_Thread_11,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_buffer size is: {0}#1#6891#
#1.5 #02004C4F4F5000240000217E00000DA80087E01467F46442#1215086031757#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52596#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053e]###b19ec73048e011dd8a8102004c4f4f50#Thread[Managed_Application_Thread_12,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###PacketImpl.checkUnderflow(). Try to read  {0},  bytes from position: {1}#2#1#4223#
#1.5 #02004C4F4F5000240000217F00000DA80087E01467F46442#1215086031757#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52596#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053e]###b19ec73048e011dd8a8102004c4f4f50#Thread[Managed_Application_Thread_12,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_start position is: {0}. m_position is: {1}. Payload start is: {2}. The messsage size is: {3} #4#0#4223#14#4223#
#1.5 #02004C4F4F5000240000218000000DA80087E01467F46442#1215086031757#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52596#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053e]###b19ec73048e011dd8a8102004c4f4f50#Thread[Managed_Application_Thread_12,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_buffer size is: {0}#1#4223#
#1.5 #02004C4F4F5000240000218100000DA80087E01467F46442#1215086031757#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52596#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053e]###b19ec73048e011dd8a8102004c4f4f50#Thread[Managed_Application_Thread_12,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###PacketImpl.checkUnderflow(). Try to read  {0},  bytes from position: {1}#2#1#4223#
#1.5 #02004C4F4F5000240000218200000DA80087E01467F46442#1215086031757#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52596#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053e]###b19ec73048e011dd8a8102004c4f4f50#Thread[Managed_Application_Thread_12,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_start position is: {0}. m_position is: {1}. Payload start is: {2}. The messsage size is: {3} #4#0#4223#14#4223#
#1.5 #02004C4F4F5000240000218300000DA80087E01467F46442#1215086031757#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52596#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053e]###b19ec73048e011dd8a8102004c4f4f50#Thread[Managed_Application_Thread_12,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_buffer size is: {0}#1#4223#
#1.5 #02004C4F4F50002F0000202500000DA80087E01467F46C12#1215086031772#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52597#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053f]###c3ade2d048e011dd92fd02004c4f4f50#Thread[Managed_Application_Thread_17,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###PacketImpl.checkUnderflow(). Try to read  {0},  bytes from position: {1}#2#1#4115#
#1.5 #02004C4F4F50002F0000202600000DA80087E01467F46C12#1215086031772#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52597#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053f]###c3ade2d048e011dd92fd02004c4f4f50#Thread[Managed_Application_Thread_17,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_start position is: {0}. m_position is: {1}. Payload start is: {2}. The messsage size is: {3} #4#0#4115#14#4115#
#1.5 #02004C4F4F50002F0000202700000DA80087E01467F46C12#1215086031772#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52597#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053f]###c3ade2d048e011dd92fd02004c4f4f50#Thread[Managed_Application_Thread_17,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_buffer size is: {0}#1#4115#
#1.5 #02004C4F4F50002F0000202800000DA80087E01467F46C12#1215086031772#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52597#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053f]###c3ade2d048e011dd92fd02004c4f4f50#Thread[Managed_Application_Thread_17,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###PacketImpl.checkUnderflow(). Try to read  {0},  bytes from position: {1}#2#1#4115#
#1.5 #02004C4F4F50002F0000202900000DA80087E01467F46C12#1215086031772#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52597#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053f]###c3ade2d048e011dd92fd02004c4f4f50#Thread[Managed_Application_Thread_17,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_start position is: {0}. m_position is: {1}. Payload start is: {2}. The messsage size is: {3} #4#0#4115#14#4115#
#1.5 #02004C4F4F50002F0000202A00000DA80087E01467F46C12#1215086031772#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52597#SAP J2EE Engine JTA Transaction : [03a5bffffffa60053f]###c3ade2d048e011dd92fd02004c4f4f50#Thread[Managed_Application_Thread_17,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_buffer size is: {0}#1#4115#
#1.5 #02004C4F4F50002D000023EB00000DA80087E01467F473E2#1215086031804#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52598#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005310]###b2e5780048e011dd8b7702004c4f4f50#Thread[Managed_Application_Thread_9,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###PacketImpl.checkUnderflow(). Try to read  {0},  bytes from position: {1}#2#1#4490#
#1.5 #02004C4F4F50002D000023EC00000DA80087E01467F473E2#1215086031804#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52598#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005310]###b2e5780048e011dd8b7702004c4f4f50#Thread[Managed_Application_Thread_9,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_start position is: {0}. m_position is: {1}. Payload start is: {2}. The messsage size is: {3} #4#0#4490#14#4490#
#1.5 #02004C4F4F50002D000023ED00000DA80087E01467F473E2#1215086031804#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52598#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005310]###b2e5780048e011dd8b7702004c4f4f50#Thread[Managed_Application_Thread_9,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_buffer size is: {0}#1#4490#
#1.5 #02004C4F4F50002D000023EE00000DA80087E01467F473E2#1215086031804#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52598#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005310]###b2e5780048e011dd8b7702004c4f4f50#Thread[Managed_Application_Thread_9,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###PacketImpl.checkUnderflow(). Try to read  {0},  bytes from position: {1}#2#1#4490#
#1.5 #02004C4F4F50002D000023EF00000DA80087E01467F473E2#1215086031804#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52598#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005310]###b2e5780048e011dd8b7702004c4f4f50#Thread[Managed_Application_Thread_9,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_start position is: {0}. m_position is: {1}. Payload start is: {2}. The messsage size is: {3} #4#0#4490#14#4490#
#1.5 #02004C4F4F50002D000023F000000DA80087E01467F473E2#1215086031804#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52598#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005310]###b2e5780048e011dd8b7702004c4f4f50#Thread[Managed_Application_Thread_9,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_buffer size is: {0}#1#4490#
#1.5 #02004C4F4F50002A0000243400000DA80087E01467F47BB2#1215086031819#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52599#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005311]###b2d4d63048e011ddc10602004c4f4f50#Thread[Managed_Application_Thread_14,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###PacketImpl.checkUnderflow(). Try to read  {0},  bytes from position: {1}#2#1#4167#
#1.5 #02004C4F4F50002A0000243500000DA80087E01467F47BB2#1215086031819#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52599#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005311]###b2d4d63048e011ddc10602004c4f4f50#Thread[Managed_Application_Thread_14,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_start position is: {0}. m_position is: {1}. Payload start is: {2}. The messsage size is: {3} #4#0#4167#14#4167#
#1.5 #02004C4F4F50002A0000243600000DA80087E01467F47BB2#1215086031819#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52599#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005311]###b2d4d63048e011ddc10602004c4f4f50#Thread[Managed_Application_Thread_14,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_buffer size is: {0}#1#4167#
#1.5 #02004C4F4F50002A0000243700000DA80087E01467F47BB2#1215086031819#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52599#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005311]###b2d4d63048e011ddc10602004c4f4f50#Thread[Managed_Application_Thread_14,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###PacketImpl.checkUnderflow(). Try to read  {0},  bytes from position: {1}#2#1#4167#
#1.5 #02004C4F4F50002A0000243800000DA80087E01467F47BB2#1215086031819#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52599#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005311]###b2d4d63048e011ddc10602004c4f4f50#Thread[Managed_Application_Thread_14,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_start position is: {0}. m_position is: {1}. Payload start is: {2}. The messsage size is: {3} #4#0#4167#14#4167#
#1.5 #02004C4F4F50002A0000243900000DA80087E01467F47BB2#1215086031819#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52599#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005311]###b2d4d63048e011ddc10602004c4f4f50#Thread[Managed_Application_Thread_14,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_buffer size is: {0}#1#4167#
#1.5 #02004C4F4F50003000001F7C00000DA80087E01467F3A4DA#1215086032022#/System/Server#amt-sybex.com/dts-core-sda#com.sap.engine.services.ts#Guest#52580#SAP J2EE Engine JTA Transaction : [03a5bffffffa60052fffffffe]###c3bc13a048e011dd8a2b02004c4f4f50#Thread[Managed_Application_Thread_16,5,Managed_Application_Thread]##0#0#Error#1#com.sap.engine.services.ts#Java#ts_0003#com.sap.engine.services.ts.exceptions.TSResourceBundle#Status of ( {0} ) should be active, but it is {1}.#2#SAP J2EE Engine JTA Transaction : [03a5bffffffa60052fffffffe]#STATUS_MARKED_ROLLBACK = 1#
#1.5 #02004C4F4F50003000001F8100000DA80087E01467F3A4DA#1215086032022#/System/Server##com.sap.jms.resourceadapter.RaServerSession#Guest#52580#SAP J2EE Engine JTA Transaction : [03a5bffffffa60052fffffffe]###c3bc13a048e011dd8a2b02004c4f4f50#Thread[Managed_Application_Thread_16,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms#Plain###Application exception happened while invoking onMessage() method. It was caught and suppressed in the ServerSession. For more details see the trace file#
#1.5 #02004C4F4F50002E000022B200000DA80087E01467F4A6AA#1215086032038#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52600#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005312]###b845338048e011ddb94c02004c4f4f50#Thread[Managed_Application_Thread_15,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###PacketImpl.checkUnderflow(). Try to read  {0},  bytes from position: {1}#2#1#14730#
#1.5 #02004C4F4F50002E000022B300000DA80087E01467F4A6AA#1215086032038#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52600#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005312]###b845338048e011ddb94c02004c4f4f50#Thread[Managed_Application_Thread_15,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_start position is: {0}. m_position is: {1}. Payload start is: {2}. The messsage size is: {3} #4#0#14730#14#14730#
#1.5 #02004C4F4F50002E000022B400000DA80087E01467F4A6AA#1215086032038#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52600#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005312]###b845338048e011ddb94c02004c4f4f50#Thread[Managed_Application_Thread_15,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_buffer size is: {0}#1#14730#
#1.5 #02004C4F4F50002E000022B500000DA80087E01467F4A6AA#1215086032038#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52600#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005312]###b845338048e011ddb94c02004c4f4f50#Thread[Managed_Application_Thread_15,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###PacketImpl.checkUnderflow(). Try to read  {0},  bytes from position: {1}#2#1#14730#
#1.5 #02004C4F4F50002E000022B600000DA80087E01467F4A6AA#1215086032038#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52600#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005312]###b845338048e011ddb94c02004c4f4f50#Thread[Managed_Application_Thread_15,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_start position is: {0}. m_position is: {1}. Payload start is: {2}. The messsage size is: {3} #4#0#14730#14#14730#
#1.5 #02004C4F4F50002E000022B700000DA80087E01467F4A6AA#1215086032038#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52600#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005312]###b845338048e011ddb94c02004c4f4f50#Thread[Managed_Application_Thread_15,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_buffer size is: {0}#1#14730#
#1.5 #02004C4F4F50003000001F8200000DA80087E01467F4C5EA#1215086032288#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52601#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005313]###c3bc13a048e011dd8a2b02004c4f4f50#Thread[Managed_Application_Thread_16,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###PacketImpl.checkUnderflow(). Try to read  {0},  bytes from position: {1}#2#1#5240#
#1.5 #02004C4F4F50003000001F8300000DA80087E01467F4C5EA#1215086032288#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52601#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005313]###c3bc13a048e011dd8a2b02004c4f4f50#Thread[Managed_Application_Thread_16,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_start position is: {0}. m_position is: {1}. Payload start is: {2}. The messsage size is: {3} #4#0#5240#14#5240#
#1.5 #02004C4F4F50003000001F8400000DA80087E01467F4C5EA#1215086032288#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52601#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005313]###c3bc13a048e011dd8a2b02004c4f4f50#Thread[Managed_Application_Thread_16,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_buffer size is: {0}#1#5240#
#1.5 #02004C4F4F50003000001F8500000DA80087E01467F4C5EA#1215086032288#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52601#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005313]###c3bc13a048e011dd8a2b02004c4f4f50#Thread[Managed_Application_Thread_16,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###PacketImpl.checkUnderflow(). Try to read  {0},  bytes from position: {1}#2#1#5240#
#1.5 #02004C4F4F50003000001F8600000DA80087E01467F4C5EA#1215086032288#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52601#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005313]###c3bc13a048e011dd8a2b02004c4f4f50#Thread[Managed_Application_Thread_16,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_start position is: {0}. m_position is: {1}. Payload start is: {2}. The messsage size is: {3} #4#0#5240#14#5240#
#1.5 #02004C4F4F50003000001F8700000DA80087E01467F4C5EA#1215086032288#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52601#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005313]###c3bc13a048e011dd8a2b02004c4f4f50#Thread[Managed_Application_Thread_16,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###m_buffer size is: {0}#1#5240#
#1.5 #02004C4F4F50003200001CAA00000DA80087E01467F4D58A#1215086032366#/System/Server#amt-sybex.com/dts-core-sda#com.sap.jms.protocol.PacketImpl#Guest#52602#SAP J2EE Engine JTA Transaction : [03a5bffffffa6005314]###d3f7ced048e011dd99b802004c4f4f50#Thread[Managed_Application_Thread_19,5,Managed_Application_Thread]##0#0#Error#1#com.sap.jms.protocol#Java###PacketImpl.checkUnderflow(). Try to read  {0},  bytes from position: {1}#2#1#1230#

Vlado
Advisor
Advisor
0 Kudos

Hi Gerry,

I'd suggest to open a CSS ticket as we'd probably need to debug into this and SDN is not so convenient for that purposes (e.g. it's not possible to attach full trace files, establish a connection, etc.).

We should update the thread after the issue has been resolved.

Thanks and regards,

\-- Vladimir

Former Member
0 Kudos

Hi Vladimir,

There is already a ticket open (0020079747 0000551297 2008) related to this issue.

This is also a ticket open for being unable to create an XAQueueConnection factory (0120025231 0000511712 2008).

Thanks,

Gerry