[JBoss JIRA] Created: (JBRULES-1235) Multiple Criteria break BRMS rule editor
by Ben Truitt (JIRA)
Multiple Criteria break BRMS rule editor
----------------------------------------
Key: JBRULES-1235
URL: http://jira.jboss.com/jira/browse/JBRULES-1235
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-brms
Reporter: Ben Truitt
Assigned To: Mark Proctor
Attachments: screenshot.jpeg, screenshot1.jpeg, screenshot2.jpeg
In the BRMS - when creating a brl asset - more than one criteria causes the interface to not work properly.
Two ways to trigger:
1) Under the fact, choose "All of (AND)", then add two criteria - adding the second is the bug
2) Under the fact, add one criteria, then use the '+' icon to add another - adding the second is the bug.
I'll attach screenshots, which should help explain.
Sorry if this is a dupe - I looked, but didn't find anything like this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months
[JBoss JIRA] Created: (JBAS-4815) UnifiedInvokerProxyHA - Client instance check and assignment should be atomic
by Galder Zamarreno (JIRA)
UnifiedInvokerProxyHA - Client instance check and assignment should be atomic
-----------------------------------------------------------------------------
Key: JBAS-4815
URL: http://jira.jboss.com/jira/browse/JBAS-4815
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering, Remoting
Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
I have realised that UnifiedInvokerProxy/UnifiedInvokerProxyHA maintain a instance reference to
the InvokerLocator/Client instances to a specific invocation is using. That is, when a new target is
chosen, the unified proxy updates its Client and corresponding InvokerLocator instances (if they've
changed), and uses the Cient instance variable to make the call. As far as I can see there's no
synchronisation in the usage/assignment of Client or InvokerLocator. Proxies are meant to be thread
safe which means that multiple client app threads could be using the same proxy without any problems.
I can see all this going wrong the moment someone uses client proxies this way in a clustered
environment with round robin load balance policy. We've got no guarantee that round robin will work
correctly in these situations.
Several solutions have been discussed in
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months
[JBoss JIRA] Created: (JBCACHE-890) Custom flags per node, incorporate and consolidate some domain-specific flags
by Elias Ross (JIRA)
Custom flags per node, incorporate and consolidate some domain-specific flags
-----------------------------------------------------------------------------
Key: JBCACHE-890
URL: http://jira.jboss.com/jira/browse/JBCACHE-890
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Elias Ross
Assigned To: Manik Surtani
I believe that with java.util.EnumSet and a list of enumerations, that some of the specific flags we track on a node could be consolidated. Immediately what comes to mind are the CacheLoader flags "childrenLoaded" and "dataLoaded"
Further, I believe that some additional functionality could be incorporated.
For instance:
1. For certain internal nodes, they could be marked as "internal" or "local" and not replicated. Or possibly hidden from access entirely.
2. Some nodes might be marked as "read-only" or "non-persisted" or "non-evictable"
3. Some nodes might have special sorted ordering.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months