Bug 1149093 - In JON, JDG server 6.4.0 reports version 6.3.0.GA which is wrong (kill version.txt from EAP)
Summary: In JON, JDG server 6.4.0 reports version 6.3.0.GA which is wrong (kill versio...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: JON Plugin
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ER8
: 6.4.0
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks: jdg64-GA-Blockers 1183064
TreeView+ depends on / blocked
 
Reported: 2014-10-03 08:28 UTC by Tomas Sykora
Modified: 2015-01-28 13:30 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tomas Sykora 2014-10-03 08:28:17 UTC
I am sure that there is 6.4.0.ER1 installed on agent machines, however, JON gui reports there is 6.3.0.GA version of JDG server. This is wrong and I need to look at the cause of this issue. 

The strange thing is that in current JDG tag/branch there is NO "6.3.0.GA" string so I suspect maybe JON decisioning mechanisms or interference with EAP server or EAP plugin. 

No JIRA this time, product-related issue.

Comment 2 Tomas Sykora 2014-10-07 12:05:54 UTC
We state in server_home/version.txt:

Red Hat JBoss Enterprise Application Platform - Version 6.3.0.GA

Which obviously should be:

Red Hat JBoss Data Grid - Version 6.4.0 (+ current release)

However, this does not need to solve the problem completely. Experimenting...

Comment 3 Tomas Sykora 2014-10-07 12:16:32 UTC
Done with experimenting...

This works pretty well. We need to state proper product name and version in version.txt file in server_home folder. 

That's all. 


Just a note: 

https://github.com/rhq-project/rhq/blob/master/modules/plugins/jboss-as-7/src/main/java/org/rhq/modules/plugins/jbossas7/BaseProcessDiscovery.java#L688

explain how version discovery works in RHQ.

Comment 4 Tomas Sykora 2014-10-07 12:54:57 UTC
version.txt file comes from EAP and needs to be removed.

Comment 6 Tomas Sykora 2015-01-02 11:12:01 UTC
This has been fixed and works like a charm in 6.4.0.ER8 build. Thanks Tristan and Dave!


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