Bug 900892 (JBPAPP6-1430)
| Summary: | Log message too cryptic when deployment references a non-existent configuration in profile config | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Brad Maxwell <bmaxwell> | ||||||
| Component: | Other | Assignee: | Brad Maxwell <bmaxwell> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Martin Svehla <msvehla> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 6.0.0 | CC: | bmaxwell, msvehla, rsvoboda | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | TBD EAP 6 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| URL: | http://jira.jboss.org/jira/browse/JBPAPP6-1430 | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-08-11 11:50:41 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Brad Maxwell
2012-09-14 21:06:49 UTC
Attachment: Added: helloWorld.ear Attachment: Added: helloWorld.ear-source.zip Link: Added: This issue Cloned to JBPAPP-9934 Link: Added: This issue incorporates AS7-5562 Docs QE Status: Removed: NEW 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. 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.
|