Resolution:

When user tries to view the deployed module, the console will use JDK to unzip the deployed module. If the deployed module is huge, there may not be enough memory for JDK to unzip the module. Thus the Java OutOfMemory error will be thrown.

Here are some alternatives to avoid the error.

1. User can increase the heap size by changing the setting of vmparam in <AppServer install>/bin/console.config file.

2. User can run management console on Windows machine as Window's JDK is more stable.

3. Alternatively user can use Deployment Descriptor Editor to view the deployed module and deploy using iastool or Borland AppServer Deployment Wizard. When using Deployment Descriptor Editor, another VM will be created with its own memory space. User can start Deployment Descriptor Editor either from <AppServer install>/bin directory or from "Tools" tab of management console menu.

For deployment, user can:

A. Use iastool. To find out how to use iastool, please type "iastool -usage deploy" in <AppServer install>/bin directory.

B. Or start the deployment tool under Wizards menu in Borland Management Console.

1. Open Borland Management Console, click Wizards in the menu bar. Select Partition Deployment Wizard and click.
2. A Borland AppServer Deployment Wizard window will pop up. Click Add button to add the file you want to deploy.