Bug 999465
| Summary: | appclient.xml wrong naming version | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Aleksandar Kostadinov <akostadi> |
| Component: | Application Client | Assignee: | Stuart Douglas <sdouglas> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | Tom WELLS <twells> |
| Priority: | unspecified | ||
| Version: | 6.1.1 | CC: | brian.stansberry, cdewolf, dimitris, lcarlon, rdickens, twells |
| Target Milestone: | ER4 | ||
| Target Release: | EAP 6.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
The naming subsystem would fail to start because of an incorrect version number in the appclient.xml file, causing a dependency issue. This version has been corrected, and the appclient launches successfully.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-15 16:16:52 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: | |||
|
Description
Aleksandar Kostadinov
2013-08-21 11:15:35 UTC
I haven't tried it against EAP6. Are you sure this is a problem against EAP 6 too and not just upstream WildFly? I found it with EAP and then checked wildfly. Would you create a push request for EAP or should I do? I was ready to create one so did it anyways, please see https://github.com/jbossas/jboss-eap/pull/305 Thank you. Carlo de Wolf <cdewolf> made a comment on jira WFLY-1914 How can a change in namespace definition be a fix here? The server should behave just fine on an old namespace version. Brian Stansberry <brian.stansberry> made a comment on jira WFLY-1914 Carlo: The subsystem was written such that the parsers treat {code} <subsystem xmlns="urn:jboss:domain:naming:1.0"/> {code} as equivalent to {code} <subsystem xmlns="urn:jboss:domain:naming:2.0"> <remote-naming/> </subsystem> {code} The latter requires the remoting subsystem which is not present in appclient.xml. We can't change the parser for 1.0 without breaking existing working configs. We still see the issue with 6.2.0 ER3.1.. just saying Brian, I speculated that it is ER3.1, I'm using RPM distro that's possibly not exactly matching 3.1. I'll try again when ER5 is out. Ah, I see. ER3.1 was just some sort of respin of ER3 that didn't include any new fixes. I do not see the issue with ER5. |