HiLo Key Generator
The name of the table used to store sequence names and their highest Hi values.
The name of the column in the table that is used to store a name of a sequence.
The name of the column in the table that is used to store the highest Hi value of a sequence.
The DDL statement that will be used to create the table in the database when the service starts and CreateTable attribute is set to true.
Can be true or false. If set to true and the table doesn't exist in the database yet, the table will be created using the DDL statement specified in the CreateTableDdl attribute. If set to false, the table is assumed to exist in the database.
Can be true or false. If set to true and the table exists in the database, the table will be dropped when the service stops, e.g. at undeploy/redeploy time or server restart.
This attribute is optional. If not set then the last Hi value will be stored in the KeyGenerator's highestHi static variable. When a generator is exhausted and needs to refresh its Hi value, the value of this static variable will be used as the current highest Hi value. Of course, this approach doesn't work in a cluster.
To make the service work in a cluster, you should set SelectHiSql to an SQL statement that selects the highest Hi value of the sequence. FOR UPDATE at the end of the query is recommended.
The JNDI name the KeyGeneratorFactory service will be bound to.
The name of the sequence.
HiLo block size.
To see TRACE logging from the service which includes SQL and DDL statements executed, enable TRACE threshold for category
in the log4j.xml.