Bug 1315380 - One server shown twice in Servers list
Summary: One server shown twice in Servers list
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Plugin -- JBoss EAP 7
Version: JON 3.3.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Simeon Pinder
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-07 15:34 UTC by Hayk Hovsepyan
Modified: 2016-03-07 15:45 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-07 15:37:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Hayk Hovsepyan 2016-03-07 15:34:45 UTC
Description of problem:
When server is started in security mode (2-way SSL), imported into JON servers, and then restarted in unsecure mode and again imported, it shows two servers in Servers list.

Version-Release number of selected component (if applicable):
Version 3.3
Update-03
DR01 
jon-plugin-pack-eap-3.3.0.GA.zip

How reproducible:
always

Steps to Reproduce:
1. Configure EAP7  server to 2-way SSL and start it.
2. Agent monitoring EAPs is running and registered with the server.
3. In discovery queue of JON server it will show this server.
4. Import that server and verify that it is UP.
5. Stop that EAP7 server and start it in unsecure mode.
6. In discovery queue of JON server it will be shown with other port (xxx90).
7. Import it.
8. It will show one of servers UP and the second one as a DOWN.
9. Fix the DOWN server, by changing it's connection settings, such as port, 
"Start Script Arguments" to make it UP.

There will be 2 same servers shown UP, both with the same port, but with different Key.
1st key is: hostConfig: /home/hudson/jboss-eap7-standalone/standalone/configuration/standalone-full-secured-changed.xml
2nd key is: hostConfig: /home/hudson/jboss-eap7-standalone/standalone/configuration/standalone-full-changed.xml

1st key is pointing to wrong configuration file, s server is restarted in unsecure mode, but it is just a key.

According to discussion with developers, it is expected behavior.
This is by design. Same way if server is restarted from standalone-full to standalone.

Comment 1 Hayk Hovsepyan 2016-03-07 15:45:50 UTC
Similar to https://bugzilla.redhat.com/show_bug.cgi?id=1315376


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