WebSphere Commerce ReleasetoFulfillment job creates
unnecessary objects in memory
|
|
Technote (troubleshooting)
| | Problem(Abstract)
| Your WebSphere Commerce ReleasetoFulfillment job creates
unnecessary objects in memory, and this causes unnecessary peaks in memory
usage. You can see evidence of these peaks by analyzing verbose garbage
collection logs. In extreme cases, these peaks can result in OutOfMemory
errors.
This issue is only relevant when the WebSphere Commerce store uses
ATP-inventory.
|
|
|
|
| Cause
|
| The original SQL that is used in the ReleasetoFulfillment
job to search for orders includes the 'R' (Released) and 'S' (Shipped)
order states. This search is too broad and does not limit the result set
to what is required. For each order in the result set, a bean is created
in memory, regardless of whether the bean is required, and this causes an
unnecessary peak in memory usage.
|
|
|
| Resolving the
problem
|
| This problem (APAR JR27374) is resolved in Fix Pack
6.0.0.4 or newer. You can obtain the Fix Pack from the Fixes
by version page. The fix uses an improved SQL that does not include
the 'R' (Released) and 'S' (Shipped) order states.
|
| |
| Segment
| Product
| Component
| Platform
| Version
| Edition
|
| Commerce
| WebSphere Commerce Professional Edition
| Performance
| AIX, i5/OS, Linux, Solaris, Windows
| 6.0, 6.0.0.1, 6.0.0.2, 6.0.0.3
| Professional Edition
|
| Commerce
| WebSphere Commerce - Express
| Performance
| AIX, i5/OS, Linux, Solaris, Windows
| 6.0, 6.0.0.1, 6.0.0.2, 6.0.0.3
| Express
|
|
Current web document: http://www.ibm.com/support/docview.wss?uid=swg21296570
|