One of my customers has recently migrated to WAS v8 and they went with base version [v8.0.0.3].

They tried executing thier deployment automation scripts which were working on v7 and v6. However the scripts didn't execute on WAS8.

Now, if we run the script, it is going out of memory whatever the Xmx size you specify.

So that first modification recommended was to change the XMX at set "PERFJAVAOPTION=" in wsadmin.bat file.

After the modification, it was found that the wsasmin is taking 2 XMX values.  And last XMX value is considered for max heap

2CIUSERARG -Xms256M

2CIUSERARG -Xmx1024M

2CIUSERARG -Xmx256M

Any suggestions for resolving this issue are highly appriciated.

Hi Joseph,

  have you done an echo of PERFJAVAOPTION before execute the comand?
 
  have you checked setupCmdLine script? have you put directly Xmx in the comand avoiding the PERFJAVAOPTION variable?
 
  if you a having two Xmx arguments, in my opinion another variable is establishing one of both.
 
  Checking fixpacks (8.0.0.4) not seems a bug.
 
  Tell me if I can help with any test
 
regards,

Hi Gabriel,

Looking at the possibility of the second XMX being picked up from the WS_ANT .
Will update you, if we make any progress