I feel there is a bug in Liferay even in EE version for this read write db config. If you specify the following
1
2spring.configs=\
3 META-INF/base-spring.xml,\
4 \
5 META-INF/hibernate-spring.xml,\
6 META-INF/infrastructure-spring.xml,\
7 META-INF/management-spring.xml,\
8 \
9 META-INF/util-spring.xml,\
10 \
11 META-INF/jpa-spring.xml,\
12 \
13 META-INF/audit-spring.xml,\
14 META-INF/cluster-spring.xml,\
15 META-INF/editor-spring.xml,\
16 META-INF/jcr-spring.xml,\
17 META-INF/ldap-spring.xml,\
18 META-INF/messaging-core-spring.xml,\
19 META-INF/messaging-misc-spring.xml,\
20 META-INF/poller-spring.xml,\
21 META-INF/rules-spring.xml,\
22 META-INF/scheduler-spring.xml,\
23 META-INF/scripting-spring.xml,\
24 META-INF/search-spring.xml,\
25 META-INF/workflow-spring.xml,\
26 \
27 META-INF/counter-spring.xml,\
28 META-INF/document-library-spring.xml,\
29 META-INF/mail-spring.xml,\
30 META-INF/portal-spring.xml,\
31 META-INF/portlet-container-spring.xml,\
32 \
33 META-INF/dynamic-data-source-spring.xml,\
34 #META-INF/shard-data-source-spring.xml,\
35 #META-INF/memcached-spring.xml,\
36 #META-INF/monitoring-spring.xml,\
37 \
38 META-INF/ext-spring.xml
We can see in above that even infrastructure-spring.xml is there which means jdbc.default.* jndi name is still considered. No doubt it uses both read and write db that we configured in portal-ext.properties, it is also trying to use jdbc.default.* properties which is there in portal.properties and hence using hypersonic too which is causing the above problem.
Can any liferay guys confirm the same?
Regards,
Sandeep
Be kell jelentkezni ahhoz, hogy ez helytelenként legyen megjelölve.