|Applies To||Federated Identity Management Module (FIM) 4.x|
|Issue||FIM 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
....Caused by: java.lang.ExceptionInInitializerError
|Cause||The 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.|
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:
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 ID||a46795|