[JBoss JIRA] Created: (JBAS-9276) Make the annotation @Management works in association with @Singleton
by Laurent Vandwalle (JIRA)
Make the annotation @Management works in association with @Singleton
--------------------------------------------------------------------
Key: JBAS-9276
URL: https://issues.jboss.org/browse/JBAS-9276
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMX
Affects Versions: 6.0.0.Final
Reporter: Laurent Vandwalle
Fix For: 6.1.0
In JBoss 5.1, the use of @Management in association with @Service allowed to manage (JMX Management) the singleton EJB.
In JBoss 6.0 Final, @Service annotations can be replace by the JEE6 standard annotation @Singleton.
The problem is that the @Management annoation does not work if used in association with the @Singleton annotation.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (JBRULES-2917) matching of field==v1 || field==v2 breaks when variable binding is added
by Wolfgang Laun (JIRA)
matching of field==v1 || field==v2 breaks when variable binding is added
------------------------------------------------------------------------
Key: JBRULES-2917
URL: https://issues.jboss.org/browse/JBRULES-2917
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.2.0.M1
Reporter: Wolfgang Laun
Assignee: Mark Proctor
Priority: Critical
Fix For: 5.2.0.M1
class Assignment { Class source, target; }
The following rule fails to match when target == java.lang.Object.class
rule ObjectIsAssignable
when
Assignment( $t: target == (java.lang.Object.class) || target == source )
then
end
The following rule fails to match when target == source
rule ObjectIsAssignable
when
Assignment( $t: target == source || target == (java.lang.Object.class) )
then
end
The error does not occur if the binding ($t) is omitted.
See Workaround.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (JBRULES-2982) Massive performance degradation from 5.2.0.M1 to 5.2.0.M2
by Roman Novak (JIRA)
Massive performance degradation from 5.2.0.M1 to 5.2.0.M2
---------------------------------------------------------
Key: JBRULES-2982
URL: https://issues.jboss.org/browse/JBRULES-2982
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core (expert)
Affects Versions: 5.2.0.M2
Reporter: Roman Novak
Assignee: Mark Proctor
Priority: Critical
the drools-planner SolutionInitializer takes 75 minutes to complete im 5.2.0.M2
5.2.0.M1 took 9,5 Minutes
It also seems that accumulation queries with init, action, result sections break down completely in performance.
The following query takes now 3 minutes 45 secs to complete. Before it was ~1 sec.
The cardinalities:
PostingPeriodOpt = 5
MediumLocationOpt = 25000
MediumBookingOpt = 13000
query "queryMediumPartlyTaken"
$pp : PostingPeriodOpt()
$mlo : MediumLocationOpt(mTypeId == $pp.mTypeId)
$mp: MediumPeriodUsage( subOptimal > 0 ) from accumulate(
$mbo : MediumBookingOpt ( mediId == $mlo.mediId, eval(timeInterval.overlaps($pp.getCycle())) ),
init ( MediumPeriodUsage $mpu = new MediumPeriodUsage($mlo, $pp); ),
action( $mpu.addBooking( $mbo.getIndexRange() ); ),
result( $mpu )
)
end
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month