IDM services start up issue after Hotfix deployment: WFLYDS0005: Caught exception writing deployment marker file

Products

• CA Identity Suite
• CA Identity Manager

Issue/Introduction

After deploying hotfix (version CHF_IMS-14.4.1-CHF002, CHF_JCS-14.4.1-CHF002, CHF_PS-14.4.1-CHF002) on development servers. After deployment we see idm restart issue. Services starts- stops and start up automatically. We followed below steps 

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.

Log shows:

2022-07-06 13:27:32,933 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0005: Caught exception writing deployment marker file /opt/CA/jboss/jboss-eap-7.2.9/standalone/deployments/iam_im.ear.dodeploy: java.io.FileNotFoundException: /opt/CA/jboss/jboss-eap-7.2.9/standalone/deployments/iam_im.ear.dodeploy (Is a directory)
 at java.io.FileOutputStream.open0(Native Method)
 at java.io.FileOutputStream.open(FileOutputStream.java:270)

Cause

 

 

Resolution

Verify ownership of the ../deployments directory and its contents. 

In the above case the files were inadvertently owned by 'idm' user instead of the weblogic or wildfly user that runs the application server.

Correcting the ownership and/or permissions resolved the issue.