[JBoss JIRA] Created: (JBMESSAGING-1823) Selector and paging : messages are not loaded from storage
by CYRIL GERBIER (JIRA)
Selector and paging : messages are not loaded from storage
-----------------------------------------------------------
Key: JBMESSAGING-1823
URL: https://jira.jboss.org/browse/JBMESSAGING-1823
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.5.GA, 1.4.0.SP3.CP10, 1.4.0.SP3.CP09, 1.4.0.SP3.CP08, 1.4.0.SP3.CP07, 1.4.0.SP3.CP06, 1.4.0.SP3.CP05, 1.4.0.SP3.CP04, 1.4.0.SP3_CP03, 1.4.0.SP3.CP02, 1.4.0.SP3_CP01, 1.4.0.SP3
Environment: Jboss Messaging 1.4.0SP3 (also 1.4.5.GA)
Reporter: CYRIL GERBIER
Attachments: SelectorPagingPb.zip
My problem concern the use of selector on paging queues: as long as the first message in memory is not consumed, jboss messaging 1.4.0 SP3 (also 1.4.5.GA) doesn't load messages from storage.
For example, I create a queue with following paging parameters: FullSize=20, PageSize=10, DownCacheSize=10. I send 35 messages in this queue (with JMS property test set from 0 to 35). So I have 20 messages in memory and 15 on storage.
Then, I try to consume messages except the one with test=2. I use selector on test property to consume my messages.
The result is I can consume all messages in memory, but I can't for those in storage: they are staying in storage, and JBoss Messaging doesn't load these messages from storage.
Actually, the messages in storage are loaded only when first message in memory is consumed. In my case, I don't consume message 2 which is the first message in memory.
How avoid this behaviour that block all my product with thousands of messages blocked in my queue?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBRULES-2718) Ruleflows are not working correctly in Stateless session
by Grégoire Botquin (JIRA)
Ruleflows are not working correctly in Stateless session
--------------------------------------------------------
Key: JBRULES-2718
URL: https://jira.jboss.org/browse/JBRULES-2718
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 5.1.1.FINAL
Environment: Windows 7
Reporter: Grégoire Botquin
Assignee: Mark Proctor
We are currently migrating from 5.0.1 to 5.1.1. and our RuleFlows are not working anymore. After some investigations it seems it could be related to the knowledgesession type (Statefull / Stateless). When launching a ruleflow in stateless session, it seems that the process stops it's execution after the first RuleFlowGroup found in the flow (maybe after some other node types (?)), and that without any reason nor exception/error trace.
In attach, I made a ruleflow sample with two nodes (one ruleflow group and one script node). The nodes are only making a simple System.out.println. When executing it in Statefull session, we have two outputs. When executing it in Stateless session, there is only one output, this one of the RuleFlowGroup. The script node has not been executed as it should be. No exceptions were found in logs.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBRULES-2223) ArrayIndexOutOfBoundsException in AbstractRuleBase.getStatefulSessions()
by Assen Todorov (JIRA)
ArrayIndexOutOfBoundsException in AbstractRuleBase.getStatefulSessions()
------------------------------------------------------------------------
Key: JBRULES-2223
URL: https://jira.jboss.org/jira/browse/JBRULES-2223
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.7
Reporter: Assen Todorov
Assignee: Mark Proctor
The following exception is thrown on a multithreaded application, based on Terracotta & JBoss Drools (4.0.7).
{code}
java.lang.ArrayIndexOutOfBoundsException: 0
at org.drools.util.ObjectHashSet.toArray(ObjectHashSet.java:152)
at org.drools.common.AbstractRuleBase.getStatefulSessions(AbstractRuleBase.java:724)
.......
{code}
The code :
{code}
/**
* Creates a new rule base if necesarry.
* @param aRuleSet the rule set for the new rule base.
* @throws RuleConversionException if the rule engine has a problem with rule set compilation and loading.
*/
private void createRuleBase(final RuleSet aRuleSet) throws RuleConversionException
{
Check.notNull(aRuleSet, "aRuleSet");
final String code = aRuleSet.getCode();
Check.notNull(code, "aRuleSet.getCode()");
Check.notEmpty(code, "aRuleSet.getCode()");
final ECRC ecrc = new ECRC();
ecrc.update(code);
final long crc = ecrc.getValue();
synchronized(ruleBaseCache)
{
ruleBase = ruleBaseCache.get(crc);
if(ruleBase == null)
{
ruleBase = loadRuleBaseFromCode(code);
ruleBaseCache.put(crc, ruleBase);
}
else {
// rulebase already exist
final StatefulSession[] sessions = ruleBase.getStatefulSessions();
if(sessions.length > 0) {
// old sessions (working memories exist)
for(StatefulSession session: sessions) {
// clear the working memory
session.dispose();
}
}
}
}
}
{code}
The class where this method is defined, is declared as _instrumented-classes_ in the Terracotta configuration.
Hope this helps !
--
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
15 years, 3 months