cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kiran Koneti (JIRA)" <>
Subject [jira] [Created] (CLOUDSTACK-5207) jdbc.exceptions are observed when both Master 1 and master 2 goes down and comes back.
Date Wed, 20 Nov 2013 06:15:23 GMT
Kiran Koneti created CLOUDSTACK-5207:

             Summary: jdbc.exceptions are observed when both Master 1 and master 2 goes down
and comes back.
                 Key: CLOUDSTACK-5207
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Management Server
    Affects Versions: 4.3.0
            Reporter: Kiran Koneti
            Priority: Critical
             Fix For: 4.3.0

1)I have created a replication db with 2 masters say M1 and M2.
2)The CS setup came up and both the db's are in sync.
3)now i made the M1 down and the M2 was made the master and the operations of CS were normal.
4)Now i made the M2 also down and the db of the CS could not be accessed.
5)Later i made the M1 up and then M2.The data sync happened properly but there is an error
message which is constantly shown in the MS log and it is as below:

"2013-11-20 11:34:50,938 ERROR [c.c.u.d.ConnectionConcierge] (ConnectionConcierge-1:ctx-7c449525)
Unable to keep the db connection for LockMaster1
com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No operations allowed
after connection closed.  Connection closed after inability to pick valid new connection during
        at sun.reflect.GeneratedConstructorAccessor25.newInstance(Unknown Source)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
        at java.lang.reflect.Constructor.newInstance(
        at com.mysql.jdbc.Util.handleNewInstance(
        at com.mysql.jdbc.Util.getInstance(
        at com.mysql.jdbc.SQLError.createSQLException(
        at com.mysql.jdbc.SQLError.createSQLException(
        at com.mysql.jdbc.SQLError.createSQLException(
        at com.mysql.jdbc.SQLError.createSQLException(
        at com.mysql.jdbc.LoadBalancingConnectionProxy.invoke(
        at com.mysql.jdbc.FailoverConnectionProxy.invoke(
        at $Proxy19.prepareStatement(Unknown Source)
        at org.apache.commons.dbcp.DelegatingConnection.prepareStatement(
        at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.prepareStatement(
        at org.apache.cloudstack.managed.context.ManagedContextRunnable$
        at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$
        at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(
        at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(
        at java.util.concurrent.Executors$
        at java.util.concurrent.FutureTask$Sync.innerRunAndReset(
        at java.util.concurrent.FutureTask.runAndReset(
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(
        at java.util.concurrent.ScheduledThreadPoolExecutor$
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$

This message was sent by Atlassian JIRA

View raw message