Manual

-Xnoclassgc
Is an optional argument to stop the Java class garbage collection.
Syntax:
-Xnoclassgc
By default, the Java runtime reclaims space for unused Java classes. Including this optional
argument might prevent any memory-leak problems.
Hibernate Framework Configurations for NonStop Systems
This section discusses the NonStop specific Hibernate configurations for the following:
• JDBC Driver for SQL/MX Database
• Database Transaction Management
• Connection Pooling
All the configurations for JDBC, Transaction Management, and Connection Pooling are configured
in either the hibernate.properties or the hibernate.cfg.xml file.
JDBC Driver for SQL/MX Database
The JDBC driver to be used when a Hibernate application connects to the SQL/MX database
must be specified in the hibernate.cfg.xml or hibernate.properties file created while
developing the Hibernate application.
This section discusses the following:
• Configuring the JDBC Type 2 Driver for SQL/MX Database
• Configuring JDBC Type 4 Driver for SQL/MX Database
Configuring the JDBC Type 2 Driver for SQL/MX Database
In a typical Hibernate application, you can configure the JDBC Type 2 driver for the SQL/MX
database using either one of the following preferred options:
• Configuring the JDBC Type 2 Driver for the SQL/MX Database using hibernate.cfg.xml
• Configuring JDBC Type 2 Driver for SQL/MX Database using hibernate.properties
Configuring the JDBC Type 2 Driver for the SQL/MX Database using hibernate.cfg.xml
The advantage of using this approach is the externalization of mapping file names to the
configuration. To complete the database operation in a Hibernate application using the JDBC
Type 2 driver for the SQL/MX database, complete the following steps:
1. Specifying the JDBC Type 2 Driver for SQL/MX Database
2. Defining the Connection URL
3. Establishing the Connection
4. Defining the Hibernate Dialect for SQL/MX Database
5. Specifying the Mapping Resources
6. Opening a Session for Database Operation
7. Closing the Session
Specifying the JDBC Type 2 Driver for SQL/MX Database
One of the advantages of using the JDBC driver is that the SQL/MX database server does not
require any changes. Instead, the JDBC Type 2 driver translates calls written in Java to the specific
format required by the database server.
To specify the JDBC Type 2 driver, enter com.tandem.sqlmx.SQLMXDriver as the JDBC Type
2 driver class for the SQL/MX database in the hibernate.cfg.xml file under the
<session-factory> tag as shown:
318 Configuring Hibernate Applications on NonStop Systems