[JBoss JIRA] Created: (JGRP-1243) FD_SOCK: reduce number of messages sent on a suspicion
by Bela Ban (JIRA)
FD_SOCK: reduce number of messages sent on a suspicion
------------------------------------------------------
Key: JGRP-1243
URL: https://jira.jboss.org/browse/JGRP-1243
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 2.10.1, 2.11
- When B suspects C, B multicasts a SUSPECT(C) message
- Everyone receives the SUSPECT(C) message and passes it up and down the stack as a SUSPECT(C) event
- VERIFY_SUSPECT *on every member* sends one (or more) ARE_YOU_DEAD messages to C
- C replies to the sender with a I_AM_NOT_DEAD messages, or not if crashed
- However, only the coordinator (or next in line) actually processes the SUSPECT(C) event in GMS !
--> All of the VERIFY_SUSPECT processing is superfluous unless it is the coord or next-in-line !
The number of messages used for a false suspicion are (1 SUSPECT mcast) + ((N-1) ARE_YOU_DEAD unicasts) + ((N-1) I_AM_NOT_DEAD unicasts)) !
SOLUTION:
- The SUSPECT(C) message could be sent as a unicast only to the coordinator and the next-in-line member. Maybe we could use a max_rank=2 for this, similar to the suggested solution for FD_ALL ? This would be good for non multicast based transports, e.g. TCP
- The SUSPECT(C) message is multicast to everyone, but only the coord and next-in-line start the VERIFY_SUSPECT processing
Issue: if we have {A,B,C,D,E}, what happens if A,B and C crash at the same time ?
- E's connection to A closes: E sends a SUSPECT(A) to B and C (excluding suspected A)
--> B and C are dead and won't process the message !
- Then E suspects B and sends a SUSPECT(A,B) to C and D (excluding suspected A and B)
- C adds A and B to its suspect list and finds out it is the next-in-line
- C then runs the VERIFY_SUSPECT protocol
- C passes the SUSPECT(A,B) event up the stack
- C becomes the new coord
--
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
14 years
[JBoss JIRA] Commented: (JBAS-8483) errors injecting the Weld BeanManager.
by Marius Bogoevici (JIRA)
[ https://jira.jboss.org/browse/JBAS-8483?page=com.atlassian.jira.plugin.sy... ]
Marius Bogoevici commented on JBAS-8483:
----------------------------------------
Nimo,
Would you mind uploading an example for reproducing this?
> errors injecting the Weld BeanManager.
> --------------------------------------
>
> Key: JBAS-8483
> URL: https://jira.jboss.org/browse/JBAS-8483
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Weld/CDI
> Affects Versions: 6.0.0.M5
> Environment: jboss as 6 milestone 5
> Reporter: nimo stephan
> Assignee: Marius Bogoevici
>
> The same weld-war does work in jboss as 6 milestone 4. Deploying it in jboss as 6 milestone 5 does work, only when invoking a bean, then weld throws exception:
> (The full stacktrace can be seen here: http://community.jboss.org/thread/157055)
> 10:57:33,719 SEVERITY [javax.enterprise.resource.webcontainer.jsf.application] javax.ejb.EJBException: java.lang.RuntimeException: Unable to inject jndi dependency: env/org.jboss.weld.integration.ejb.SessionBeanInterceptor/beanManager into property org.jboss.weld.integration.ejb.SessionBeanInterceptor.beanManager: MyWAR not bound: javax.faces.el.EvaluationException: javax.ejb.EJBException: java.lang.RuntimeException: Unable to inject jndi dependency: env/org.jboss.weld.integration.ejb.SessionBeanInterceptor/beanManager into property org.jboss.weld.integration.ejb.SessionBeanInterceptor.beanManager: MyWAR not bound
> at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102) [:2.0.2-FCS]
--
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
14 years
[JBoss JIRA] Created: (JBRULES-2326) request to improve upon error message received from invalid rule syntax (currently getting NPE)
by Jeremy Ary (JIRA)
request to improve upon error message received from invalid rule syntax (currently getting NPE)
-----------------------------------------------------------------------------------------------
Key: JBRULES-2326
URL: https://jira.jboss.org/jira/browse/JBRULES-2326
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 5.1.0.M1
Reporter: Jeremy Ary
Assignee: Mark Proctor
My (albeit improper) rule syntax that caused the NPE error:
when
QueueList ( queueIds contains 1 )
( not EventList ( events contains 1 )
|| ( $eventList : EventList ( events contains 1 )
&& RfEvent ( eventTypeId == 1, lastActivationLong after[-1h] sessionTime ) from $eventList.events ) )
then
modify (eventList) { add(1) }
Stack Trace:
org.drools.runtime.rule.ConsequenceException: java.lang.NullPointerException
at org.drools.runtime.rule.impl.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:23)
at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:943)
at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:885)
at org.drools.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1086)
at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:660)
at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:627)
at org.drools.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:183)
at com.famc.service.RuleFlowRunner.main(RuleFlowRunner.java:118)
Caused by: java.lang.NullPointerException
at org.drools.base.mvel.DroolsMVELFactory.getTupleObjectFor(DroolsMVELFactory.java:182)
at org.drools.base.mvel.DroolsMVELFactory.setContext(DroolsMVELFactory.java:176)
at org.drools.base.mvel.MVELConsequence.evaluate(MVELConsequence.java:57)
at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:934)
... 6 more
Request for ticket:
[10:19] <etirelli> jary: raising a NPE is clearly a bug, but the reason is that you have modify(eventList) instead of modify($eventList)... in any case, the way you authored the rule is not ideal
[10:19] <etirelli> jary: could you please open a JIRA so that we can provide an appropriate error message, please?
--
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
14 years
[JBoss JIRA] Created: (JBRULES-2268) Unknown Parser Error when spreading rule condition over multiple lines
by Jeremy Ary (JIRA)
Unknown Parser Error when spreading rule condition over multiple lines
----------------------------------------------------------------------
Key: JBRULES-2268
URL: https://jira.jboss.org/jira/browse/JBRULES-2268
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler
Affects Versions: 5.0.0.CR1
Environment: XP-SP3, eclipse 3.4.2, 5.0.0.CR1
Reporter: Jeremy Ary
Assignee: Mark Proctor
Full message:
Unknown error while parsing. This is a bug. Please contact the Development team.
To recreate:
I broke a condition over multiple lines and mistakenly misgrouped my parentheses, leading to an unknown error while parsing:
{code}
rule "recreate bug"
when
Loan ( amount >= 175000 )
&& ( program == "FHA" ) )
then
modify (queueList) { add (QueueIds.UWENTRY) }
end
{code}
When corrected to the following, the rule is parsed properly:
{code}
rule "recreate bug"
when
Loan ( ( amount >= 175000 )
&& ( program == "FHA" ) )
then
modify (queueList) { add (QueueIds.UWENTRY) }
end
{code}
--
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
14 years