Intermittent Java Virtual Machine memory allocation errors *|* -C268102426D4370F85256F8800668AFC- *|*

The Java Virtual Machine values suggested in this technote where calculated for base Commerce installations.

If your site has been highly customized and you are using Java Development Kit 1.4.1 refer to technote 1176363.

Due to the intermittent nature of this problem it is recommended that all customers running WebSphere Commerce
releases 6.0 5.6.1 5.6 or 5.5 connecting to a DB2 database from a server running under AIX Windows or Linux complete the following steps:

If garbage collection tracing (verbosegc) has not been enabled then the Java Virtual Machine
can crash and restart periodically without any visible symptoms other than slow performance.
If verbosegc has been enabled the following errors can be found in the native_stderr.log file:

<AF[2082]: Allocation Failure. need 255768 bytes 7 ms since last AF>
<AF[2082]: managing allocation failure action=2 (62667808/536803840)>
<GC(2104): mark stack overflow[1902]>
<GC(2104): GC cycle started Fri Nov 19 21:48:04 2004
<GC(2104): freed 6116120 bytes 12% free (68783928/536803840) in 4117 ms>
<GC(2104): mark: 1719 ms sweep: 105 ms compact: 2293 ms>
<GC(2104): refs: soft 0 (age >= 32) weak 0 final 1 phantom 0>
<GC(2104): moved 2514995 objects 299673064 bytes reason=1 used 15808 more bytes>
<AF[2082]: managing allocation failure action=3 (68783928/536803840)>
<AF[2082]: managing allocation failure action=4 (68783928/536803840)>
<AF[2082]: managing allocation failure action=6 (68783928/536803840)>
<AF[2082]: totally out of heap space>
<AF[2082]: completed in 4129 ms>

<AF[2083]: Allocation Failure. need 32784 bytes 1817 ms since last AF>
<AF[2083]: managing allocation failure action=2 (28528/536803840)>
<GC(2105): mark stack overflow[1903]>
<GC(2105): GC cycle started Fri Nov 19 21:48:07 2004
<GC(2105): freed 67886448 bytes 12% free (67914976/536803840) in 1702 ms>
<GC(2105): mark: 1601 ms sweep: 101 ms compact: 0 ms>
<GC(2105): refs: soft 0 (age >= 32) weak 0 final 120 phantom 0>
<AF[2083]: completed in 1724 ms>

The Java Virtual Machine argument can be changed from the Administrative Console. To change the Java Virtual Machine argument from the Administrative Console:

1. Select Apserver > Apname > Process definitions > Java Virtual Machine.

2. Update the argument as shown in the following screen capture: