[jboss-jira] [JBoss JIRA] (AS7-5562) Log message too cryptic when deployment references a non-existent configuration in profile config

Log message too cryptic when deployment references a non-existent configuration in profile config ------------------------------------------------------------------------------------------------- Key: AS7-5562 URL: https://issues.jboss.org/browse/AS7-5562 Project: Application Server 7 Issue Type: Enhancement Components: Server Affects Versions: 7.1.2.Final (EAP) Reporter: Brad Maxwell Assignee: Brad Maxwell Fix For: Open To Community Attachments: helloWorld.ear, helloWorld.ear-source.zip When a jboss-ejb-client.xml inside of a deployment that references an outbound-socket that does not exist in the standalone.xml, it logs a cryptic message and does not explain where the issue is. Note when a deployment contains more sub deployements, the log message is much larger and the issue if you know what to look for is hidden in the middle. 15:41:01,189 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.ejb3.dd-based-ejb-client-context.\"helloWorld.ear\" Missing[jboss.remoting.endpoint.subsystem.outbound-connection.part101node01-connection]","jboss.deployment.subunit.\"helloWorld.ear\".\"helloWorld.war\".INSTALL Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"helloWorld.ear\".INSTALL Missing[JBAS014861: <one or more transitive dependencies>]"]}}} The error message should be translated to say something to the extent of "Your deployment helloWorld.ear contains a jboss-ejb-client.xml which references an outbound-socket named part101node01 which is not defined in your JBoss profile's remoting subsystem configuration" jboss.ejb3.dd-based-ejb-client-context.\"helloWorld.ear - this shows that helloWorld.ear is the deployment, jboss.ejb3.dd-based-ejb-client-context seems to the jboss-ejb-client.xml jboss.remoting.endpoint.subsystem.outbound-connection.part101node01-connection - this shows that the subsystem that is missing the outbound-configuration is the remoting subsystem and that the reference name missing is part101node01