Last updated on DECEMBER 03, 2014
Applies to:Oracle SOA Suite - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
During load testing in B2B, a new JMS connection was being created for each inbound message being processed in B2B. This lead to memory leak issue due to high volume of messages being processed.
There is a functionality which caches JMS Sessions when B2B server property b2b.useJMSDataSourceCache is set to true. This results in performance improvement. When this property is set to false (which is the default value), a new JMS connection is initiated. A flag: reset_jms (default value as false) was introduced by the caching fix.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms