4:04 p.m.
Add support for fireUntilHalt to BusinessRulesProcessor
-------------------------------------------------------
Key: JBESB-2882
URL: https://jira.jboss.org/jira/browse/JBESB-2882
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.6
Reporter: Jeff DeLong
To better support CEP, an ESB Rule Service should be able to create the KnowledgeBase,
StatefulKnowledgeSession, etc, and then execute fireUntilHalt. This will cause the thread
to block, and the rules engine will continue to process (in a separate thread). Either the
same ESB Service, or different service with access to the StatefulKnowledgeSession, can
then receive messages / events and insert them into the StatefulKnowledgeSession.
FireUntil Halt provides two important benefits to a CEP application. First it provides
more timely rules firing. Even more important, it support the case where the absence of
incoming events should cause rules to fire.
--
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
8:48 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-2882) Add support for fireUntilHalt to BusinessRulesProcessor
[
https://jira.jboss.org/jira/browse/JBESB-2882?page=com.atlassian.jira.plu...
]
Kevin Conner updated JBESB-2882:
--------------------------------
Fix Version/s: 4.8
Add support for fireUntilHalt to BusinessRulesProcessor
-------------------------------------------------------
Key: JBESB-2882
URL: https://jira.jboss.org/jira/browse/JBESB-2882
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.6
Reporter: Jeff DeLong
Fix For: 4.8
To better support CEP, an ESB Rule Service should be able to create the KnowledgeBase,
StatefulKnowledgeSession, etc, and then execute fireUntilHalt. This will cause the thread
to block, and the rules engine will continue to process (in a separate thread). Either the
same ESB Service, or different service with access to the StatefulKnowledgeSession, can
then receive messages / events and insert them into the StatefulKnowledgeSession.
FireUntil Halt provides two important benefits to a CEP application. First it provides
more timely rules firing. Even more important, it support the case where the absence of
incoming events should cause rules to fire.
--
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
10:15 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-2882) Add support for fireUntilHalt to BusinessRulesProcessor
[
https://jira.jboss.org/browse/JBESB-2882?page=com.atlassian.jira.plugin.s...
]
David Ward reassigned JBESB-2882:
---------------------------------
Assignee: David Ward
Add support for fireUntilHalt to BusinessRulesProcessor
-------------------------------------------------------
Key: JBESB-2882
URL: https://jira.jboss.org/browse/JBESB-2882
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.6
Reporter: Jeff DeLong
Assignee: David Ward
Fix For: 4.9
To better support CEP, an ESB Rule Service should be able to create the KnowledgeBase,
StatefulKnowledgeSession, etc, and then execute fireUntilHalt. This will cause the thread
to block, and the rules engine will continue to process (in a separate thread). Either the
same ESB Service, or different service with access to the StatefulKnowledgeSession, can
then receive messages / events and insert them into the StatefulKnowledgeSession.
FireUntil Halt provides two important benefits to a CEP application. First it provides
more timely rules firing. Even more important, it support the case where the absence of
incoming events should cause rules to fire.
--
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
4:18 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-2882) Add support for fireUntilHalt to BusinessRulesProcessor
[
https://jira.jboss.org/browse/JBESB-2882?page=com.atlassian.jira.plugin.s...
]
David Ward closed JBESB-2882.
-----------------------------
Resolution: Done
Committed revision 34210. (trunk)
Thew new property is:
ruleFireMethod=FIRE_ALL_RULES or FIRE_UNTIL_HALT.
Description of these properties are in detail in the Services Guide, as well as in javadoc
and lightly in Programmers Guide.
Note that FIRE_UNTIL_HALT blocks the current thread, so a new Thread (with the correct
context class loader) is spawned to call fireUntilHalt(). When someone sends in a Message
that specifies dispose as a Message property, halt() is called on the session, which kills
the spawned thread. The thread is a daemon thread, so it will not keep jboss from
shutting down if it is stopped.
Add support for fireUntilHalt to BusinessRulesProcessor
-------------------------------------------------------
Key: JBESB-2882
URL: https://jira.jboss.org/browse/JBESB-2882
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.6
Reporter: Jeff DeLong
Assignee: David Ward
Fix For: 4.9
To better support CEP, an ESB Rule Service should be able to create the KnowledgeBase,
StatefulKnowledgeSession, etc, and then execute fireUntilHalt. This will cause the thread
to block, and the rules engine will continue to process (in a separate thread). Either the
same ESB Service, or different service with access to the StatefulKnowledgeSession, can
then receive messages / events and insert them into the StatefulKnowledgeSession.
FireUntil Halt provides two important benefits to a CEP application. First it provides
more timely rules firing. Even more important, it support the case where the absence of
incoming events should cause rules to fire.
--
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
6:03 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2882) Add support for fireUntilHalt to BusinessRulesProcessor
[
https://jira.jboss.org/browse/JBESB-2882?page=com.atlassian.jira.plugin.s...
]
Jeff DeLong commented on JBESB-2882:
------------------------------------
A few comments.
1) "When someone sends in a Message that specifies dispose as a Message property,
halt() is called on the session, which kills the spawned thread." Is
session.dispose() called. If not, the Message property should be named halt (or something
similar). Does re-deploying the service also call halt and dispose of the the session?
2) Is there a mechanism to "publish" the stateful session so that other services
could process messages through a second entry point?
Add support for fireUntilHalt to BusinessRulesProcessor
-------------------------------------------------------
Key: JBESB-2882
URL: https://jira.jboss.org/browse/JBESB-2882
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.6
Reporter: Jeff DeLong
Assignee: David Ward
Fix For: 4.9
To better support CEP, an ESB Rule Service should be able to create the KnowledgeBase,
StatefulKnowledgeSession, etc, and then execute fireUntilHalt. This will cause the thread
to block, and the rules engine will continue to process (in a separate thread). Either the
same ESB Service, or different service with access to the StatefulKnowledgeSession, can
then receive messages / events and insert them into the StatefulKnowledgeSession.
FireUntil Halt provides two important benefits to a CEP application. First it provides
more timely rules firing. Even more important, it support the case where the absence of
incoming events should cause rules to fire.
--
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
12:20 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2882) Add support for fireUntilHalt to BusinessRulesProcessor
[
https://jira.jboss.org/browse/JBESB-2882?page=com.atlassian.jira.plugin.s...
]
David Ward commented on JBESB-2882:
-----------------------------------
Jeff, in response to your comments:
1a) Yes. If a session was created when the config is FIRE_ALL_RULES, then
"dispose=true" in the MessageProperties will simply dispose() the session.
However, when a session was created when the config is FIRE_UNTIL_HALT, then
"dispose=true" in the message Properties will first call session.halt(), then
session.dispose(). The "client" of the stateful session doesn't have to
worry about whether fireAllRules() or fireUntilHalt() was used. They just have to know to
send in dispose=true when they are done.
1b) Yes. Undeploying (or redeploying - which is just an undeploy followed by a deploy)
the service will always call halt() before dispose() on the stateful session IF that
session was configured with FIRE_UNTIL_HALT. Otherwise, just dispose() is called.
2) I do not belive this was a requirement. Please start a developer (not user) forum
thread with more detail and provide the link? Thanks.
David
Add support for fireUntilHalt to BusinessRulesProcessor
-------------------------------------------------------
Key: JBESB-2882
URL: https://jira.jboss.org/browse/JBESB-2882
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.6
Reporter: Jeff DeLong
Assignee: David Ward
Fix For: 4.9
To better support CEP, an ESB Rule Service should be able to create the KnowledgeBase,
StatefulKnowledgeSession, etc, and then execute fireUntilHalt. This will cause the thread
to block, and the rules engine will continue to process (in a separate thread). Either the
same ESB Service, or different service with access to the StatefulKnowledgeSession, can
then receive messages / events and insert them into the StatefulKnowledgeSession.
FireUntil Halt provides two important benefits to a CEP application. First it provides
more timely rules firing. Even more important, it support the case where the absence of
incoming events should cause rules to fire.
--
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
12:26 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2882) Add support for fireUntilHalt to BusinessRulesProcessor
[
https://jira.jboss.org/browse/JBESB-2882?page=com.atlassian.jira.plugin.s...
]
Jeff DeLong commented on JBESB-2882:
------------------------------------
David,
WRT to 2 I can start another developer forum thread (I seem to remember comment on this
requirement in a developer forum thread a year or more ago). However it you look at the
text in this JIRA it says:
"Either the same ESB Service, or different service with access to the
StatefulKnowledgeSession, can then receive messages / events and insert them into the
StatefulKnowledgeSession. "
Jeff
Add support for fireUntilHalt to BusinessRulesProcessor
-------------------------------------------------------
Key: JBESB-2882
URL: https://jira.jboss.org/browse/JBESB-2882
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.6
Reporter: Jeff DeLong
Assignee: David Ward
Fix For: 4.9
To better support CEP, an ESB Rule Service should be able to create the KnowledgeBase,
StatefulKnowledgeSession, etc, and then execute fireUntilHalt. This will cause the thread
to block, and the rules engine will continue to process (in a separate thread). Either the
same ESB Service, or different service with access to the StatefulKnowledgeSession, can
then receive messages / events and insert them into the StatefulKnowledgeSession.
FireUntil Halt provides two important benefits to a CEP application. First it provides
more timely rules firing. Even more important, it support the case where the absence of
incoming events should cause rules to fire.
--
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
12:44 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2882) Add support for fireUntilHalt to BusinessRulesProcessor
[
https://jira.jboss.org/browse/JBESB-2882?page=com.atlassian.jira.plugin.s...
]
Jeff DeLong commented on JBESB-2882:
------------------------------------
Started forum thread https://community.jboss.org/thread/154668 to discuss 2 in detail.
Add support for fireUntilHalt to BusinessRulesProcessor
-------------------------------------------------------
Key: JBESB-2882
URL: https://jira.jboss.org/browse/JBESB-2882
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.6
Reporter: Jeff DeLong
Assignee: David Ward
Fix For: 4.9
To better support CEP, an ESB Rule Service should be able to create the KnowledgeBase,
StatefulKnowledgeSession, etc, and then execute fireUntilHalt. This will cause the thread
to block, and the rules engine will continue to process (in a separate thread). Either the
same ESB Service, or different service with access to the StatefulKnowledgeSession, can
then receive messages / events and insert them into the StatefulKnowledgeSession.
FireUntil Halt provides two important benefits to a CEP application. First it provides
more timely rules firing. Even more important, it support the case where the absence of
incoming events should cause rules to fire.
--
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
12:54 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2882) Add support for fireUntilHalt to BusinessRulesProcessor
[
https://jira.jboss.org/browse/JBESB-2882?page=com.atlassian.jira.plugin.s...
]
David Ward commented on JBESB-2882:
-----------------------------------
Thanks Jeff. Yeah, I originally misunderstood the comment "Either the same ESB
Service, or ..."
I definitely think that would be a different requirement, and thus a different jira, than
this one. I will give this some thought and follow up on the new forum thread. When we
decide how it should be handled, I'll create a new jira.
Add support for fireUntilHalt to BusinessRulesProcessor
-------------------------------------------------------
Key: JBESB-2882
URL: https://jira.jboss.org/browse/JBESB-2882
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.6
Reporter: Jeff DeLong
Assignee: David Ward
Fix For: 4.9
To better support CEP, an ESB Rule Service should be able to create the KnowledgeBase,
StatefulKnowledgeSession, etc, and then execute fireUntilHalt. This will cause the thread
to block, and the rules engine will continue to process (in a separate thread). Either the
same ESB Service, or different service with access to the StatefulKnowledgeSession, can
then receive messages / events and insert them into the StatefulKnowledgeSession.
FireUntil Halt provides two important benefits to a CEP application. First it provides
more timely rules firing. Even more important, it support the case where the absence of
incoming events should cause rules to fire.
--
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
5045
days inactive
5332
days old
8 comments
3 participants
participants (3)
-
David Ward (JIRA) -
Jeff DeLong (JIRA)
-
Kevin Conner (JIRA)