11 Troubleshooting

This chapter provides information about the log files where the Oracle Role Manager Integration Library writes messages along with some error conditions and solutions.

This chapter contains the following topics:

• Log Files

• Oracle Role Manager Application Server Console Errors

• Oracle Identity Manager Application Server Console Errors

11.1 Log Files

The Integration Library messages are written to the server.log.* files in both the Oracle Role Manager application server and the Oracle Identity Manager application server.

Depending on the application server that you use, log information is written to the following files:

• For JBoss:

  JBOSS_HOME/server/default/log/server.log
  

• For IBM WebSphere:

  WEBSPHERE_HOME/AppServer/profiles/profile_name/logs/server_name/SystemOut.log
  

• For WebLogic Server:

  WEBLOGIC_HOME/user_projects/domains/domain_name/servers/server_name/server_name.log
  

11.2 Oracle Role Manager Application Server Console Errors

The following table describes error conditions that may appear in the application server console for Oracle Role Manager.

Problem Description	Solution
Returned Warning Message: WARN [OutgoingEventManagerImpl] Explicitly committed to a non-XA queue from within a transaction. Please check the configuration for the /oim/OIMserver/QueueConnectionFactory connection factory.	This can be ignored. This occurs when the application server on which Oracle Identity Manager is deployed is non-transactional, where Oracle Role Manager explicitly commits a transaction on initialization of the Oracle Role Manager connection factory to ensure messages are sent from Oracle Role Manager to Oracle Identity Manager.

11.3 Oracle Identity Manager Application Server Console Errors

The following table describes error conditions that may appear in the application server console for Oracle Identity Manager.

Problem Description	Solution
Returned Warning Message: WARN [IntegrationContext] General error utilizing plugin class	This can be ignored. It is caused by an intermittent race condition and causes no harm or loss of functionality.
Returned Error Message: WARN [IntegrationContext] Truncating the ORM Role Name when creating a shadowing OIM Group was xxxx. Truncated to yyyy.	This occurs when the integration detects that the Oracle Role Manager role name (including role prefix ORM_) would attempt to create a group whose name length was greater than thirty characters. In this case, the integration truncates the name to the Oracle Identity Manager user group name limit of thirty characters.
Returned Error Message: javax.naming.NameNotFoundException: While trying to lookup 'connection factory'.	This occurs when the JNDI names for the JMS connection factory and the local and remote foreign JNDI providers are different. Check your WebLogic configuration to ensure that the values for all three are identical.
Returned Error Message: SECJ0055E: Authentication failed for <null>. The user id or password may have been entered incorrectly or misspelled. The user id may not exist, the account could have expired or disabled. The password may have expired.	This can occur for a variety of reasons. Common occurrences related to the Integration Library are as follows: For WebSphere deployments, bus security is mismatched. For example, the role update bus on the Oracle Role Manager server has security disabled but the foreign role update bus on the Oracle Identity Manager server has security enabled. For WebSphere deployments, the steps regarding the xlDataObjectBeans.jar file during deployment of the Integration Library application were not correctly followed. (For instructions, refer to Section 8.5, "Deploying the Oracle Role Manager Integration Library Application on WebSphere.")