000036253 - Error scheduling data purging after new installation of RSA Identity Governance & Lifecycle 7.1.0 GA

Document created by RSA Customer Support Employee on Sep 12, 2018
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000036253
Applies ToRSA Product Set: Identity Governance & Lifecycle 
RSA Version/Condition:
7.1.0 GA
Issue
After installing RSA Identity Governance & Lifecycle 7.1.0 GA and upon startup, the application does not render in the UI. The aveksaServer.log has the following stack trace error:
 


+++++
BEGIN STACK TRACE
+++++

03/27/2018 03:42:15.217 INFO  (Thread-0 (ActiveMQ-client-global-threads-729203364)) [com.aveksa.server.message.MessageSubscriber] Recieved first message from JMS
03/27/2018 03:42:15.370 INFO  (Expiry Thread 1) [com.aveksa.server.core.ExpiryManager] Expiry thread started
03/27/2018 03:42:15.381 INFO  (ServerService Thread Pool -- 67) [com.aveksa.server.agent.core.AgentMonitor] Agent Monitor initializing 0
3/27/2018 03:42:15.387 INFO  (ServerService Thread Pool -- 67) [com.aveksa.server.agent.core.AgentMonitor] Agent Monitor initialized
03/27/2018 03:42:15.387 INFO  (Expiry Thread 2) [com.aveksa.server.core.ExpiryManager] Expiry thread started
03/27/2018 03:42:15.395 INFO  (ServerService Thread Pool -- 67) [com.aveksa.server.scheduler.SchedulerServiceProvider] Deleting scheduled task 2
03/27/2018 03:42:15.417 INFO  (ServerService Thread Pool -- 67) [com.aveksa.server.scheduler.SchedulerServiceProvider] Sent message to remove task id: 2 from the scheduler: SystemScheduler
03/27/2018 03:42:15.445 INFO  (ServerService Thread Pool -- 67) [com.aveksa.server.scheduler.SchedulerServiceProvider] Deleting scheduled task 3
03/27/2018 03:42:15.452 INFO  (ServerService Thread Pool -- 67) [com.aveksa.server.scheduler.SchedulerServiceProvider] Sent message to remove task id: 3 from the scheduler: SystemScheduler
03/27/2018 03:42:15.465 INFO  (ServerService Thread Pool -- 67) [com.aveksa.server.scheduler.SchedulerServiceProvider] Deleting scheduled task 4
03/27/2018 03:42:15.469 INFO  (ServerService Thread Pool -- 67) [com.aveksa.server.scheduler.SchedulerServiceProvider] Sent message to remove task id: 4 from the scheduler: SystemScheduler
03/27/2018 03:42:15.484 ERROR (ServerService Thread Pool -- 67) [com.aveksa.server.core.Container] Unable to start service SystemService.  com.aveksa.server.runtime.ServerException: Error Scheduling Data Purging.     
    at
com.aveksa.server.system.SystemServiceProvider.initDataPruningScheduledTask(SystemServiceProvider.java:3387)
   
    at com.aveksa.server.system.SystemServiceProvider.start(SystemServiceProvider.java:470)
    at com.aveksa.server.core.Container.startService(Container.java:144)
    at com.aveksa.server.core.Container.initialize(Container.java:105)
    at com.aveksa.server.runtime.AveksaSystem.doStartupOperations(AveksaSystem.java:362)   
    at com.aveksa.server.runtime.AveksaSystem.initialize(AveksaSystem.java:335)     
    at com.aveksa.init.Startup.init(Startup.java:52)     
    at com.aveksa.gui.core.ACMFramework.init(ACMFramework.java:94)     
    at com.aveksa.gui.core.ACMFramework.initInstance(ACMFramework.java:83)     
    at com.aveksa.init.InitServlet.init(InitServlet.java:42)     
    at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:117)     
    at org.wildfly.extension.undertow.security.RunAsLifecycleInterceptor.handle(RunAsLifecycleInterceptor.java:65)



    at org.wildfly.extension.undertow.security.RunAsLifecycleInterceptor.init(RunAsLifecycleInterceptor.java:76)     
    at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:103)     
    at io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:250)     
    at io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:133)     
    at io.undertow.servlet.core.DeploymentManagerImpl$2.call(DeploymentManagerImpl.java:546)     
    at io.undertow.servlet.core.DeploymentManagerImpl$2.call(DeploymentManagerImpl.java:517)     
    at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)     
    at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)     
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)     
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)     
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)     
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)     
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)     
    at io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:559)     
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:101)     
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:82)     
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)     
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)     
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)     
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)     
    at java.lang.Thread.run(Thread.java:748)     at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: com.thoughtworks.xstream.converters.ConversionException: Cannot parse date
