000014691 - FIM configuration console does not load after deployment.

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000014691
Applies ToFederated Identity Management Module (FIM) 4.x
IssueFIM configuration console does not load after deployment.

The following error shows in the standard output of the FIM managed server.

(It may be also logged at C:\bea\user_projects\domains\base_domain\servers\FIM\log\FIM.out if the server is started from the WebLogic Administrative Console.)

SEVERE: Dispatch[/Dashboard] to method nvPreView returned an exception
java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

....Caused by: java.lang.ExceptionInInitializerError
     at com.rsa.fim.admin.target.EJBCommandTarget.execute(EJBCommandTarget.java:45)
     at com.rsa.fim.admin.Command.execute(Command.java:242)
     at com.rsa.fim.ui.handler.DashboardHandler.executeFetch(DashboardHandler.java:32)
     at com.rsa.fim.ui.action.home.DashboardAction.nvPreView(DashboardAction.java:45)
     ... 53 more
Caused by: com.rsa.fim.exception.util.ServiceLocatorException: Cannot instantiate Service Locatornull
     at com.rsa.fim.util.ServiceLocator.<clinit>(ServiceLocator.java:50)
     ... 57 more

CauseThe first exception in the error message is misleading.  The "ServiceLocatorException" located at the end of the stack trace defines the real problem.  In this instance FIM cannot find the class specified because of a problem with the JMX service.  The first exception thrown is in the first abitrary class that is unreachable. 
Resolution

This error will occur if the server listen address and listen port are not exactly the same as that defined in the fim.properties file.  Refer to page 61 in the FIM installation guide:

To configure a non-default port number:
1. Open the file FIM-domain-directory/rsa-fim-config/properties/fim.properties
in a text editor.
2. Find the following lines:

jndi.url=t3://localhost:7001

jndi.ssl.url=t3s://localhost:7002

3. Make the following changes:

?
Replace 7001 with the number you specified for the listening port. To view the port numbers you assigned , click Environment > Servers in the WebLogic Administration Console.
?
Replace 7002 with the number you specified for the SSL listening port.

Notes

Check to see what server name and port the JMX service is running on.  Look in the weblogic log file for the following line:

<JMX Connector Server started at service:jmx:iiop://10.14.97.114:7001/jndi/weblogic.management.mbeanservers.runtime

Ensure that the server name and port match exactly to what is defined in your weblogic console for the listen port and server and what is defined for the JMX URL in the fim.properties file


Note that this error message may occur if any failure prevents the FIM server from communication over JMX. See the following related solutions:

NMSV0602E: Naming Service unavailable. A communications error occurred.NMSV0602E: Naming Service unavailable. A communications error occurred.

Unknown System Error in FIM consoleUnknown System Error in FIM console

FIM 4.0 clustered deployment throws ServiceLocatorExceptionFIM 4.0 clustered deployment throws ServiceLocatorException

FIM is unable to replicate the cache between multiple FIM instances in a clustered deployment.FIM is unable to replicate the cache between multiple FIM instances in a clustered deployment.

Legacy Article IDa46795

Attachments

    Outcomes