CA IDM JBoss/Wildfly gets stuck during start up - JBAS015003: Found iam_im.ear in deployment directory. To trigger deployment create a file called iam_im.ear.dodeploy

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Portal
• CA Identity Suite

Issue/Introduction

I have IDM  installed and running on Windows 2016.  It's deployed on jboss EAP 6.4.  The issue I'm having is that occasionally when I start up jboss, the start up process gets stuck.

The workaround is to stop the service, then start it back up again.  However, this is causing an issue when the server gets patched and the windows service is supposed to start up autiomatically.

The last line in the server.log when it gets stuck starting up is always:

...

05:19:20,675 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named AlertPvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

java:global/iam_im/iam_im_wpServer/AlertPvt_EJB!com.workpoint.server.pojo.AlertPvtLocal

java:app/iam_im_wpServer/AlertPvt_EJB!com.workpoint.server.pojo.AlertPvtLocal

java:module/AlertPvt_EJB!com.workpoint.server.pojo.AlertPvtLocal

java:global/iam_im/iam_im_wpServer/AlertPvt_EJB!com.workpoint.server.pojo.AlertPvt

java:app/iam_im_wpServer/AlertPvt_EJB!com.workpoint.server.pojo.AlertPvt

java:module/AlertPvt_EJB!com.workpoint.server.pojo.AlertPvt

java:jboss/exported/iam_im/iam_im_wpServer/AlertPvt_EJB!com.workpoint.server.pojo.AlertPvt

05:19:20,675 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named FormPvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

java:global/iam_im/iam_im_wpServer/FormPvt_EJB!com.workpoint.server.pojo.FormPvt

java:app/iam_im_wpServer/FormPvt_EJB!com.workpoint.server.pojo.FormPvt

java:module/FormPvt_EJB!com.workpoint.server.pojo.FormPvt

java:jboss/exported/iam_im/iam_im_wpServer/FormPvt_EJB!com.workpoint.server.pojo.FormPvt

java:global/iam_im/iam_im_wpServer/FormPvt_EJB!com.workpoint.server.pojo.FormPvtLocal

java:app/iam_im_wpServer/FormPvt_EJB!com.workpoint.server.pojo.FormPvtLocal

java:module/FormPvt_EJB!com.workpoint.server.pojo.FormPvtLocal

05:19:20,863 WARN  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016012: Deployment deployment "iam_im.ear" contains CDI annotations but beans.xml was not found.

Environment

Release :

Component : IdentityMinder(Identity Manager)

Cause

The log indicates that JBoss is having problems deploying the .ear files, for example,

06:22:13,496 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found iam_im.ear in deployment directory. To trigger deployment create a file called iam_im.ear.dodeploy

06:22:13,496 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found castylesr5.1.1.ear in deployment directory. To trigger deployment create a file called castylesr5.1.1.ear.dodeploy

JBoss should clean up the deployments folder during shutdown/restart and manage the deployment states via updating the appropriate filename extensions but sometimes this doesn't happen as expected.

Resolution

Stop Jboss and ensure that the /JBOSS_HOME/standalone/deployments  directory includes only a .dodeploy version of the .ear files in addition to the actual application's .ear files. You may need to delete any .failed or .deploying files and create .dodeploy files for the im application's two .ear files. In other words the directory should have these files for Identity Manager to properly deploy:

       iam_im.ear

       iam_im.ear.dodeploy

       castylesr5.1.1.ear

       castylesr5.1.1.ear.dodeploy

After you create the .dodeploy files, start JBoss again.