Common issues with extended functions

Common issues with class loaders, servlet proxies, and custom connectors can be resolved by activating or customizing the platform logs.

To start platform logging

In the administrator console, in the Platform Logging managed object, turn on debugging for the Class Loader and Servlet Proxy categories. These verbose-mode logs can give you a good understanding of what the server is doing.

For information about how to access and use the administrator console, see the IBM TRIRIGA Application Platform: Administrator Console User Guide.

To simplify the debugging of class loaders and servlet proxies

In the administrator console, to add a custom category to the Platform Logging managed object, add the custom category to the CustomLogCategories.xml file and restart the server. The CustomLogCategories.xml file is in the InstallationDirectory/config folder.

This method is preferred because you set it up one time. If the server is restarted, you can turn DEBUG back on by selecting the option for your custom category.

The .jar files do not deploy as expected

Do not add multiple instances of the same .jar file to a ClassLoader record. For example, one that is added directly and one that is contained within a compressed file. When this occurs, the instance of the .jar file that is loaded is not predictable.