Issue with internal JMS queue

[Former Member]

Hi,

We discovered following issue with Netweaver version:

SAP EP 6.0 ON WEB AS 6.20

J2EE version:

Cluster-Version: 6.40 PatchLevel 106831.313

Build-On:Thursday, October 26, 2006 18:56 GMT

Perforce-Server:

Project-Dir:JKernel/630_VAL_REL

JKernel Change-List:106831

Build machine:SAPInternal

Build java version:1.3.1_18-b01 Sun Microsystems Inc.

SP-Number: 19

Source-Dir: D:\make\engine\630_VAL_REL\builds\JKernel\630_VAL_REL\archive\dbg

During sending messages into internal JMS queue we sent messages bigger than 1MB. After that, JMS queue was not able to process any other messages even if it was smaller than 1MB. Same issue occured if there was more smaller messages sent in short time (e.g. in 2 seconds). We don't have any significant error message in any log.

:

See information thath we have found in dump stack trace file (ix.log):

"SAPEngine_Application_Thread[impl:3]_25" prio=5 tid=0x0000000101f5ebf0 nid=0x37 in Object.wait() [fffffffe0bdfd000..fffffffe0bdff8b0]
 at java.lang.Object.wait(Native Method)
 - waiting on <0xfffffffe2ebfa1b8> (a java.lang.Object)
 at java.lang.Object.wait(Object.java:429)
 at com.sap.jms.client.memory.MemoryManager.allocate(MemoryManager.java:132)
 - locked <0xfffffffe2ebfa1b8> (a java.lang.Object)
 at com.sap.jms.client.memory.MemoryManager.allocateMemoryForBigMessage(MemoryManager.java:92)
 - locked <0xfffffffe2ebfa1b8> (a java.lang.Object)
 at com.sap.jms.client.session.Session.processFinalMessage(Session.java:1732)
 at com.sap.jms.client.session.Session.run(Session.java:675)
 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:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

which indicates to us that initializing of memory is locked.

Please let us know:

-if there is any log which indicates this behaviour without making thread dump

-which limits must be fulfilled to process messages without this error

-how to unblock this lock for processing correct messages without restarting NW - or if there is any predefined timout which kill this locked session and disable uncorrect message

-how to manage records in bc_jmsqueue table for removing big messages from queue if there were loaded already

-how to stop application which caused this problem. If we try to stop it through standard stop_App, application stays in Stopping mode forever.

This problem occured in test environment and also in productive environment using the same SAP NW. Now - we do not have any work around solution..... therefore periodically we need to restart SAP NW....

Thx for any suggestions.....

[Former Member]

Hi,

We are also facing the same problem of restarting the SAP NW each time, if you have found the solution, please let me know.

Thx in advance.

Ramanath