---- Debugging information ----
message             : Cannot parse date
date                : 2018-03-31 01:00:00 UCT
class               : java.util.Date
required-type       : java.util.Date
converter-type      : com.thoughtworks.xstream.converters.SingleValueConverterWrapper
wrapped-converter   : com.thoughtworks.xstream.converters.basic.DateConverter
Default date pattern: yyyy-MM-dd HH:mm:ss.S z
Default era date pattern: yyyy-MM-dd G HH:mm:ss.S z
Alternative date pattern: yyyy-MM-dd HH:mm:ss.S z
Alternative date pattern[1]: yyyy-MM-dd HH:mm:ss.S a
Alternative date pattern[2]: yyyy-MM-dd HH:mm:ssz
Alternative date pattern[3]: yyyy-MM-dd HH:mm:ss z
Alternative date pattern[4]: yyyy-MM-dd'T'HH:mm:ss.SX
Alternative date pattern[5]: yyyy-MM-dd'T'HH:mm:ssX
Alternative date pattern[6]: yyyy-MM-dd'T'HH:mmX
Alternative date pattern[7]: yyyy-MM-dd HH:mm:ssa
path                : /com.aveksa.common.scheduler.rules.CronRule/ruleStartDate
line number         : 9
class[1]            : com.aveksa.common.scheduler.rules.CronRule
converter-type[1]   : com.thoughtworks.xstream.converters.reflection.ReflectionConverter
version             : 1.4.10

-------------------------------     
    at com.thoughtworks.xstream.converters.basic.DateConverter.fromString(DateConverter.java:230)     
    at com.thoughtworks.xstream.converters.SingleValueConverterWrapper.fromString(SingleValueConverterWrapper.java:41)     
    at com.thoughtworks.xstream.converters.SingleValueConverterWrapper.unmarshal(SingleValueConverterWrapper.java:49)     
    at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)     
    at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:70)     
    at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)     
    at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.unmarshallField(AbstractReflectionConverter.java:503)     
    at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.doUnmarshal(AbstractReflectionConverter.java:429)     
    at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.unmarshal(AbstractReflectionConverter.java:281)     
    at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)     
    at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:70)     
    at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)     
    at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)     
    at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134)     
    at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32)     
    at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1486)     at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1466)     
    at com.thoughtworks.xstream.XStream.fromXML(XStream.java:1337)     at com.thoughtworks.xstream.XStream.fromXML(XStream.java:1328)     
    at com.aveksa.common.xml.XMLStreamManager.fromXML(XMLStreamManager.java:93)     
    at com.aveksa.server.system.SystemServiceProvider.getDataPruningScheduleSavedCopy(SystemServiceProvider.java:3249)     
    at com.aveksa.server.system.SystemServiceProvider.initDataPruningScheduledTask(SystemServiceProvider.java:3384)   
 
    ... 33 more
03/27/2018 03:42:15.488 INFO  (ServerService Thread Pool -- 67) [com.aveksa.migration.jdbctool.CheckDatabase] Node Time:  2018-03-27 03:42:15.488
03/27/2018 03:42:15.488 INFO  (ServerService Thread Pool -- 67) [com.aveksa.migration.jdbctool.CheckDatabase] Database Time:  2018-03-27 03:42:15.0

