That sounds good and acceptable to me, so long as we provide the mechanism for someone to do that administration. How should they go about detecting dead EPRs in the database? Why not build an admin console (or something like that) where you could see all registered EPR's and even try sending an 'ack' message to each - no response or no confirmation that it's up and you could punt it. by confirmation, it could be a simple telnet to the epr port, etc...
just an idea.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991348#3991348
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991348
Without getting into too much technical detail, but it's never possible to detect a failure with 100% accuracy until the failure is fixed. All you can ever do is failure suspect. With this approach to UIDs and multiple registration, we're always going to have garbage in the registry in the event of failures and it's never going to be possible for us to know for certain that we can/should remove an EPR. This is a long winded way of saying: we can punt this to a sys admin function for now.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991339#3991339
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991339
"tfennelly" wrote : "kurt.stam(a)jboss.com" wrote : anonymous wrote : I'm still worried that we end up with 'dead' EPRs, but I guess the code that consumes EPRs can pick the next one (and unregister dead onces?).
| |
| | Can't that happen in either case?
|
| Yes, unless we tell users to persist the UID they get back.
|
| A complete and correct solution is more complex than we have time for. I suggest that we simply don't clear out all of the EPRs at un-registration time. Any "dead" EPRs can be handled by a sys admin. Plus, the definition of a "dead" EPR may well be implementation specific.
|
| If we agree and this works (!) then we need to call this out in the docs.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991334#3991334
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991334
anonymous wrote : If it does support registering the same EPR 1+ times, then... if you didn't change the interface at all and just removed/unregistered 1 of the EPR instances matching the name, would that solve the issue? What are we doing at the moment - removing them all?
yes right now upon unregistering I clean out all similarly looking EPRs.
I'm still worried that we end up with 'dead' EPRs, but I guess the code that consumes EPRs can pick the next one (and unregister dead onces?).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991332#3991332
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991332