Discussion: What happens to events?

[Andreas Grünwald]

Hello,

I have a conceptual question regarding the handling of events in case that a connector/tool domain is not available.

Let's assume that there is a connector to an instance of Jira Issues, but the resource is frequently not available. The reason could be either because 

• the server is maintained by the admin
• because a user is editing data and hence some records are locked
• or any other reason.
  

If a new issue is added from another tool (e.g., from Excel or from Bugzilla) then it might be desirable that the event is stored until the component appears back up again. 

How does the EngSb deal with this kind of problem currently? Are the events gone after firing, or is there some kind of queue?

I am fine with any solution, but it would be interesting to hear if you took design decisions regarding this, or if you discussed a similar case earlier. If available it would be great if you could link me to some related literature or documentation regarding this.

Thanks & best,

Andreas

[Andreas Pieber]

Hey Andreas,

We'vent spent any thoughts on this by now. I think there are various options where this could be added:

* directly as a proxy before the service

* as a component somewhere in drools

Maybe there are even more possible places if I think longer about it.

So, in a nutshell, there havent been any thoughts about this by now, nor any architectural decisions. Feel free to propose your own :-)

Kind regards,

Andreas

--
You received this message because you are subscribed to the Google Groups "OpenEngSB user group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openengsb-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Felix Mayerhuber]

Hi,

one solution Andi and I have talked about today would be the following
approach:
*) In the drools-rules we could add a mechanism that if some
specific exception is catched, the rule status is set to a blocking node
(don't know the exact name, but it is part of drools)
*) This blocking node gets activated as soon as there is a specific
event triggered in drools (you can define the event it is waiting for)
*) If the connector gets online again, it throws an event (e.g.
IAmAliveAgainEvent ), which then causes the first rule to retry its logic.

This would solve the problem, right?

Kind regards
Felix

Am 2013-05-21 22:08, schrieb Andreas Pieber:
> Hey Andreas,
>
> We'vent spent any thoughts on this by now. I think there are various
> options where this could be added:
>
> * directly as a proxy before the service
> * as a component somewhere in drools
>
> Maybe there are even more possible places if I think longer about it.
>
> So, in a nutshell, there havent been any thoughts about this by now, nor
> any architectural decisions. Feel free to propose your own :-)
>
> Kind regards,
> Andreas
>
>
> On Tue, May 21, 2013 at 5:50 PM, Andreas Gr�nwald <a.gr...@gmail.com>wrote:
>
>> Hello,
>> I have a conceptual question regarding the handling of events in case that
>> a connector/tool domain is not available.
>>
>> Let's assume that there is a connector to an instance of Jira Issues, but
>> the resource is frequently not available. The reason could be either
>> because
>>

>> - the server is maintained by the admin
>> - because a user is editing data and hence some records are locked
>> - or any other reason.