cache replication

[ahmeddrira]

Hi
i am working on jbilling 3.1 since a periode , and i have remarked that in a production environment i have to run tow jbilling node wich work on the same db , so , the cache replication is very interesting think on this case , on the source code there is a configuration file for ehcache , did your team dealt with this mechanisme

[vikasbo]

Hello Ahmed - Thanks for the comment.

We are familiar with the cache configuration in jBilling. The configuration varies for Master data and Transaction data in basically their time-to-live value. Can you elaborate on the problem you are facing, I will try to address with a solution as soon as possible.

Regards
Vikas

[ahmeddrira]

Hello Vikasbo
i am running tow node of jbilling ,
immagine that i have a session on the first node which is the active node ,
i am note sure if there is an ehcache mechanism that can duplicate my session on the second node ,
so if a proxy pointe me to this node the session will persist and i am note forced to login again ;
...
there is more issue related to this , for example how hibernate manage primary keys sequences if there is tow node

[vikasbo]

Hello Ahmed - for HttpSession sharing accross nodes, the responsibility rests wtih the application server, e.g. tomcat, and the tomcat here should be installed with session replication. Since jBilling is a J2EE application, the tomcat is really the implementor here for the J2EE specs and be responsible for sharing sessions and cache across nodes. Here is an apache tutorial on how you can do it for Tomcat 7.

Please share the results after implementing the above and if you see any improvement.

Thanks
Vikas