Bug 920253 - [IPv6] platform-mbean subsytem has no children
Summary: [IPv6] platform-mbean subsytem has no children
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Plugin -- JBoss EAP 6
Version: JON 3.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: JON 4.0.0
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 919199
TreeView+ depends on / blocked
 
Reported: 2013-03-11 15:58 UTC by Libor Zoubek
Modified: 2019-06-24 15:06 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-06-24 15:06:03 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Libor Zoubek 2013-03-11 15:58:48 UTC
Description of problem: When EAP6 standalone is listening on IPv6 interface, JON does not discover platform-mbean correctly.


Version-Release number of selected component (if applicable):
JON 3.2.0.Alpha + EAP 6.0.GA

How reproducible:always


Steps to Reproduce:
1.start EAP6 standalone listening on IPv6 : standalone.sh -Djava.net.preferIPv4Stack=false -bmanagement ::1
2. import it
3. got to platform-mbean child resource
  
Actual results:
1. platform-mbean has no children at all (usually it has child resources for monitoring threads,memory etc of underlying JVM)
2. Uncaught exception is thrown when you try to visit 'Configuration' tab

 stack: TypeError: Cannot call method 'getOrCreateJsObj' of null
    at $disable (http://10.16.23.160:7080/coregui/org.rhq.enterprise.gui.coregui.CoreGUI/55A8218A3E17D2D2DE0809B2C0D7F58D.cache.html:14761:28)
    at $onSuccess_354 (http://10.16.23.160:7080/coregui/org.rhq.enterprise.gui.coregui.CoreGUI/55A8218A3E17D2D2DE0809B2C0D7F58D.cache.html:137979:5)

Expected results: platform-mbean is correctly discovered and can be monitored, no errors appear when visiting it's configuration


Additional info:

Comment 2 Filip Brychta 2019-06-24 15:06:03 UTC
JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121.
This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.


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