Praveen Sripati wrote:
We are in the process of migrating Tomcat and MySQL to Microsoft Azure Cloud
and facing challenges due to the dynamic nature of the cloud like allocation
of dynamic ip and ports to the instances of Tomcat & MySQL in Azure. Because
of this behavior Tomcat needs to
1) Dynamically update the ip and ports of the different MySQL instances in
the JDBC URL (
http://dev.mysql.com/doc/refman/5.5/en/connector-j-reference-replication-connection.html).
Suppose the following is the JDBC URL, then it has to be updated in Tomcat
at run-time when a new instance of MySQL is bought up or an instance of
MySQL is bought down.
url=jdbc:mysql:replication://127.0.0.1:5104,127.0.0.1:5108,127.0.0.1:5112,
127.0.0.1:5116,127.0.0.1:5116/itops
2) We are using DBCP (http://commons.apache.org/dbcp/) for connection
pooling. Similarly when a new instance of MySQL is bought up or an instance
of MySQL is bought down the pool has to be updated dynamically accordingly
at run-time.
Has anyone come across a solution for these problems while deploying Tomcat
and MySQL in Cloud?
I don't know anything about the MS Azure Cloud, but the example you are giving above does
not seem to make sense in the context which you are describing.
127.0.0.1 is always "localhost", so even if there is some dynamics involved, that should
not change, or ?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
