On Restart of widlfly8.2 war deployment is failing

[mallikarjuna.reddy.nune]

On Restart of widlfly8.2 war deployment is failing

After doing any manual changes , restarting wildfly on Linux system we are seeing deployment failure with below error

Any inputs will be helpful. After deleting data folder and changing ownership of files to jboss user we are able to deploy.

2016-04-01 01:43:27,484 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" =>"myproduct.ear")]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => [

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.SubscriberMessageEJB.InstanceName is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.SubscriberMessageEJB]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.RuntimeStatusDetailEJB.ValidatorFactory is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.RuntimeStatusDetailEJB]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.JobUpdatePvt_EJB.env.queue.wpEventQueue is missing [jboss.naming.context.java.queue.wpEventQueue]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.GroupTypePvt_EJB.env.jms.wpConnectionFactory is missing [jboss.naming.context.java.jms.wpConnectionFactory]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.JobUpdatePvt_EJB.env.queue.wpServAutoActQueue is missing [jboss.naming.context.java.queue.wpServAutoActQueue]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.ServerCommandsEJB.ORB is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.ServerCommandsEJB]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.ServerCommandsEJB.InstanceName is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.ServerCommandsEJB]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.ServerCommandsEJB.InAppClientContainer is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.ServerCommandsEJB]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.MonitorPvt_EJB.env.jms.wpConnectionFactory is missing [jboss.naming.context.java.jms.wpConnectionFactory]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.SubscriberMessageEJB.InAppClientContainer is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.SubscriberMessageEJB]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.WorkFlowCallBackEJB.ORB is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.WorkFlowCallBackEJB]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.AlertPvt_EJB.env.queue.wpEventQueue is missing [jboss.naming.context.java.queue.wpEventQueue]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.ScriptExecAsyncPvt_EJB.env.queue.wpEventQueue is missing [jboss.naming.context.java.queue.wpEventQueue]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.ForceActionUpdatePvt_EJB.env.jms.wpConnectionFactory is missing [jboss.naming.context.java.jms.wpConnectionFactory]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.WorkFlowCallBackEJB.InAppClientContainer is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.WorkFlowCallBackEJB]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.WorkItemUpdatePvt_EJB.env.queue.wpEventQueue is missing [jboss.naming.context.java.queue.wpEventQueue]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.UniqueIDUpdatePvt_EJB.env.jms.wpConnectionFactory is missing [jboss.naming.context.java.jms.wpConnectionFactory]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.RuntimeStatusDetailEJB.InstanceName is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.RuntimeStatusDetailEJB]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.WorkFlowCallBackEJB.Validator is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.WorkFlowCallBackEJB]",

    "jboss.deployment.subunit.\"iam_im.ear\".\"iam_im_mypoduct_ejb.jar\".INSTALL is missing [jboss.deployment.subunit.\"iam_im.ear\".\"management_console.war\".deploymentCompleteService]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.WorkItemPvt_EJB.env.queue.wpUtilQueue is missing [jboss.naming.context.java.queue.wpUtilQueue]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.SubscriberMessageEJB.ValidatorFactory is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.SubscriberMessageEJB]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.UniqueIDUpdatePvt_EJB.env.queue.wpUtilQueue is missing [jboss.naming.context.java.queue.wpUtilQueue]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.AlertPvt_EJB.env.jms.wpConnectionFactory is missing [jboss.naming.context.java.jms.wpConnectionFactory]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.ServerAutomatedActivityMDBean.env.jms.wpConnectionFactory is missing [jboss.naming.context.java.jms.wpConnectionFactory]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.ResourcePvt_EJB.env.queue.wpEventQueue is missing [jboss.naming.context.java.queue.wpEventQueue]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.ServerAutomatedActivityMDBean.env.queue.wpEventQueue is missing [jboss.naming.context.java.queue.wpEventQueue]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.SubscriberMessageEJB.Validator is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.SubscriberMessageEJB]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.RuntimeStatusDetailEJB.InAppClientContainer is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.RuntimeStatusDetailEJB]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.JobUpdatePvt_EJB.env.queue.wpUtilQueue is missing [jboss.naming.context.java.queue.wpUtilQueue]",

    "jboss.deployment.subunit.\"iam_im.ear\".\"iam_im_mypoduct_ejb.jar\".weld.weldClassIntrospector is missing [jboss.deployment.subunit.\"iam_im.ear\".\"iam_im_mypoduct_ejb.jar\".beanmanager]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.MonitorPvt_EJB.env.queue.wpEventQueue is missing [jboss.naming.context.java.queue.wpEventQueue]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.ScriptExecutePvt_EJB.env.queue.wpEventQueue is missing [jboss.naming.context.java.queue.wpEventQueue]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.ResourcePvt_EJB.env.jms.wpConnectionFactory is missing [jboss.naming.context.java.jms.wpConnectionFactory]",

    "jboss.deployment.subunit.\"iam_im.ear\".\"iam_im_wpServer.jar\".component.ServerAutomatedActivityMDBean.CREATE is missing [jboss.ra.hornetq-ra]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.RuntimeStatusDetailEJB.HandleDelegate is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.RuntimeStatusDetailEJB]",

    "jboss.deployment.subunit.\"iam_im.ear\".\"management_console.war\".INSTALL is missing [jboss.deployment.subunit.\"iam_im.ear\".\"user_console.war\".deploymentCompleteService]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.ServerCommandsEJB.HandleDelegate is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.ServerCommandsEJB]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.EventPvt_EJB.env.queue.wpEventQueue is missing [jboss.naming.context.java.queue.wpEventQueue]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.WorkItemUpdatePvt_EJB.env.queue.wpUtilQueue is missing [jboss.naming.context.java.queue.wpUtilQueue]",

    "jboss.deployment.subunit.\"iam_im.ear\".\"iam_im_wpServer.jar\".component.EventMDBean.CREATE is missing [jboss.ra.hornetq-ra]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.ServerCommandsEJB.ValidatorFactory is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.ServerCommandsEJB]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.WorkFlowCallBackEJB.ValidatorFactory is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.WorkFlowCallBackEJB]",

    "jboss.deployment.unit.\"iam_im.ear\".deploymentCompleteService is missing [jboss.deployment.subunit.\"iam_im.ear\".\"redirect.war\".deploymentCompleteService, jboss.deployment.subunit.\"iam_im.ear\".\"iam_im_mypoduct_ejb.jar\".deploymentCompleteService, jboss.deployment.subunit.\"iam_im.ear\".\"management_console.war\".deploymentCompleteService, jboss.deployment.subunit.\"iam_im.ear\".\"user_console.war\".deploymentCompleteService, jboss.deployment.subunit.\"iam_im.ear\".\"manage_redirect.war\".deploymentCompleteService]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.ForceActionUpdatePvt_EJB.env.queue.wpUtilQueue is missing [jboss.naming.context.java.queue.wpUtilQueue]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.WorkItemUpdatePvt_EJB.env.queue.wpServAutoActQueue is missing [jboss.naming.context.java.queue.wpServAutoActQueue]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.UtilityMDBean.env.jms.wpConnectionFactory is missing [jboss.naming.context.java.jms.wpConnectionFactory]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.ServerAutomatedActivityMDBean.env.queue.wpUtilQueue is missing [jboss.naming.context.java.queue.wpUtilQueue]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.RuntimeStatusDetailEJB.ORB is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.RuntimeStatusDetailEJB]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.UtilityMDBean.env.queue.wpServAutoActQueue is missing [jboss.naming.context.java.queue.wpServAutoActQueue]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.ServerCommandsEJB.Validator is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.ServerCommandsEJB]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.ServerAutomatedActivityMDBean.env.queue.wpServAutoActQueue is missing [jboss.naming.context.java.queue.wpServAutoActQueue]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.WorkItemPvt_EJB.env.jms.wpConnectionFactory is missing [jboss.naming.context.java.jms.wpConnectionFactory]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.JobUpdatePvt_EJB.env.jms.wpConnectionFactory is missing [jboss.naming.context.java.jms.wpConnectionFactory]",

    "jboss.deployment.subunit.\"iam_im.ear\".\"iam_im_wpServer.jar\".component.UtilityMDBean.CREATE is missing [jboss.ra.hornetq-ra]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.SubscriberMessageEJB.HandleDelegate is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.SubscriberMessageEJB]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.ForceActionUpdatePvt_EJB.env.queue.wpServAutoActQueue is missing [jboss.naming.context.java.queue.wpServAutoActQueue]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.WorkFlowCallBackEJB.HandleDelegate is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.WorkFlowCallBackEJB]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.WorkItemUpdatePvt_EJB.env.jms.wpConnectionFactory is missing [jboss.naming.context.java.jms.wpConnectionFactory]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.UniqueIDUpdatePvt_EJB.env.queue.wpServAutoActQueue is missing [jboss.naming.context.java.queue.wpServAutoActQueue]",

    "jboss.deployment.subunit.\"iam_im.ear\".\"redirect.war\".INSTALL is missing [jboss.deployment.subunit.\"iam_im.ear\".\"iam_im_mypoduct_ejb.jar\".deploymentCompleteService]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.EventMDBean.env.jms.wpConnectionFactory is missing [jboss.naming.context.java.jms.wpConnectionFactory]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.EventPvt_EJB.env.jms.wpConnectionFactory is missing [jboss.naming.context.java.jms.wpConnectionFactory]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.RuntimeStatusDetailEJB.Validator is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.RuntimeStatusDetailEJB]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.WorkFlowCallBackEJB.InstanceName is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.WorkFlowCallBackEJB]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.ScriptExecAsyncPvt_EJB.env.jms.wpConnectionFactory is missing [jboss.naming.context.java.jms.wpConnectionFactory]",

    "jboss.deployment.subunit.\"iam_im.ear\".\"manage_redirect.war\".INSTALL is missing [jboss.deployment.subunit.\"iam_im.ear\".\"redirect.war\".deploymentCompleteService]",

    "jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.SubscriberMessageEJB.ORB is missing [jboss.naming.context.java.comp.myproject_war_mypoduct_ejb.SubscriberMessageEJB]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.GroupTypePvt_EJB.env.queue.wpEventQueue is missing [jboss.naming.context.java.queue.wpEventQueue]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.ForceActionUpdatePvt_EJB.env.queue.wpEventQueue is missing [jboss.naming.context.java.queue.wpEventQueue]",

    "jboss.naming.context.java.comp.myproject_war_wpServer.ScriptExecutePvt_EJB.env.jms.wpConnectionFactory is missing [jboss.naming.context.java.jms.wpConnectionFactory]"

]}

Regards,

Mallikarjuna

[jamezp]

What kind of changes did you make?

--

James R. Perkins

[mallikarjuna.reddy.nune]

Hi,

Sometime we modify standalone-full.xml or any other jars in war.

We are deploying our application as jboss user. when we do any modifications to files ownership is changing as root (in linux) .

When we start wildfly after these changes, facing above error and seeing ourproject.ear.failed in deployment folder.

After stoping server and changing ownership to jboss user and renaming .failed to .dodeploy and restarting seems working.

We are using this as work around as of now .

Any inputs will be helpful.

Regards,

Mallikarjuna

[jamezp]

That's an OS level thing. If files are being changed and the owner is being changed there's nothing WildFly can do about that.

I would advise either using the web console or CLI to make changes to the configuration though. That would avoid this issues. It would also give you the benefit of not having to shut down the server before you make changes. In a lot of cases you won't even need to restart or reload the server. The changes will be available immediately with no other server interaction required.

--

James R. Perkins