It is recommended that you suppress FullGC occurrence when you execute various stop commands and the start command of the business process and the service adapter.

When you replace HCSC components by stopping online, you can suppress the frequency of FullGC occurrence by specifying the -nogc option in each operating command as shown in the following procedure example:

1. Stop reception
   

   cscrcptnstop -csc <HCSC server name> -nogc

2. Stopping business processes and service adapters
   

   csccompostop -csc <HCSC server name> -name <serviceID> -nogc

3. Deleting business processes and service adapters
   

   csccompoundeploy -csc <HCSC server name> -name <serviceID> -nogc

4. Importing repositories
   

   cscrepctl -import <repositoryZIP>

5. Deploying business processes and service adapters
   

   csccompodeploy -csc <HCSC server name> -all

6. Starting business processes and service adapters
   

   csccompostart -csc <HCSC server name> -all -nogc

7. Start reception
   

   cscrcptnstart -csc <HCSC server name> -nogc

   If you do not specify the -nogc option with this command, FullGC occurs once at each of the point in time mentioned below.FullGC does not occur at any other time.
   
   • At the time of starting the standard reception immediately after the HCSC server set up
   • At the time of starting the user-defined reception immediately after executing the csccompodeploy command
8. Explicit issue of FullGC (optional)
   

   javagc -p <process ID of J2EE server>

   The FullGC issue before the online start shown in this operation is not mandatory, but if you want to explicitly issue FullGC, use the javagc command
   For details on the javagc command, see "10. Commands Used in JavaVM" in "Application Server Command Reference Guide".
   

Because FullGC occurrence is suppressed in steps 1.~3., steps 6.~7., FullGC occurs only once in step 8. within the entire procedure in this example.