44.9 Troubleshooting Common Errors

This section describes tips for working around common errors.

44.9.1 Permgen Space Error

You might encounter the following error when you redeploy the identity applications:

11:32:20,194 ERROR [[PortalAggregator]] Servlet.service() for servlet
PortalAggregator threw exception java.lang.OutOfMemoryError: PermGen space 

To avoid this error, either:

  • Restart the Tomcat server.

or

  • Or, increase the PermSpace value by passing -XX:MaxPermSize to the Java virtual machine by means of JAVA_OPTS in the start-tomcat script, for example:

    -XX:MaxpermSize=128m

44.9.2 Email Notification Templates

If your email notification templates are displaying in a single language and not in the user’s default locale as you expect, check to see what notification template is selected. You can select a default template or a localized version of the template. When you select a localized template, the language of the localized template is used regardless of the user’s default language. When you select the default template (the template without a locale code), the email is in the user’s default language (if the default is a supported language).

44.9.3 Org Chart and Guest Access

If you encounter an error like this at runtime, then you must modify the service definitions in the User Application WAR:

error: "an error occurred Control instantiation of JUICE.OrgChartCtrl failed (Object doesn't support this property or method). Please contact your system administrator. Detailed information can be found in the console." when accessing the portlet in a browser.

44.9.4 Provisioning Notification

If the Notify Other Users of these Changes check box does not display on the following pages:

  • Edit Availability

  • My Proxy Assignments

  • My Delegate Assignments

  • Team Proxy Assignments

  • Team Delegate Assignments

  • Team Availability

Verify that Email Notification templates have been defined. You define them through the Administration > RBPM Provisioning and Security > Delegation and Proxy.

44.9.5 javax.naming.SizeLimitExceededException

If you encounter a javax.naming.SizeLimitExceededException when you use the Administration > Page Admin > Set As Default, you might have encountered a maximum size limit. You can modify this limit in the PortalGroupPageDefaults portlet settings in the portlet.xml as follows:

<portlet>
    <portlet-name>PortalGroupPageDefaults</portlet-name>
   <portlet-class>
com.novell.afw.portal.portlet.core.permission.PortalGroupPageDefaults
</portlet-class>
    <init-param>
      <name>MIN_CACHE_SIZE</name>
      <value>20</value>
    </init-param>
    <init-param>
      <name>MAX_CACHE_SIZE</name>
      <value>200</value>
    </init-param>
    <init-param>
      <name>PAC_MAX_RESULTS</name>
      <value>2000</value>
    </init-param>
    ...
</portlet>

If you have more than 200 groups and want to assign groups to the View permissions for the Page Admin tab, you also need to update the settings for the PortalUserGroupSelection portlet. Modify this limit in the portlet.xml as follows:

<portlet>
    <portlet-name>PortalUserGroupSelection</portlet-name>
   <portlet-class>
com.novell.afw.portal.portlet.core.permission.PortalUserGroupSelection
</portlet-class>
    <init-param>
      <name>MIN_CACHE_SIZE</name>
      <value>20</value>
    </init-param>
    <init-param>
      <name>MAX_CACHE_SIZE</name>
      <value>200</value>
    </init-param>
    <init-param>
      <name>PAC_MAX_RESULTS</name>
      <value>2000</value>
    </init-param>
    ...
</portlet>

Redeploy the identity applications after you make your changes.

44.9.6 Linux Open Files Error

If you run the User Application on Linux, you might encounter a Too Many Open Files Error.Linux allows 1024 open files for each process, but the identity applications often requires more. NetIQ suggests increasing the number of open files to 4096 to avoid the Too Many Open Files error.

Use the ulimit command to increase the number of open files. There are some restrictions on ulimit for non-root users. Here is an example of how you can use the ulimit command to increase the number of open files to 4096 for a non-root user:

  1. Log in as root.

  2. Edit the file /etc/security/limits.conf. Add an entry for the user named smith and allow nofile up to 4096:

    smith   hard    nofile    4096
  3. Log in as user smith and pass 4096 to the ulimit -n command. You can issue the command again with no argument to see the current value:

    smith@myhost:~> ulimit -n 4096
    smith@myhost:~> ulimit -n

You might want to specify ulimit in the user environment or the start-tomcat script so that the new value is always used.