Bug 911325 - [EAP 6.1] adding JVM definition to server-group fails
Summary: [EAP 6.1] adding JVM definition to server-group fails
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Plugin -- JBoss EAP 6
Version: JON 3.1.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: JON 3.2.0
Assignee: Thomas Segismont
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 911633 915469
TreeView+ depends on / blocked
 
Reported: 2013-02-14 17:59 UTC by Libor Zoubek
Modified: 2015-11-02 00:43 UTC (History)
3 users (show)

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


Attachments (Terms of Use)

Description Libor Zoubek 2013-02-14 17:59:47 UTC
Description of problem:


Version-Release number of selected component (if applicable):
JON 3.1.2 GA + EAP 6.1.DR4

How reproducible:always


Steps to Reproduce:
1. import EAP 6.1 in domain mode
2. create a new server-group resource
3. add a JVM Definition resource child to this new server-group
  
Actual results: JVM Definition resource creation fails with result:

Read timed out, rolled-back=false, rolled-back=false

Expected results:


Additional info: This is weird. If you do step 2. JON will claim this server-group was created and exists. If you check this in EAP 6.1 CLI, it will also look, this group exists 
Execute operation : {
"address" => [],
"operation" => "read-children-names",
"child-type" => "server-group"
}
but, if you log in to admin console, new server group is not visible, it might be EAP 6.1 issue.

Comment 1 Thomas Segismont 2013-02-20 20:02:54 UTC
Cannot reproduce. Can you try it again manually and provide logs, stack traces, http stream dumps? Thanks

Comment 2 Thomas Segismont 2013-05-02 15:47:08 UTC
Set to ON_QA waiting for input from Libor

Comment 3 Libor Zoubek 2013-05-03 12:06:35 UTC
verified (no longer able to reproduce) on Version: 4.7.0-SNAPSHOT  Build Number: 248cb85  and EAP 6.1.0.ER6


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