[JBoss JIRA] Created: (JBRULES-1856) Ateempt to edit a rule before importing mode/fact classes can appear to hang UI
by Len DiMaggio (JIRA)
Ateempt to edit a rule before importing mode/fact classes can appear to hang UI
--------------------------------------------------------------------------------
Key: JBRULES-1856
URL: https://jira.jboss.org/jira/browse/JBRULES-1856
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-guvnor
Affects Versions: 5.0.0.M2
Reporter: Len DiMaggio
Assignee: Mark Proctor
Attachments: M2-create_rule_with_no_facts.png
Seeing this problem with BRMS with Drools 5 M2 and as built from trunk on Nov 21.
If a user attempts to create a new rule, without first importing a model .jar to provide facts to be used in the rule, then attempting to add a condition to that rule results in the "Add a condition to the rule" dialog being displayed - but the UI appears to hang.
The UI is not really hung as the user can just close the "Add a condition to the rule" dialog to continue.
See attached screenshot.
To recreate:
* login to BRMS
* create a catageory
* create a package
* create a rule - attempt to edit the WHEN clause of the rule
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 7 months
[JBoss JIRA] Moved: (JBJCA-30) Allow flushing of connection pool on fatal connection events
by Jesper Pedersen (JIRA)
[ https://jira.jboss.org/jira/browse/JBJCA-30?page=com.atlassian.jira.plugi... ]
Jesper Pedersen moved JBAS-5824 to JBJCA-30:
--------------------------------------------
Project: JBoss JCA (was: JBoss Application Server)
Key: JBJCA-30 (was: JBAS-5824)
Component/s: Core
(was: JCA service)
Fix Version/s: (was: JBossAS-5.1.0.Beta1)
Security: (was: Public)
> Allow flushing of connection pool on fatal connection events
> ------------------------------------------------------------
>
> Key: JBJCA-30
> URL: https://jira.jboss.org/jira/browse/JBJCA-30
> Project: JBoss JCA
> Issue Type: Feature Request
> Components: Core
> Reporter: Chris Bredesen
> Assignee: Jesper Pedersen
> Priority: Minor
>
> As an alternative to validating connections (either on borrow or in the background), we could implement a feature similar to WebSphere's purge policy. The idea is that we can assume in certain cases that a single fatal exception means every connection in the pool will subsequently throw fatal exceptions. Such is the case in situations where the connected database has been restarted. Rather than implementing a purge policy per se, we would implement an "on fatal behavior". The behavior could define one of three actions to be taken when a fatal exception is encountered:
> 1. Destroy single connection (equivalent to WAS policy of "single connection")
> 2. Initiate validation run
> 3. Flush entire pool (equivalent to WAS policy of "whole pool")
> Note that all of the above (indeed this entire feature) requires the use of an ExceptionSorter.
> In terms of implementation, I see two possibilities:
> 1. Implement this feature as an MBean, which means we'd need some way of registering connection event listeners outside JCA.
> 2. Implement this feature as part of the JCA adapter which I think makes more sense, but is more impactful.
> Regarding #1, if it's possible to simply add a way to register connection event listeners from outside the adapter, that could become its own feature request and this feature simply turns into an MBean that can be implemented separately.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 7 months