Synchrony cannot communicate with the database due to The BUFFERDIR connection property is invalid error
プラットフォームについて: Server と Data Center のみ - この記事は、サーバーおよびデータセンター プラットフォームのアトラシアン製品にのみ適用されます。
Even though the Collaborative Editing management page reports the connection between Confluence and Synchrony as stable, you are unable to edit pages with this feature enabled.
The following error can be found in atlassian-synchrony
Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@24f7d161 is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests. com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@97422f3 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception: java.sql.SQLException: The BUFFERDIR connection property is invalid. at net.sourceforge.jtds.jdbc.JtdsConnection.unpackProperties(JtdsConnection.java:1286)
The BUFFERDIR is a directory used as a temporary data holder for the connection between the application and the database. When using Tomcat as a web server, this directory is always the CATALINA_TMPDIR, which corresponds to the temp folder inside of Confluence Install. You can find more information about the Confluence directories here:
If Synchrony is unable to access this folder (<confluence-install>/temp), it will not be unable to communicate with the database and the editor will not load as expected.
- Check that the directory <confluence-install>/temp exists
- Ensure that Operating System account which is used to start and stop Confluence has full read/write/execute permissions on this directory
If you are on Windows and you've added the
java.io.tmpdirproperty in <confluence-home>/synchrony-args.properties to point to <confluence-install>/temp, please make sure the path uses double backslashes instead of a single backslash. For example:
- Once those items are checked, restart Confluence and Synchrony should be able to reach the database