03/27/2018 03:42:17.587 INFO  (ServerService Thread Pool -- 67) [com.aveksa.server.runtime.AveksaEventEngine] Starting the pool with a max size of [20]
03/27/2018 03:42:17.588 INFO  (ServerService Thread Pool -- 67) [com.aveksa.server.runtime.AveksaEventEngine] Thread pool started
03/27/2018 03:42:17.646 INFO  (EventHandler for event [AveksaEventEngineInitializedEvent]) [com.aveksa.server.scheduler.SchedulerServiceProvider] Deleting scheduled task 5
03/27/2018 03:42:17.651 INFO  (EventHandler for event [AveksaEventEngineInitializedEvent]) [com.aveksa.server.scheduler.SchedulerServiceProvider] Sent message to remove task id: 5 from the scheduler: SystemScheduler
03/27/2018 03:42:17.662 INFO  (EventHandler for event [AveksaEventEngineInitializedEvent]) [com.aveksa.server.scheduler.SchedulerServiceProvider] Deleting scheduled task 6
03/27/2018 03:42:17.689 INFO  (EventHandler for event [AveksaEventEngineInitializedEvent]) [com.aveksa.server.scheduler.SchedulerServiceProvider] Sent message to remove task id: 6 from the scheduler: SystemScheduler
03/27/2018 03:42:17.868 INFO  (ServerService Thread Pool -- 67) [com.aveksa.server.core.Container] Starting a local agent
03/27/2018 03:42:17.885 INFO  (Local Agent Thread) [com.aveksa.client.datacollector.startup.Bootstrap] Initializing bootstrap of agent
03/27/2018 03:42:17.896 INFO  (Local Agent Thread) [com.aveksa.client.datacollector.startup.agent.AgentShutDownHook] ASDH20: Created ShutDownHook with ID: Thread-129
03/27/2018 03:42:17.907 INFO  (Local Agent Thread) [com.aveksa.client.datacollector.agent.AgentConfiguration] COMPLETED method=LoadProperties http://localhost:8080/aveksa/agent.submit, 1 
03/27/2018 03:42:17.909 INFO  (Local Agent Thread) [com.aveksa.client.datacollector.agent.AgentConfiguration] Aveksa Product Version: 7.1.0

+++++
END STACK TRACE
+++++

CauseIt is suspected that the root cause is either:
  1. Java or the RSA Identity Governance & Lifecycle application does not like the date format for the NAME = 'Data_Pruning_Pkg.Main' task found in the T_SCHEDULED_TASKS table.
  2. Java or the RSA Identity Governance & Lifecycle application does not like the date format for the PARAMETER = "DataPurgingDatabaseUpdateSchedule”  found in the T_SYSTEM_SETTINGS table.
Workaround
  1. Ensure that acm is not running by typing:


acm status

        If acm is running, the message returned will be RSA Identity Governance and Lifecycle is running.

  1. Then type the following command to stop acm:


acm stop


  1. With acm shut down and the database running, execute the following SQL commands: 


UPDATE T_SYSTEM_SETTINGS SET VALUE = 'false' WHERE  PARAMETER = 'DataPurgingScheduledTask'; 
commit;


This command has the following results:


  1. Sets the DataPurgingScheduledTask to false in the T_SYSTEM_SETTINGS table. 
  2. Deletes the row in the T_SCHEDULED_TASKS table where NAME = Data_Pruning_Pkg.Main.
  3. Note that this workaround does leaves a VALUE for the DataPurgingDatabaseUpdateSchedule PARAMETER in the T_SYSTEM_SETTINGS table when it should be NULL.
        4. Next start acm:


acm start


  1. You may then re-schedule the Purging task by navigating to Admin > System > Data Management  > Purging and reviewing the Scheduling section.

Attachments

    Outcomes