Remote debugging (CR #344244) To use remote debugging, the file pbjag80.sl must exist in the EAServer lib subdirectory as a symbolic link to libpbjag80x.sl. On some machines, the installer may create pbjag80.sl as a regular file or not install it at all. If pbjag80.sl is a regular file, remove it. Create pbjag80.sl as a symbolic link to libpbjag80x.sl. For example:
ln -s libpbjag80x.sl pbjag80.sl
(CR #341947) For remote debugging, you cannot use a port number larger than 32767 to access EAServer.
Multiple PBVM versions (CR #380753) When one PBVM version is loaded, you cannot use another PBVM version. For example, when a PowerBuilder 8.0.4 (server-side) component is called by a PowerBuilder client, the 8.0.4 PBVM is loaded on the server side. Then, if you attempt to call a PowerBuilder 9.0.1 component deployed on EAServer, an error occurs. The same problem occurs if the 9.0.1 PBVM is loaded before calling an 8.0.4 component. To avoid this problem, install only one version of the PBVM on EAServer.
(CR #386852) If you install EAServer using the silent installer, both versions of the PBVM are installed, regardless of how you configure the EASPowerBuilderv8Support.active and EASPowerBuilderv9SupportHP.active properties in SilentInstall_Unix.txt. See the description of CR #380753, above.
Version 8.0.4 and multiple component instances (CR #384703) Using PowerBuilder 8.0.4, if you create 10 or more instances of a client-side component, then click Start Loop on the opened instance windows one by one, the application may crash.
