[JBoss JIRA] (WFLY-9553) PooledConnectionFactoryAdd adds a resource with no registration
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-9553?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-9553:
-----------------------------------
Description:
When working on WFCORE-3415 I was investigating discrepancies in mbean counts generated via the method in that fix vs current code. I discovered one in WildFly's messaging-activemq that is a result of a statistics resource being added to the resource tree even if attribute that triggers registration of the related ManagementResourceRegistration isn't set. So we have an undescribed resource.
This likely has no other impact than a slightly inaccurate result from MBeanServerConnection.getMBeanCount() but we don't want this kind of thing anyway.
was:
When working on WFCORE-2930 I was investigating discrepancies in mbean counts generated via the method in that fix vs current code. I discovered one in WildFly's messaging-activemq that is a result of a statistics resource being added to the resource tree even if attribute that triggers registration of the related ManagementResourceRegistration isn't set. So we have an undescribed resource.
This likely has no other impact than a slightly inaccurate result from MBeanServerConnection.getMBeanCount() but we don't want this kind of thing anyway.
> PooledConnectionFactoryAdd adds a resource with no registration
> ---------------------------------------------------------------
>
> Key: WFLY-9553
> URL: https://issues.jboss.org/browse/WFLY-9553
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 11.0.0.Final
> Reporter: Brian Stansberry
> Assignee: Jeff Mesnil
> Priority: Minor
>
> When working on WFCORE-3415 I was investigating discrepancies in mbean counts generated via the method in that fix vs current code. I discovered one in WildFly's messaging-activemq that is a result of a statistics resource being added to the resource tree even if attribute that triggers registration of the related ManagementResourceRegistration isn't set. So we have an undescribed resource.
> This likely has no other impact than a slightly inaccurate result from MBeanServerConnection.getMBeanCount() but we don't want this kind of thing anyway.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (DROOLS-2147) Type test error
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2147?page=com.atlassian.jira.plugi... ]
Edson Tirelli updated DROOLS-2147:
----------------------------------
Sprint: 2017 Week 47-48
> Type test error
> ---------------
>
> Key: DROOLS-2147
> URL: https://issues.jboss.org/browse/DROOLS-2147
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Affects Versions: 7.4.1.Final
> Reporter: Edson Tirelli
> Assignee: Matteo Mortari
> Fix For: 7.5.0.Final
>
> Attachments: TypeTestError.dmn
>
>
> Attached model is raising the following runtime error:
> {quote}Error while evaluating node 'People groups': the declared result type is 'DMNType\{ http://www.trisotech.com/dmn/definitions/_cbdacb7b-f72d-457d-b4f4-54020a0... : tListPeople }' but the actual value '\[\[\{Age=20, Name=Ana}, \{Age=22, Name=Bob}], \[\{Age=27, Name=Charlie}, \{Age=29, Name=Daniel}], \[\{Age=31, Name=Edson}, \{Age=32, Name=Fred}]]' is not an instance of that type{quote}
> The engine should not generate such error as the type is correct.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months