Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
RE: Why is Liferay 6.1 WebDAV not using read-writer database configuration?
We recently enabled read-writer database configuration for Liferay 6.1. Our database administrators confirmed they are now seeing read traffic to both databases and write traffic to one. I thought this odd as I thought it would result in reads to one and writes to the others but regardless we moved forward anyway. A couple days later users reported that the WebDAV functionality used to upload files via Windows Explorer was not working. Windows explorer opens but shows that the target path/folder is empty. I checked the logs and see that when WebDAV is used the logs are showing that its trying to perform an insert against the database which isnt configured for write traffic and its failing. Database admins confirmed the same. Other than WebDAV all other OOB functionality has been working as expected and all write traffic has been targeting the database configured for writes.
- I've not been able to identify anything unique about WebDAV in the source which would explain this behavior? Is this a known bug? Can someone suggest how to override this so that it will honor the read and write specific properties in portal-ext.properties?
With the release date of the last 6.1 CE release in 2013, it's a long abandoned version. Even 6.1 EE (with 7 years support time) has reached its end of life by now.
My #1 recommendation is to upgrade and check if the same behavior can be observed on the latest version.
As of your question "how to override": I'm suspecting that you'd need an ext plugin for patching the behavior, after you find what to patch.
Powered by Liferay™