Getting Ready › Release Notes › Known Issues and Important Notes › Known Issues and Limitations › CA AppLogic Limitations

CA AppLogic Limitations

1. The included HalSign TurboGate PV Drivers v3.0.1 does not install on Windows 8 32-bit. It does install correctly on Windows 8 64-bit.
2. Sample applications from older releases will fail to start on a 3.8 grid due to new resource requirements for appliances in the system and dynamic catalogs (due to these appliances being re-based on CentOS 6.3). Please use the updated sample applications provided with the 3.8 release (the data volumes from the older sample applications can be migrated over to an instance of the newer sample applications).
3. Grid size is limited to 128 servers per grid for Xen.
   This is a limitation of the current CA AppLogic release. This release has been certified up to 60 servers; however configurations up to 128 (for Xen) are supported.
4. CA AppLogic cannot be installed on servers with 3 TB or larger drives.
5. For proper operation of the user interface, enable JavaScript, pop-ups, and cookies for the grid controller host. Ensure your browser is updated with the latest available version to correct defects that affect AJAX applications.
6. Protocols are not enforced on appliance terminals, only endpoints are enforced.

   This means that an appliance can only talk to appliances connected to it (plus its own server and the grid controller). Nevertheless, protocols on new appliances should be properly specified to help ensure application design integrity and compatibility with future versions of CA AppLogic.

7. The total available disk space does not take volume mirroring into account.

   The total available disk space reported by the grid info command is a raw estimate and does not take volume mirroring into account. The true available disk space is the reported available amount divided by the number of mirrors (2 mirrors by default).

   For example, if there is 1000GB of available disk space and the grid was configured for mirroring of 2, the available disk space is 500GB. Also, to successfully mirror volumes, there must be enough disk space on at least X servers (where X is the number of mirrors). CA AppLogic creates a volume even if one of its mirrors cannot be created (in this case, it displays a warning that the volume could not be mirrored).

8. A server failure during application start may cause the application start to fail.

   If an application is started and one of the grid's servers fails, the application start fails if one or more of the application's appliances were scheduled to run on the failed server. If this situation occurs, restart the application.

9. The volume management GUI available using the filers has an upload limitation of 10MB per file.

   To upload larger files to your volume, use the vol manage shell command. You must specify the external IP settings for this command to enable remote access from within the volume manager. For more information, see the vol manage command documentation.

10. The property markup for appliance configuration is only supported for the volfix configuration mode.

    The dhcp configuration mode does not support the property markup for appliance configuration. When porting appliances from volfix to dhcp configuration modes, the APK documentation describes how to deal with appliances that depend upon the property markup for appliance configuration. See the Appliance Kit (APK) for more information.

11. Validation flags do not appear if the application is opened in read-only mode.

    To see the validation flags for an application, open the application in edit mode. The validation flags are used to flag appliances that do not have all of their mandatory properties, terminals, and volumes properly configured.

12. The graphical console cannot be used with appliances that are distributed with CA AppLogic that are missing their GUI, desktop packages, and support (X11, Gnome Desktop, and so on). This is done to make the appliances as compact as possible. Use the iso2class utility to create appliances with full desktop support.
13. Running more than one Windows application with appliances having the same instance name results in a Duplicate Computer Name error from Windows.

    This error appears because CA AppLogic sets the computer name of an appliance to its instance name. If you have multiple appliances running on a grid that have the same instance names, the duplicate name error appears in Windows on the graphical console. This error is a warning and does not affect the grid or its operation. However, if you need to use Windows as a domain controller, you need to set the computer names to unique names for each appliance. You can use the wincfg utility to set the computer name in your appliance.

14. The graphical console requires the latest version of Java in your browser.

    If the latest version of Java is not used, the graphical console can hang while trying to load. Verify that you are using the latest Java version. If not, upgrade Java in your browser, then re-open your browser for the graphical console to work correctly.

15. Failover groups may not be satisfied upon controller recovery.

    When a secondary server takes over as the new primary server, if there are not enough resources available on the server to start the grid controller, CA AppLogic restarts appliances that are running on the new primary server on other servers within the grid so the grid controller can be started on the new primary server. Note that this may break appliance failover groups. If CA AppLogic stops one of these appliances it may not be able to restart the appliance on another server because there may not be enough resources to satisfy the failover group.

16. Xen-HVM-based appliances use more memory than their configured amount.

    All HVM-based appliances (Windows for example) use more memory on the server than what they are configured to use. Depending on the amount of memory assigned to an HVM-based appliance, the appliance uses additional memory on the server in which it is running (this additional memory is required by the virtualization hypervisor running on the servers and is known as shadow memory). Therefore, it is possible that a server might have enough available memory compared to what is assigned for the appliance, the appliance is not able to run on that server due to the additional shadow memory needed for HVM-based appliances that is not available on the server. The CA AppLogic scheduler does take this extra shadow memory into account when scheduling appliances during application start.

17. Internet Explorer cannot be used to access the graphical console of an appliance that is based on Ubuntu.

    Any other supported browser can be used.

18. The shared interface support in CA AppLogic 3.x does not work on Windows-based appliances.

    Shared interfaces work with all other supported operating systems.

19. If any server on a grid has greater than 4 TB of local storage, the dom0 memory for the entire grid must be set to 1 GB. This is specified through the BFC using the parameter dom0_vm_mb=1024 when you install the grid.