Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1112433

Summary: 'JBAS015876: Starting deployment of "null"' in server log
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: James Livingston <jlivings>
Component: ServerAssignee: Chao Wang <chaowan>
Status: CLOSED CURRENTRELEASE QA Contact: Jan Martiska <jmartisk>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.2.3CC: asaji, chaowan, jmartisk, joallen, kkhan
Target Milestone: DR1   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:

Description James Livingston 2014-06-23 23:53:30 UTC 
When a deployment contains sub-deployments, the server will log an entry like 'JBAS015876: Starting deployment of "null" (runtime-name: some_ejb.jar)' which looks like it could be a problem.

There is no actual problem, it is just that the sub deployment does not have a management name. It would be nice to pull in the fix for WFLY-2205 to reduce the risk of confusion, although it's a superficial change.
Comment 2 JBoss JIRA Server 2014-09-08 17:43:47 UTC 
Brian Stansberry <brian.stansberry> updated the status of jira JBEAP-5 to Resolved
Comment 3 Jan Martiska 2014-09-18 10:41:26 UTC 
Verified in EAP 6.4.0.DR1.1.