cancel
Showing results for 
Search instead for 
Did you mean: 

MS Queue Worker : BLOCKED

Former Member
0 Kudos

Is there anyone who know why this happen? Appearing again and again, now it makes me feel sick...... see below :

"MS Queue Worker [JDBC_http://sap.com/xi/XI/SystemRqst]" cpu=471550.00 [reset 471550.00] ms allocated=36211481608 B (33.72 GB) [reset 36211481608 B (33.72 GB)] user="PIISUSER" prio=5 tid=0x0000000114a7cd90 nid=0x10c23 waiting for monitor entry [0x00000001230c8000..0x00000001230cbec8]
   java.lang.Thread.State: BLOCKED (on object monitor)
	at java.util.Hashtable.containsKey(Ljava/lang/Object;)Z(Hashtable.java:313)
	- waiting to lock <0x070000008a1d2088> (a java.util.Hashtable)
	at com.sap.engine.messaging.impl.core.service.Request.isMessageBlocked(Lcom/sap/engine/interfaces/messaging/api/MessageKey;)Z(Request.java:184)
	at com.sap.engine.messaging.impl.core.service.Send.execute()V(Send.java:78)
	at com.sap.engine.messaging.impl.spi.ServicesImpl.send(Lcom/sap/engine/interfaces/messaging/spi/TransportableMessage;)V(ServicesImpl.java:184)

Edited by: Mr.Hwang on Apr 21, 2010 4:04 AM

Accepted Solutions (1)

Accepted Solutions (1)

rajasekhar_reddy14
Active Contributor
0 Kudos

Hi.,

Are you working with larger messages, this error occurs when EXCEEDS DB size, contact your basis team they will help you.

Regards,

Raj

Answers (2)

Answers (2)

Former Member
0 Kudos

I increased visual admin's messaging.system.queueParallelism.maxReceivers property 0 to 2, and problem has cleared.

Thanks anyway!

Edited by: Mr.Hwang on Apr 26, 2010 4:32 AM

Former Member
0 Kudos

Can you have a look at SAP note 920979. We had similar issue & there were not enough resouces to set lock on processing messages. YOu need to encrease the value of avalaible enqueue lock which will solve the issue.

Regards

Sushil