Configuring the JMS based cluster notification

Hi,

We are trying to use the JMS based cluster notification mechanism to publish
cacheupdates on one node to other nodes in a cluster. There are some
constraints ( as I see them ) in 2.0.1 

 - One is that the JNDI context properties are read from the system resource
'jndi.properties'. Why not read these properties from the
'oscache.properties' file ? The problem is that, if in the same deployment,
there is some other component which also reads its JNDI context properties
from 'jndi.properties' then the two configurations can't be different.

 - The other thing is that the current implementation would probably not
work ( I'm not exactly sure about this ) if the JMS server used for this
notification happens to be secured. It would be more appropriate to use the
'javax.jms.ConnectionFactory.createConnection(String userid,String passwd)'
API instead of 'javax.jms.ConnectionFactory.createConnection()'.

 - Also, there could be a provision to update the JMS configuration and
re-establish the JMS connection. Currently, if the JMS server is re-started
or for some reason one would temporarily like to use another JMS server,
then the *same* cache cannot be reconfigured.

Regards,
Radhakrishnan


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click