[TECHNICAL-SUPPORT] LPS-39276 Lock service should always use the primary database node if read/write splitting is enabled

Hey Shuyang,

1) Done, but I have found some anomalies.

We agreed on using "ChainableMethodAdviceInjector" as a means of enabling "DynamicDataSourceAdvice" in "dynamic-data-source-spring.xml". Even though "DynamicDataSourceAdvice" got injected to the chain of advices, when a service method was called I didn't see it running. It was supposed to be between "SystemEventAdvice" and "TransactionInterceptor", but after debugging into the corresponding "ServiceBeanMethodInvocation", I didn't see ANY of those advices which were created by means of "ChainableMethodAdviceInjector".

I think that after "ServiceBeanAopProxyCreator" created instances of "ServiceBeanAopProxy" for service beans, "ChainableMethodAdviceInjector" inserts a  new advice to the chain in vain, because the list of method interceptors got cached in instances of "ServiceBeanAopProxy".

For this reason I made this change: https://github.com/laszlocsontos/liferay-portal/commit/915a808596ebf4ef8c99710a1d51e4fdca791dfc

Could you please check if this really a bug?

2) Done.

3) Done.

Cheers,
László

PS: This is a follow-up PR based on the comments here: https://github.com/shuyangzhou/liferay-portal/pull/382#issuecomment-23423065

CC: @zsigmondrab