Bug 1106658 - (6.4.0) management console does not show all connectors - JBoss EAP 6.2.2
Summary: (6.4.0) management console does not show all connectors - JBoss EAP 6.2.2
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console
Version: 6.2.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DR1
: EAP 6.4.0
Assignee: Harald Pehl
QA Contact: Pavel Jelinek
URL:
Whiteboard:
Depends On:
Blocks: 1129016 1131419
TreeView+ depends on / blocked
 
Reported: 2014-06-09 17:03 UTC by Leticia Konno
Modified: 2019-08-19 12:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1131419 (view as bug list)
Environment:
Last Closed: 2019-08-19 12:38:46 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker HAL-427 0 Major Resolved Management console does not show all connectors 2016-02-25 11:26:57 UTC

Description Leticia Konno 2014-06-09 17:03:41 UTC
Description of problem:

Configure more than 10 connectors in Profiles > full > Messaging > Connections > Default View > Connector.

The connectors table only shows 10 items. It is possible to see all connectors using the following command in the CLI. Also, the table for Acceptors do not page too. 

ls -l /profile=full/subsystem=messaging/hornetq-server=default/remote-connector

Version-Release number of selected component (if applicable):
JBoss EAP 6.2.2

Comment 2 JBoss JIRA Server 2014-06-27 20:29:22 UTC
Harald Pehl <hpehl> updated the status of jira HAL-427 to Coding In Progress

Comment 3 JBoss JIRA Server 2014-06-27 20:45:34 UTC
Harald Pehl <hpehl> updated the status of jira HAL-427 to Resolved

Comment 10 Kabir Khan 2014-08-24 11:03:09 UTC
Appears fixed by HAL 2.2.10 upgrade https://bugzilla.redhat.com/show_bug.cgi?id=1129016. Setting to MODIFIED.

Comment 11 Pavel Jelinek 2014-09-29 08:48:30 UTC
Verified for EAP 6.4.0.DR2 that paging fixed the issue.


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