Bug 999465 – appclient.xml wrong naming version

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 999465 - appclient.xml wrong naming version

Summary:	appclient.xml wrong naming version

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	Application Client (Show other bugs)
Sub Component:
Version:	6.1.1
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	ER4
Target Release:	EAP 6.2.0
Assigned To:	Stuart Douglas
QA Contact:
Docs Contact:	Tom WELLS

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2013-08-21 07:15 EDT by Aleksandar Kostadinov
Modified:	2015-05-17 21:29 EDT (History)
CC List:	6 users (show)

See Also:
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 11:16:52 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	WFLY-1914	Major	Resolved	Application client container doesn't start	2015-09-16 10:32:50 EDT

Groups: None (edit)

Description Aleksandar Kostadinov 2013-08-21 07:15:35 EDT

This is a clone of https://issues.jboss.org/browse/WFLY-1914 

Trivial to fix and IMO can happily go to 6.1.1 without risk. Actually that might be a regression in EAP.

Comment 1 Jaikiran Pai 2013-08-21 07:17:31 EDT

I haven't tried it against EAP6. Are you sure this is a problem against EAP 6 too and not just upstream WildFly?

Comment 2 Aleksandar Kostadinov 2013-08-21 07:35:18 EDT

I found it with EAP and then checked wildfly. Would you create a push request for EAP or should I do?

Comment 3 Aleksandar Kostadinov 2013-08-21 07:39:04 EDT

I was ready to create one so did it anyways, please see
https://github.com/jbossas/jboss-eap/pull/305

Comment 4 Jaikiran Pai 2013-08-21 07:41:16 EDT

Thank you.

Comment 5 JBoss JIRA Server 2013-08-22 03:12:15 EDT

Carlo de Wolf <cdewolf@redhat.com> 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.

Comment 6 JBoss JIRA Server 2013-08-23 16:57:07 EDT

Brian Stansberry <brian.stansberry@redhat.com> 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.

Comment 8 Stuart Douglas 2013-09-30 05:04:18 EDT

PR: https://github.com/jbossas/jboss-eap/pull/489

Comment 10 Aleksandar Kostadinov 2013-10-07 07:15:20 EDT

We still see the issue with 6.2.0 ER3.1.. just saying

Comment 13 Aleksandar Kostadinov 2013-10-07 14:46:09 EDT

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.

Comment 14 Brian Stansberry 2013-10-07 14:54:04 EDT

Ah, I see. ER3.1 was just some sort of respin of ER3 that didn't include any new fixes.

Comment 16 Aleksandar Kostadinov 2013-10-14 09:15:42 EDT

I do not see the issue with ER5.

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