Bug 900892 (JBPAPP6-1430) - Log message too cryptic when deployment references a non-existent configuration in profile config
Summary: Log message too cryptic when deployment references a non-existent configurati...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: JBPAPP6-1430
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Other
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: TBD EAP 6
Assignee: Brad Maxwell
QA Contact: Martin Svehla
URL: http://jira.jboss.org/jira/browse/JBP...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-14 21:06 UTC by Brad Maxwell
Modified: 2014-08-11 11:50 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-08-11 11:50:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
helloWorld.ear (990 bytes, application/octet-stream)
2012-09-14 21:13 UTC, Brad Maxwell
no flags Details
helloWorld.ear-source.zip (5.28 KB, application/zip)
2012-09-14 21:13 UTC, Brad Maxwell
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker AS7-5562 0 Major Open Log message too cryptic when deployment references a non-existent configuration in profile config 2017-05-30 12:59:29 UTC
Red Hat Issue Tracker JBPAPP6-1430 0 Major Closed Log message too cryptic when deployment references a non-existent configuration in profile config 2017-05-30 12:59:29 UTC

Description Brad Maxwell 2012-09-14 21:06:49 UTC
Help Desk Ticket Reference: https://na7.salesforce.com/500A000000AsUt9
project_key: JBPAPP6

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

Comment 1 Brad Maxwell 2012-09-14 21:13:35 UTC
Attachment: Added: helloWorld.ear
Attachment: Added: helloWorld.ear-source.zip


Comment 2 Brad Maxwell 2012-09-14 21:17:59 UTC
Link: Added: This issue Cloned to JBPAPP-9934


Comment 3 Brad Maxwell 2012-09-14 21:20:08 UTC
Link: Added: This issue incorporates AS7-5562


Comment 4 Anne-Louise Tangring 2012-11-13 20:57:59 UTC
Docs QE Status: Removed: NEW 


Comment 5 Rostislav Svoboda 2013-02-25 11:15:23 UTC
If this should be included in EAP 6.1.0, jboss-eap-6.1.0 flag must be selected to enter 3-ACK process. Please set pm, dev, qa acks to '?' too.

Comment 7 Martin Svehla 2014-08-11 11:50:41 UTC
Tried the example EAR in EAP 6.3.0.GA and I'm getting following message:

JBAS014775:    New missing/unsatisfied dependencies:
      service jboss.remoting.endpoint.subsystem.outbound-connection.part101node01-connection (missing) dependents: [service jboss.ejb3.dd-based-ejb-client-context."helloWorld.ear"]

So it seems somewhere in older releases the message was changed to something more descriptive. I'm closing this bug, if you think more work needs to be done on it, please reopen with explanation. Thanks.


Note You need to log in before you can comment on or make changes to this bug.