[JBoss JIRA] (WFLY-9222) Query MBean names takes forever when having many loggers and many classes
by Steffen Czymmeck (JIRA)
[ https://issues.jboss.org/browse/WFLY-9222?page=com.atlassian.jira.plugin.... ]
Steffen Czymmeck updated WFLY-9222:
-----------------------------------
Steps to Reproduce:
1. Extract a fresh copy of WildFly
2. Open standalone/configuration/standalone.xml and configure ~300 loggers with unique names (see attachment)
3. Run WildFly and deploy an ear with many classes (see attachment -> 10.000 empty classes spread across 100 jar files)
4. Open jconsole and click the MBeans tab
was:
1. Extract a fresh copy of WildFly
2. Open standalone/configuration/standalone.xml and configure ~300 loggers with unique names (see attachment)
3. Run WildFly and deploy an ear with many classes (see attachment -> 10.000 empty classes spread to 100 jar files)
4. Open jconsole and click the MBeans tab
> Query MBean names takes forever when having many loggers and many classes
> -------------------------------------------------------------------------
>
> Key: WFLY-9222
> URL: https://issues.jboss.org/browse/WFLY-9222
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.1.0.Final
> Environment: Windows 7 and Windows 10
> Reporter: Steffen Czymmeck
> Assignee: Jason Greene
> Attachments: manyClasses.ear, standalone.xml
>
>
> If you configure many loggers (~300) and deploy a rather big ear with many classes, it takes forever to query mbean names with
> javax.management.MBeanServer#queryNames or via. jconsoles MBeans tab.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9222) Query MBean names takes forever when having many loggers and many classes
by Steffen Czymmeck (JIRA)
Steffen Czymmeck created WFLY-9222:
--------------------------------------
Summary: Query MBean names takes forever when having many loggers and many classes
Key: WFLY-9222
URL: https://issues.jboss.org/browse/WFLY-9222
Project: WildFly
Issue Type: Bug
Affects Versions: 10.1.0.Final
Environment: Windows 7 and Windows 10
Reporter: Steffen Czymmeck
Assignee: Jason Greene
Attachments: manyClasses.ear, standalone.xml
If you configure many loggers (~300) and deploy a rather big ear with many classes, it takes forever to query mbean names with
javax.management.MBeanServer#queryNames or via. jconsoles MBeans tab.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (DROOLS-1702) I am unable to create same repository name in another Organizational unit.
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1702?page=com.atlassian.jira.plugi... ]
Michael Anstis resolved DROOLS-1702.
------------------------------------
Assignee: Michael Anstis (was: Edson Tirelli)
Resolution: Rejected
This is not a bug; but my design.
Repository names are scoped at the workbench level and not the OU level.
This design allows the same repository to be shared across different OUs.
> I am unable to create same repository name in another Organizational unit.
> ---------------------------------------------------------------------------
>
> Key: DROOLS-1702
> URL: https://issues.jboss.org/browse/DROOLS-1702
> Project: Drools
> Issue Type: Bug
> Reporter: Jai Nath Gupta
> Assignee: Michael Anstis
>
> Hi,
> I am unable to create same repository name in another Organizational unit.
> Example:
> OrganizationaUnit: HDFCBank
> Repository: Insurance
> Project:PolicyRule
> OrganizationaUnit: ICICIBank
> Repository: Insurance
> Project:PolicyRule
> I am unable to create Insurance Repository for ICICIBank.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (DROOLS-1702) I am unable to create same repository name in another Organizational unit.
by Jai Nath Gupta (JIRA)
Jai Nath Gupta created DROOLS-1702:
--------------------------------------
Summary: I am unable to create same repository name in another Organizational unit.
Key: DROOLS-1702
URL: https://issues.jboss.org/browse/DROOLS-1702
Project: Drools
Issue Type: Bug
Reporter: Jai Nath Gupta
Assignee: Edson Tirelli
Hi,
I am unable to create same repository name in another Organizational unit.
Example:
OrganizationaUnit: HDFCBank
Repository: Insurance
Project:PolicyRule
OrganizationaUnit: ICICIBank
Repository: Insurance
Project:PolicyRule
I am unable to create Insurance Repository for ICICIBank.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months