Holder valve in MX?

[marc.fleury]

So one of the sexy features that the microkernel approach brings to the table is something like this:

A (connector or not) calls MBean B, imagine bean B goes under maintenance and you stop it for a period of time.

A is still sending threads to B. Can we build a "valve" in the MX base that holds threads while the MBean is under maintenance?


synchronized(targetLock) { targetLock.wait();}

and when the target is ready (notification based)

targetLock.notifyAll();

you get the idea. I am pretty sure it should be at the core invocation level, although you could possibly do it at the interceptor level. I don't know.

[juha]

yes

that is the suspend()/resume() in the invoker I was selling to David at SFO to implement the lifecycle services.

(think you missed that discussion)

(and it was late, I think it put David to sleep too)

-- Juha

[davidjencks]

No, I was awake, but I haven't implemented it yet either.

david

[juha]

thats ok, its on my list of things to do right after the loader repository per mbean server work

-- Juha

[davidjencks]

Whats loader repository per mbean server? sounds interesting;-)

david

[juha]

well basically just extends what you just did -- a loader repository mbean that allows us to config the loader repository scope from JVM level down to MBean server level.

-- Juha