Maybe you bound a serialized copy of your mbean object in jndi, so when you look it up you get a new one... changing anything on it won't affect the original that the mbean server knows about.
Why don't you skip jndi and access it through the mbean server?
My guess is you actually changed a serialized
copy of the MBean.
Look at the other posts in this forum for the
I'm not sure it was available in 2.4.3?
The http adaptor is available at port 8082, but that means
invoking the MBean through a http socket.
Jinx (or is that just an English thing)