Symantec IGA

Expand all | Collapse all

IAM Application Failed to start up:The IAM FW Startup was not successful

Jump to Best Answer
  • 1.  IAM Application Failed to start up:The IAM FW Startup was not successful

    Posted 04-04-2018 01:01 PM

    Hello,

     

    We have IAM installed on a weblogic cluster. Few days back when we tried to rolling bounce , one of the JVM is failing to start up( JVM is coming up but the IAM application is failing to start up properly) but the application on the secondary JVM is just fine its failing on the primary JVM of the weblogic cluster.

     

    Below is the log snippet and attached the logs for more deatils

    IDMGR 12.5.13

     

    Log snippet: server.out

     

    AVA Memory arguments: -Xms4096m -Xmx4096m -XX:ReservedCodeCacheSize=50m -XX:MaxPermSize=256m
    .
    WLS Start Mode=Production
    .
    CLASSPATH=/cust/weblogic/middleware/wls10.3.5.0/server/lib/jsafeFIPS.jar::/cust/weblogic/middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/java/jdk1.6.0_27/lib/tools.jar:/cust/weblogic/middleware/wls10.3.5.0/server/lib/weblogic_sp.jar:/cust/weblogic/middleware/wls10.3.5.0/server/lib/weblogic.jar:/cust/weblogic/middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/cust/weblogic/middleware/wls10.3.5.0/server/lib/webservices.jar:/cust/weblogic/middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/cust/weblogic/middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/cust/weblogic/middleware/wls10.3.5.0/server/lib/xqrl.jar::/cust/weblogic/middleware/wls10.3.5.0/server/lib/ojdbc6.jar:/cust/weblogic/middleware/wls10.3.5.0/server/lib/sqljdbc.jar:/cust/weblogic/middleware/wls10.3.5.0/server/lib/derbyclient.jar:/cust/weblogic/middleware/wls10.3.5.0/server/lib/derbynet.jar:/cust/weblogic/middleware/wls10.3.5.0/server/lib/derby.jar
    .
    PATH=/cust/weblogic/middleware/wls10.3.5.0/server/bin:/cust/weblogic/middleware/modules/org.apache.ant_1.7.1/bin:/usr/java/jdk1.6.0_27/jre/bin:/usr/java/jdk1.6.0_27/bin:/cust/weblogic/middleware/wls10.3.5.0/server/bin:/cust/weblogic/middleware/modules/org.apache.ant_1.7.1/bin:/usr/java/jdk1.6.0_27/jre/bin:/usr/java/jdk1.6.0_27/bin:/cust/CA/webagent/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/opt/insight/r/bin:/root/bin
    .
    ***************************************************
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    ***************************************************
    starting weblogic with Java version:
    java version "1.6.0_27"
    Java(TM) SE Runtime Environment (build 1.6.0_27-b07)
    Java HotSpot(TM) 64-Bit Server VM (build 20.2-b06, mixed mode)
    Starting WLS with line:
    /usr/java/jdk1.6.0_27/bin/java -server -Xms4096m -Xmx4096m -XX:ReservedCodeCacheSize=50m -XX:MaxPermSize=256m -Dweblogic.Name=idm_prod_mgs1 -Djava.security.policy=/cust/weblogic/middleware/wls10.3.5.0/server/lib/weblogic.policy -Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory -Dweblogic.security.SSL.nojce=true -da -Dplatform.home=/cust/weblogic/middleware/wls10.3.5.0 -Dwls.home=/cust/weblogic/middleware/wls10.3.5.0/server -Dwli.home=/cust/weblogic/middleware/wls10.3.5.0/integration -Dweblogic.ext.dirs=/cust/weblogic/middleware/patch_wls1035/profiles/default/sysext_manifest_classpath weblogic.Server
    <Apr 3, 2018 8:04:36 PM PDT> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
    <Apr 3, 2018 8:04:36 PM PDT> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
    <Apr 3, 2018 8:04:36 PM PDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.2-b06 from Sun Microsystems Inc.>
    <Apr 3, 2018 8:04:37 PM PDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
    <Apr 3, 2018 8:04:39 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Apr 3, 2018 8:04:39 PM PDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Apr 3, 2018 8:04:39 PM PDT> <Notice> <Log Management> <BEA-170019> <The server log file /cust/weblogic/middleware/domains/idm_domain_prod/servers/idm_prod_mgs1/logs/idm_prod_mgs1.log is opened. All server side log events will be written to this file.>
    <Apr 3, 2018 8:04:44 PM PDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Apr 3, 2018 8:04:46 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <Apr 3, 2018 8:04:46 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Apr 3, 2018 8:05:56 PM PDT> <Warning> <JMS> <BEA-040456> <An entity of type "Queues" with name "iam_im AnalyticsNotificationQueue" in JMS module "iam_im imJMSModule" is not targeted. There is no sub-deployment with name "iam_im imJMSSubdeployment" in the configuration repository (config.xml), and so this entity will not exist anywhere in the domain.>
    20:06:18,217 WARN [ims.tmt.CreateDatabaseSchema] ****** Schema for: Workpoint is up to date.
    20:06:18,338 INFO [com.workpoint.client.ClientContext] Loaded client properties from file:/cust/weblogic/middleware/domains/idm_domain_prod/servers/idm_prod_mgs1/stage/iam_im/iam_im.ear/config/workpoint-client.properties
    20:06:20,068 WARN [org.apache.myfaces.shared_impl.util.LocaleUtils] Locale name in faces-config.xml null or empty, setting locale to default locale : en_US
    20:06:20,548 WARN [ims.default] CA IAM Framework Server
    20:06:20,548 WARN [ims.default] Copyright 2000 - 2010 CA. All Rights Reserved
    20:06:20,553 WARN [ims.default] ################################################
    20:06:20,553 WARN [ims.default] # IAM Framework 200.0.0.0.916
    20:06:20,553 WARN [ims.default] ################################################
    20:06:20,553 WARN [ims.default] ################################################
    20:06:20,553 WARN [ims.default] # CA Identity Manager 12.5.13.0.944
    20:06:20,553 WARN [ims.default] ################################################
    20:06:20,553 WARN [ims.default] ---- CA IAM FW Startup Sequence Initiated. ----
    20:06:20,553 WARN [ims.default] * Startup Step 1 : Attempting to start ServiceLocator.
    20:06:21,157 WARN [ims.tmt.CreateDatabaseSchema] ****** Schema for: Task Persistence is up to date.
    20:06:21,167 WARN [ims.tmt.CreateDatabaseSchema] ****** Schema for: Archive is up to date.
    20:06:25,809 WARN [ims.tmt.CreateDatabaseSchema] ****** Schema for: Auditing is up to date.
    20:06:25,910 WARN [ims.tmt.CreateDatabaseSchema] ****** Schema for: Report Snapshot is up to date.
    20:06:25,912 WARN [ims.default] * Startup Step 2 : Attempting to start PolicyServerService
    20:06:25,913 WARN [ims.default] Unlimited Strength Java Crypto Extensions enabled: TRUE
    20:06:25,924 WARN [ims.default] Policy Server connection enabled: true
    20:06:25,930 WARN [ims.default] * Startup Step 3 : Attempting to start ServerCommandService
    20:06:25,965 WARN [ims.default] * Startup Step 4 : Attempting to start EnvironmentService
    20:06:25,970 WARN [ims.default] * Startup Step 5 : Attempting to start CacheManagerService
    20:06:25,978 WARN [ims.default] * Startup Step 6 : Attempting to load global plugins.
    20:06:28,015 WARN [ims.default] * Startup Step 7 : Attempting to start AdaptersConfigService
    20:06:28,018 WARN [ims.default] * Startup Step 8 : Attempting to start EmailProviderService
    20:06:28,028 WARN [ims.default] * Startup Step 9 : Attempting to start AuditProviderService
    20:06:28,036 WARN [ims.default] * Startup Step 10 : Attempting to start RuntimeStatusDetailService
    20:06:28,045 WARN [ims.default] * Startup Step 11 : Attempting to start PasswordService
    20:06:28,045 WARN [ims.default] * Startup Step 12 : Attempting to start LogicalAttributeService
    20:06:28,047 WARN [ims.default] * Startup Step 13 : Attempting to start BLTHService
    20:06:28,047 WARN [ims.default] * Startup Step 14 : Attempting to start ParticipantResolverService
    20:06:28,048 WARN [ims.default] * Startup Step 15 : Attempting to start NotificationRuleService
    20:06:28,051 WARN [ims.default] * Startup Step 16 : Attempting to start EventAdapterService
    20:06:28,051 WARN [ims.default] * Startup Step 17 : Attempting to start TaskService
    20:06:28,058 WARN [ims.default] * Startup Step 18 : Attempting to start WorkflowCallbackService
    20:06:28,064 WARN [ims.default] * Startup Step 19 : Attempting to start WorkflowService
    20:06:28,070 WARN [ims.default] * Startup Step 20 : Attempting to start EventService
    20:06:28,105 WARN [ims.default] * Startup Step 21 : Attempting to start AdminService
    20:06:28,106 WARN [ims.default] * Startup Step 22 : Attempting to start GeneralMonitorAdmin
    20:06:28,107 WARN [ims.default] * Startup Step 23 : Attempting to start GlobalInitializer plug-ins
    20:06:28,109 WARN [ims.default] * Startup Step 24 : Attempting to start environments
    20:06:30,043 WARN [ims.jdbc.JDBCSchema] Column dirMaxPages in table IM_DIRECTORY should have type INTEGER but has type NUMBER(0)
    20:06:30,043 WARN [ims.jdbc.JDBCSchema] Column dirMaxRows in table IM_DIRECTORY should have type INTEGER but has type NUMBER(0)
    20:06:30,043 WARN [ims.jdbc.JDBCSchema] Column dirTimeout in table IM_DIRECTORY should have type INTEGER but has type NUMBER(0)
    20:06:30,043 WARN [ims.jdbc.JDBCSchema] Column directoryConnection in table IM_DIRECTORY should have type INTEGER but has type NUMBER(0)
    20:06:30,606 WARN [ims.jdbc.JDBCSchema] Column managedObjectType in table IM_MOBJ_DEF should have type INTEGER but has type NUMBER(0)
    20:06:30,999 WARN [ims.jdbc.JDBCSchema] Column screenType in table IM_SCREEN_DEFINITION should have type INTEGER but has type NUMBER(0)
    20:06:31,125 WARN [ims.jdbc.JDBCSchema] Column rowOrder in table IM_TAB should have type INTEGER but has type NUMBER(0)
    20:06:32,676 WARN [ims.jdbc.JDBCSchema] Column maxLength in table IM_MOBJ_ATTR_DEF should have type INTEGER but has type NUMBER(0)
    20:06:36,477 WARN [ims.jdbc.JDBCSchema] Column rowOrder in table IM_SCREEN_FIELD should have type INTEGER but has type NUMBER(0)
    20:06:36,494 WARN [ims.jdbc.JDBCSchema] Column type in table IM_ROLE should have type INTEGER but has type NUMBER(0)
    20:06:37,122 WARN [ims.jdbc.JDBCSchema] Column actiontype in table IM_TASK should have type INTEGER but has type NUMBER(0)
    20:06:37,122 WARN [ims.jdbc.JDBCSchema] Column managedObjectType in table IM_TASK should have type INTEGER but has type NUMBER(0)
    20:06:37,122 WARN [ims.jdbc.JDBCSchema] Column priority in table IM_TASK should have type INTEGER but has type NUMBER(0)
    20:06:37,122 WARN [ims.jdbc.JDBCSchema] Column CategoryOrder in table IM_TASK should have type INTEGER but has type NUMBER(0)
    20:06:37,122 WARN [ims.jdbc.JDBCSchema] Column Category2Order in table IM_TASK should have type INTEGER but has type NUMBER(0)
    20:06:37,122 WARN [ims.jdbc.JDBCSchema] Column Category3Order in table IM_TASK should have type INTEGER but has type NUMBER(0)
    20:06:37,122 WARN [ims.jdbc.JDBCSchema] Column taskOrder in table IM_TASK should have type INTEGER but has type NUMBER(0)
    20:06:37,122 WARN [ims.jdbc.JDBCSchema] Column type in table IM_TASK should have type INTEGER but has type NUMBER(0)
    20:06:38,378 WARN [ims.jdbc.JDBCSchema] Column sortOrder in table IM_TASK_HANDLER should have type INTEGER but has type NUMBER(0)
    20:06:38,378 WARN [ims.jdbc.JDBCSchema] Column valRuleType in table IM_TASK_HANDLER should have type INTEGER but has type NUMBER(0)
    20:06:40,133 WARN [ims.jdbc.JDBCSchema] Column identitypolicysubtype in table IM_IDENTITY_POLICY should have type INTEGER but has type NUMBER(0)
    20:06:40,523 WARN [ims.jdbc.JDBCSchema] Column valSourceType in table IM_VALIDATION_RULE should have type INTEGER but has type NUMBER(0)
    20:06:40,807 WARN [ims.jdbc.JDBCSchema] Column validationruleoid in table IM_VALIDATION_SET_RULE should have type INTEGER but has type NUMBER(0)
    20:06:40,807 WARN [ims.jdbc.JDBCSchema] Column validationrulesetoid in table IM_VALIDATION_SET_RULE should have type INTEGER but has type NUMBER(0)
    20:06:41,182 WARN [ims.jdbc.JDBCSchema] Column minLength in table FWPASSWORDPOLICY should have type INTEGER but has type NUMBER(0)
    20:06:41,182 WARN [ims.jdbc.JDBCSchema] Column maxLength in table FWPASSWORDPOLICY should have type INTEGER but has type NUMBER(0)
    20:06:41,182 WARN [ims.jdbc.JDBCSchema] Column maxRepeatingChar in table FWPASSWORDPOLICY should have type INTEGER but has type NUMBER(0)
    20:06:41,182 WARN [ims.jdbc.JDBCSchema] Column minUpperCase in table FWPASSWORDPOLICY should have type INTEGER but has type NUMBER(0)
    20:06:41,182 WARN [ims.jdbc.JDBCSchema] Column minLowerCase in table FWPASSWORDPOLICY should have type INTEGER but has type NUMBER(0)
    20:06:41,182 WARN [ims.jdbc.JDBCSchema] Column minAlpha in table FWPASSWORDPOLICY should have type INTEGER but has type NUMBER(0)
    20:06:41,182 WARN [ims.jdbc.JDBCSchema] Column minNumbers in table FWPASSWORDPOLICY should have type INTEGER but has type NUMBER(0)
    20:06:41,182 WARN [ims.jdbc.JDBCSchema] Column minAlphaNum in table FWPASSWORDPOLICY should have type INTEGER but has type NUMBER(0)
    20:06:41,182 WARN [ims.jdbc.JDBCSchema] Column minPunctuation in table FWPASSWORDPOLICY should have type INTEGER but has type NUMBER(0)
    20:06:41,182 WARN [ims.jdbc.JDBCSchema] Column minNonPrintable in table FWPASSWORDPOLICY should have type INTEGER but has type NUMBER(0)
    20:06:41,182 WARN [ims.jdbc.JDBCSchema] Column minNonAlpha in table FWPASSWORDPOLICY should have type INTEGER but has type NUMBER(0)
    20:06:41,182 WARN [ims.jdbc.JDBCSchema] Column evaluationPriority in table FWPASSWORDPOLICY should have type INTEGER but has type NUMBER(0)
    20:06:41,219 WARN [ims.jdbc.JDBCSchema] Column cleanup in table SNAPSHOT_TYPE should have type INTEGER but has type NUMBER(0)
    20:06:41,227 WARN [ims.jdbc.JDBCSchema] Column explore in table EXPLORE_AND_CORRELATE should have type INTEGER but has type NUMBER(0)
    20:06:41,227 WARN [ims.jdbc.JDBCSchema] Column correlate in table EXPLORE_AND_CORRELATE should have type INTEGER but has type NUMBER(0)
    20:06:41,227 WARN [ims.jdbc.JDBCSchema] Column create_global_user in table EXPLORE_AND_CORRELATE should have type INTEGER but has type NUMBER(0)
    20:06:41,227 WARN [ims.jdbc.JDBCSchema] Column update_global_user_fields in table EXPLORE_AND_CORRELATE should have type INTEGER but has type NUMBER(0)
    20:06:41,237 WARN [ims.jdbc.JDBCSchema] Column priority in table PX_POLICY should have type INTEGER but has type NUMBER(0)
    20:06:41,462 WARN [ims.jdbc.JDBCSchema] Column type in table PX_WHEN should have type INTEGER but has type NUMBER(0)
    20:06:41,462 WARN [ims.jdbc.JDBCSchema] Column step in table PX_WHEN should have type INTEGER but has type NUMBER(0)
    20:06:41,491 WARN [ims.jdbc.JDBCSchema] Column priority in table PX_RULE should have type INTEGER but has type NUMBER(0)
    20:06:41,499 WARN [ims.jdbc.JDBCSchema] Column priority in table PX_ACTION_ELEMENT should have type INTEGER but has type NUMBER(0)
    20:06:41,507 WARN [ims.jdbc.JDBCSchema] Column priority in table PX_DATA_ELEMENT should have type INTEGER but has type NUMBER(0)
    20:06:41,516 WARN [ims.jdbc.JDBCSchema] Column operator in table PX_CONDITION should have type INTEGER but has type NUMBER(0)
    20:06:41,723 WARN [ims.tmt.EnvironmentService] * Starting environment: MBP_USR_MGMNT
    20:06:41,745 WARN [ims.llsdk.role.azcache.ridiculouslydetailed] Adding typekey 'ADMINISTRATIVE ROLEMembership' for environment: 41
    20:06:41,747 WARN [ims.llsdk.role.azcache.ridiculouslydetailed] Adding typekey 'ADMINISTRATIVE ROLEAdminstration' for environment: 41
    20:06:41,750 WARN [ims.llsdk.role.azcache.ridiculouslydetailed] Adding typekey 'ADMINISTRATIVE ROLEOwnership' for environment: 41
    20:06:41,753 WARN [ims.llsdk.role.azcache.ridiculouslydetailed] Adding typekey 'ACCESS ROLEMembership' for environment: 41
    20:06:41,757 WARN [ims.llsdk.role.azcache.ridiculouslydetailed] Adding typekey 'ACCESS ROLEAdminstration' for environment: 41
    20:06:41,762 WARN [ims.llsdk.role.azcache.ridiculouslydetailed] Adding typekey 'ACCESS ROLEOwnership' for environment: 41
    20:06:41,766 WARN [ims.llsdk.role.azcache.ridiculouslydetailed] Adding typekey 'PROVISIONING ROLEAdminstration' for environment: 41
    20:06:41,769 WARN [ims.llsdk.role.azcache.ridiculouslydetailed] Adding typekey 'PROVISIONING ROLEOwnership' for environment: 41
    20:06:41,772 WARN [ims.llsdk.role.azcache.ridiculouslydetailed] Adding typekey 'IDENTITY POLICYIdentity Policy' for environment: 41
    20:06:41,776 WARN [ims.llsdk.role.azcache.ridiculouslydetailed] Adding typekey 'IDENTITY POLICYOwnership' for environment: 41
    20:06:41,777 WARN [ims.llsdk.role.azcache.ridiculouslydetailed] Adding typekey 'IDENTITY POLICY SETIdentity Policy Set' for environment: 41
    20:06:43,374 WARN [ConnectionManagedObject] Validating managed object connections...
    20:06:43,435 WARN [ConnectionManagedObject] Validating connection BUS_OBJ_RPT_SVR_CONNECTION
    20:06:43,436 WARN [ConnectionManagedObject] Validating connection BUS_OBJ_RPT_SVR_CONNECTION success.
    20:06:43,437 WARN [ConnectionManagedObject] Validating connection rptParamConn
    20:06:43,437 WARN [ConnectionManagedObject] Validating connection rptParamConn success.
    20:06:43,437 WARN [ConnectionManagedObject] Finished validating managed object conections.
    20:06:43,593 WARN [ims.tmt.WorkPointScriptsImportPlugin] WF is not enabled for environment:MBP_USR_MGMNT
    20:06:43,723 WARN [im.plugins.IMEnvironmentInitializerPlugin] Starting the EnvironmentListener for env : MBP_USR_MGMNT
    20:06:43,754 WARN [ims.tmt.EnvironmentService] * Started environment: MBP_USR_MGMNT
    20:08:38,453 WARN [ims.default] * Startup Step 25 : Attempting to start SchedulerService
    20:08:40,875 WARN [ims.default] * CryptoJ was initialized properly.
    20:08:40,876 WARN [ims.default] ** FIPS mode enabled : true
    20:08:40,880 WARN [ims.default] * Startup Step 26 : Attempting to recover unprocessed events and runtime status details
    20:08:40,882 ERROR [ims.bootstrap.Main] The IAM FW Startup was not successful
    20:08:40,882 ERROR [ims.bootstrap.Main] java.lang.NullPointerException
    at java.io.ByteArrayInputStream.<init>(ByteArrayInputStream.java:89)
    at com.netegrity.ims.statusDetail.RuntimeStatusDetailService._readRSD(RuntimeStatusDetailService.java:174)
    at com.netegrity.ims.statusDetail.RuntimeStatusDetailService.postLostRSD(RuntimeStatusDetailService.java:135)
    at com.netegrity.ims.bootstrap.Main.start(Main.java:293)
    at com.netegrity.webapp.SystemInitializer.contextInitialized(SystemInitializer.java:44)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

    20:08:40,883 WARN [ims.tmt.events] Attempting to shutdown long running events if any.
    20:08:40,885 WARN [ims.tmt.EnvironmentService] * Stopping environment: MBP_USR_MGMNT
    20:08:40,916 WARN [ims.tmt.EnvironmentService] * Stopped environment: MBP_USR_MGMNT
    java.lang.NullPointerException
    at java.io.ByteArrayInputStream.<init>(ByteArrayInputStream.java:89)
    at com.netegrity.ims.statusDetail.RuntimeStatusDetailService._readRSD(RuntimeStatusDetailService.java:174)
    at com.netegrity.ims.statusDetail.RuntimeStatusDetailService.postLostRSD(RuntimeStatusDetailService.java:135)
    at com.netegrity.ims.bootstrap.Main.start(Main.java:293)
    at com.netegrity.webapp.SystemInitializer.contextInitialized(SystemInitializer.java:44)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    20:08:40,986 WARN [im.plugins.IMEnvironmentInitializerPlugin] Installation in FIPS mode. No shared secret required.
    20:08:43,112 INFO [com.workpoint.server.ServerProperties] Loaded server properties from file:/cust/weblogic/middleware/domains/idm_domain_prod/servers/idm_prod_mgs1/stage/iam_im/iam_im.ear/config/workpoint-server.properties
    20:08:43,117 INFO [com.workpoint.server.ServerProperties] PRODUCT = WorkPoint; VERSION = 3.4.2; BUILD = 20071218 P003; BUILD DATE = March 21, 2008
    <Apr 3, 2018 8:08:43 PM PDT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    <Apr 3, 2018 8:08:43 PM PDT> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
    <Apr 3, 2018 8:08:43 PM PDT> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of idm_prod_cluster.>
    <Apr 3, 2018 8:08:50 PM PDT> <Notice> <Cluster> <BEA-000142> <Trying to download cluster JNDI tree from server idm_prod_mgs2.>
    <Apr 3, 2018 8:08:50 PM PDT> <Notice> <Cluster> <BEA-000164> <Synchronized cluster JNDI tree from server idm_prod_mgs2.>
    <Apr 3, 2018 8:08:50 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <Apr 3, 2018 8:08:51 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <Apr 3, 2018 8:08:51 PM PDT> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster address "******">
    <Apr 3, 2018 8:08:51 PM PDT> <Notice> <Security> <BEA-090171> <Loading the identity certificate and private key stored under the alias calwinalias from the JKS keystore file /cust/weblogic/middleware/wls10.3.5.0/server/lib/certs/idmprod/CalWINIdentity.>
    <Apr 3, 2018 8:08:51 PM PDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /usr/java/jdk1.6.0_27/jre/lib/security/cacerts.>
    <Apr 3, 2018 8:08:51 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Apr 3, 2018 8:08:51 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Apr 3, 2018 8:08:51 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Apr 3, 2018 8:08:51 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Apr 3, 2018 8:08:51 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Apr 3, 2018 8:08:51 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Apr 3, 2018 8:08:51 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Apr 3, 2018 8:08:51 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Apr 3, 2018 8:08:51 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Apr 3, 2018 8:08:51 PM PDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.7.40.151:8003 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Apr 3, 2018 8:08:51 PM PDT> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on 10.7.40.151:8004 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
    <Apr 3, 2018 8:08:51 PM PDT> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "idm_prod_mgs1" for domain "idm_domain_prod" running in Production Mode>
    <Apr 3, 2018 8:08:51 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <Apr 3, 2018 8:08:51 PM PDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    20:08:52,784 ERROR [ims.tmt.cachemanager] Failed to get user provider. java.lang.NullPointerException
    20:08:52,789 ERROR [ims.tmt.cachemanager] Failed to get user provider. java.lang.NullPointerException
    20:08:52,789 ERROR [ims.tmt.cachemanager] Failed to get user provider. java.lang.NullPointerException
    20:08:52,790 ERROR [ims.tmt.cachemanager] Failed to get user provider. java.lang.NullPointerException
    20:08:52,791 ERROR [ims.tmt.cachemanager] Failed to get user provider. java.lang.NullPointerException
    20:08:52,791 ERROR [ims.tmt.cachemanager] Failed to get user provider. java.lang.NullPointerException
    20:08:52,792 ERROR [ims.tmt.cachemanager] Failed to get user provider. java.lang.NullPointerException
    20:08:52,793 ERROR [ims.tmt.cachemanager] Failed to get user provider. java.lang.NullPointerException
    20:08:52,794 ERROR [ims.tmt.cachemanager] Failed to get user provider. java.lang.NullPointerException
    20:08:52,794 ERROR [ims.tmt.cachemanager] Failed to get user provider. java.lang.NullPointerException



  • 2.  Re: IAM Application Failed to start up:The IAM FW Startup was not successful
    Best Answer

    Broadcom Employee
    Posted 04-05-2018 07:45 AM

    Hi rajesh,
    We already fixed such an issue for jboss by deleting all the *.ser files under the <jboss_home>\bin\iam\iam\im\rsd folder.
    So please find this RSD folder into your weblogic instance and delete the .ser file(s) (get a backup of those files before) then restart the weblogic.

    Regards,

    Philippe.



  • 3.  Re: IAM Application Failed to start up:The IAM FW Startup was not successful

    Posted 04-05-2018 12:03 PM

    Hi Philippe

     

    Thanks for the response i will check if any of those available in weblogic and proceed further

     

    Thanks,

    Raj



  • 4.  Re: IAM Application Failed to start up:The IAM FW Startup was not successful

    Posted 04-11-2018 12:08 PM

    Hi Philippe,

     

    The solution worked..Thanks a ton. @guiph01

     

    Thanks,

    Raj.