tag:help-archives.hannonhill.com,2010-02-09:/discussions/general/318-error-abstractflushingeventlistener-could-not-synchronize-database-state-with-sessionCascade CMS: Discussion 2012-12-13T21:18:51Ztag:help-archives.hannonhill.com,2010-02-09:Comment/76405852011-06-03T20:02:19Z2011-06-03T20:02:19ZERROR [AbstractFlushingEventListener] Could not synchronize database state with session <div><p>I am seeing a lot of the following error in my logs after we had
a power failure:</p>
<p>ERROR [AbstractFlushingEventListener] Could not synchronize
database state with session</p>
<p>It seems also that within a couple hours of rebooting that
logins stop working and I see this in my logs as well:</p>
<p>[JDBCExceptionReporter] Cannot get a connection, pool
exhausted</p>
<p>Has anyone experienced this before?<br>
I just reinstalled 6.8.2. I still see the synchronization errors,
but I'm waiting on the pool exhausted errors to appear again.</p></div>horsagertag:help-archives.hannonhill.com,2010-02-09:Comment/76405852011-06-21T12:10:23Z2011-06-21T12:10:23ZERROR [AbstractFlushingEventListener] Could not synchronize database state with session <div><p>Are you still seeing these problems in your instance? This looks
to be related to a potential problem with the database
configuration. If you continue to see errors concerning the
connection pool, you'll want to check what the current setting is
on the database (for the connection pool) and then check to see the
maximum number of connections Cascade Server is using.</p>
<p>To check on the Cascade side, you will want to view the contents
of the file <em>/tomcat/conf/context.xml</em>.</p>
<p>In that file, you will see a database configuration for the
database to which you are connecting. In the
<code><Resource></code> element, you should see the attribute
<strong>MaxActive</strong>. By default, I believe this is set to
<em>50</em>. This value is the maximum number of database
connections in the pool. You could try increasing this by 10 or so
to see if that alleviates the problem, but you will want to make
sure first that your database allows for that number of
connections.</p>
<p>Let me know what you find.</p>
<p>Thanks</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/76405852011-06-21T13:21:04Z2011-06-21T13:21:04ZERROR [AbstractFlushingEventListener] Could not synchronize database state with session <div><p>Tim,</p>
<p>Thank you for the reply. We are no longer experiencing this
issue. It appears to have resolved itself. No configuration changes
were made. For some reason a third service restart was more magic
than the first two.</p>
<p>Chris</p></div>horsagertag:help-archives.hannonhill.com,2010-02-09:Comment/76405852011-06-21T13:23:21Z2011-06-21T13:23:21ZERROR [AbstractFlushingEventListener] Could not synchronize database state with session <div><p>Good deal Chris! Glad to hear that you are no longer
experiencing these problems.</p>
<p>I appreciate the update!</p></div>Tim