[JBoss JIRA] Created: (JBMESSAGING-761) Consider clean ways of taking a node out of the cluster for maintenance
by Tim Fox (JIRA)
Consider clean ways of taking a node out of the cluster for maintenance
-----------------------------------------------------------------------
Key: JBMESSAGING-761
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-761
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Fix For: 1.2.1
We should consider how the system administrator can take a node out of the cluster for maintenance without clients losing messages.
If a node is just shut down then any clients connected to that node will failover to another node, potentially losing any non persistent messages - this may not be acceptable.
We should also consider functionality on the jmx console where a server cen block the creation of any new connections, and the information such as client machine name, client id, ip address can be displayed for existing connetions. This would allow the sysadmin to contact the clients and shut them down cleanly before bringing the server down.
--
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
18 years, 10 months
[JBoss JIRA] Created: (JBMICROCONT-140) Configurator should check that fields/methods exist before trying to use them
by Adrian Brock (JIRA)
Configurator should check that fields/methods exist before trying to use them
-----------------------------------------------------------------------------
Key: JBMICROCONT-140
URL: http://jira.jboss.com/jira/browse/JBMICROCONT-140
Project: JBoss MicroContainer
Issue Type: Bug
Components: Configurator
Affects Versions: JBossMC_2_0_0 Beta
Reporter: Adrian Brock
Assigned To: Ales Justin
Fix For: JBossMC_2_0_0_CR1
Make sure the configurator is throwing reasonable error messages (not NPE)
when things are null.
e.g. the following method needs to check for null method info meaning there is no getter
public static TargettedJoinpoint getPropertyGetterJoinPoint(boolean trace, PropertyInfo info) throws Throwable
{
if (trace)
log.trace("Get property setter join point info=" + info);
if (info == null)
throw new IllegalArgumentException("Null property info");
JoinpointFactory jpf = info.getBeanInfo().getJoinpointFactory();
MethodInfo minfo = info.getGetter();
+ if (minfo == null)
+ throw new IllegalArgumentException("Property is write only");
return getMethodJoinpoint(null, jpf, minfo.getName(), null, null);
}
--
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
18 years, 10 months
[JBoss JIRA] Created: (JBRULES-446) Support rulebase configuration via jsr94 registerRuleExecutionSet properties
by Juergen none (JIRA)
Support rulebase configuration via jsr94 registerRuleExecutionSet properties
----------------------------------------------------------------------------
Key: JBRULES-446
URL: http://jira.jboss.com/jira/browse/JBRULES-446
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JSR94
Affects Versions: 3.0.4
Reporter: Juergen none
Assigned To: Mark Proctor
Priority: Minor
Is it possible to support rulebase configuration via jsr94 registerRuleExecutionSet properties?
Suggestion:
- new property in
org.drools.jsr94.rules.Constants.java:41:
//jh: added to support handing a rulebase config via jsr94
/** <code>RuleExecutionSet</code> rulebase config constant. */
public static final String RES_CONFIG = "javax.rules.admin.RuleExecutionSet.config";
- modification of method (probably secure against ClassCastException)
org.drools.jsr94.rules.admin.RuleExecutionSetImpl.java:118:RuleExecutionSetImpl(...):
//jh: support rulebase configuration via jsr94
final org.drools.reteoo.ReteooRuleBase ruleBase = new org.drools.reteoo.ReteooRuleBase((org.drools.RuleBaseConfiguration)properties.get(org.drools.jsr94.rules.Constants.RES_CONFIG), new Jsr94FactHandleFactory() );
/*
final org.drools.reteoo.ReteooRuleBase ruleBase = new org.drools.reteoo.ReteooRuleBase( new Jsr94FactHandleFactory() );
*/
--
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
18 years, 10 months
[JBoss JIRA] Created: (JBRULES-528) Implementation for Decision tables, and compiler options in DroolsJSR
by Vignesh S (JIRA)
Implementation for Decision tables, and compiler options in DroolsJSR
---------------------------------------------------------------------
Key: JBRULES-528
URL: http://jira.jboss.com/jira/browse/JBRULES-528
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JSR94
Reporter: Vignesh S
Assigned To: Mark Proctor
Priority: Optional
The implementation for Decision tables and compiler options can be given in drools JSR and to my knowledge it can done easily in the method
public RuleExecutionSet createRuleExecutionSet(final Reader ruleExecutionSetReader,
final Map properties) throws RuleExecutionSetCreateException
org.drools.jsr94.rules.admin.LocalRuleExecutionSetProviderImpl class
By adding one more condition for ".xsl" for decision tables
and setting a new property for the compiler in map parameter
--
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
18 years, 10 months
[JBoss JIRA] Created: (JBPORTAL-1126) CMS needs to store contributing version for new versions of pages
by Alex Pinkin (JIRA)
CMS needs to store contributing version for new versions of pages
-----------------------------------------------------------------
Key: JBPORTAL-1126
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1126
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Portal CMS
Affects Versions: 2.4 Final
Reporter: Alex Pinkin
Assigned To: Roy Russo
-CMS needs to store contributing version for new versions of pages (1.1 was created from 1.0, etc).
To prevent locking the edit of a content item, it is useful to allow multiple drafts to be created of a content item. This situation can cause problems for approvers if there are multiple drafts needing approval. It would be helpful if approvers could see what version was the contributing version for a particular content item version.
--
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
18 years, 10 months
[JBoss JIRA] Created: (JBRULES-573) EqualityAssertMapComparator does not work with JSR94 Fact Handles
by Juergen none (JIRA)
EqualityAssertMapComparator does not work with JSR94 Fact Handles
-----------------------------------------------------------------
Key: JBRULES-573
URL: http://jira.jboss.com/jira/browse/JBRULES-573
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 3.0.5
Environment: java 1.5.0_09
Reporter: Juergen none
Assigned To: Mark Proctor
Equal objects are asserted multiple times via jsr94 interface
Using jsr94 interface to use drools stateful rule session
Assert behaviour set to equality:
PROPERTY_ASSERT_BEHAVIOR = RuleBaseConfiguration.WM_BEHAVIOR_EQUALITY
fact handle factory creates org.drools.jsr94.rules.Jsr94FactHandle objects
BUT:
org.drools.common.EqualityAssertMapComparator::hashCodeOf()
obj.getClass() == this.factHandleClass is false because
this.factHandleClass is DefaultFactHandle and
obj.getClass() is Jsr94FactHandle
--> so instead of hashcode of object wrapped by handle, hashcode of facthandle object is used --> equal objects are asserted multiple times
GUESS: either
- obj.getClass() instanceof this.factHandleClass or
- this.factHandleClass should be set to Jsr94FactHandle?
--
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
18 years, 10 months