title: nested exception is javax.management.InstanceAlreadyExistsException: com.zaxxer.hikari:name=dataSource,type=HikariDataSource
body: <p>I have deployed my spring boot application in tomcat-8.5. It works fine as long as one instance of the war is deployed but as soon as I try to deploy next version of same war file (I am trying to do parallel deployment in tomcat), it throws </p>
  
  <p><code>Caused by: org.springframework.jmx.export.UnableToRegisterMBeanException: Unable to register MBean [HikariDataSource (HikariPool-7)] with key 'dataSource'; nested exception is javax.management.InstanceAlreadyExistsException: com.zaxxer.hikari:name=dataSource,type=HikariDataSource</code>.</p>
  
  <p>I know, since one instance is already running with existing hikari pool, deploying another instance is trying to create a different pool with same name and throwing the error because pool already exist.</p>
  
  <p>I can change the pool name every time I deploy a new version of the application but I don't think that would be a good solution.</p>
  
  <p>Is there any better way i can achieve parallel deployment in tomcat without facing this issue? </p>