[jboss-jira] [JBoss JIRA] Commented: (JBAS-5231) cluster-safe configuration for HILOSEQUENCES is not enabled in the "all" server conf
[ http://jira.jboss.com/jira/browse/JBAS-5231?page=comments#action_12403366 ]
Alexey Loubyansky commented on JBAS-5231:
-----------------------------------------
Yes, it looks good to me even w/o the SelectHiSql. Of course, we need proper tests for
this. But fixing "JBAS-3266 HiLoKeyGenerator is not cluster-safe" I seem to have
not realized all the things that it fixed. Proper tests mean running a couple of JBoss
instances and using key generators backed by the same db and table.
cluster-safe configuration for HILOSEQUENCES is not enabled in the
"all" server conf
-------------------------------------------------------------------------------------
Key: JBAS-5231
URL: http://jira.jboss.com/jira/browse/JBAS-5231
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Clustering
Affects Versions: JBossAS-5.0.0.Beta4
Reporter: Luc Texier
Assigned To: Alexey Loubyansky
\jboss-5.0.0.Beta4\server\all\deploy\uuid-key-generator.sar\META-INF
In the EAP "production" configuration, the following attribute is enabled by
default. Not in the "all"configuration which is clustered by definition
<!-- Uncomment to make it cluster-safe: Select current Hi value query (FOR UPDATE
is recommended) -->
<attribute name="SelectHiSql">
select HIGHVALUES from HILOSEQUENCES where SEQUENCENAME='general' FOR
UPDATE
</attribute>
some more information
http://wiki.jboss.org/wiki/Wiki.jsp?page=CMPHiLoKeyGenerator
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira