NOM Leak in JMS connector 2.1.2

[GoogleCodeExporter]

What steps will reproduce the problem?
Unknown

What is the expected output? What do you see instead?
After some time the JMS container gives us: 

OutOfVirtualMemoryError in NOM. 
This happens when the operating system is unable to allocate - further memory 
for the process or the maximum size set for the NOM virtual memory is not 
enough 
for the process.
You may try to increase the maximum virtual memory size by changing the value 
of the  property - "bus.xml.vm.maxsize" - in Cordys Properties file, 
eg. "bus.xml.vm.maxsize=<SIZE_IN_MB>"

After analysis of NOM by JConsole we see a NOM leak, see KKV 
NOMLeakInfoAnonymized.txt

We cannot analyze why the NOM leak is happen.
Please, help.

What version of the product are you using? On what operating system?
JMS connector 2.1.2, see also AboutCordys.txt

Please provide any additional information below.
See attachments:
-KKV NOMLeakInfoAnonymized.txt (output JConsole / JMX getNOMLeakInfo)
-kkv_log.zip
-jmsconfig.txt
-ReceiveMessageExports.zip (Exports of BPM in JMS configuration)
-aboutcordys.txt

Original issue reported on code.google.com by wblijlev...@gmail.com on 29 Oct 2013 at 12:12

Attachments:

• jms_ticket.zip

[GoogleCodeExporter]

For us it is high prio.

Original comment by wblijlev...@gmail.com on 29 Oct 2013 at 1:12