You can run a server in different modes, debug and normal, using different Java runtime versions and different Java virtual machines (VMs). To start the server in the desired configuration:
By default, EAServer runs with JDK version 1.4. To run with JDK version 1.5, start the server using the -jdk15 option, or set the JAVA_HOME environment variable to the JDK 1.5 installation directory—see “Configuring environment variables”.
Switching back
to JDK 1.4 from JDK 1.5
Classes compiled with JDK 1.5 cannot be run in JDK 1.4 or
earlier JDK versions. Since EAServer generates new classes for deployed
applications, applications deployed with JDK 1.5 may not run if
the server is restarted with JDK 1.4. To switch back to JDK 1.4
from JDK 1.5, undeploy and redeploy any applications that were deployed
to the server running in JDK 1.5. Applications deployed to JDK 1.4
must also be compiled with JDK 1.4 (or with JDK 1.5 while specifying
JDK 1.4 compatibility with the -source
1.4 option to javac).
EAServer uses the JVM defined by the java command. To specify which JVM to use, set the DJC_JVM_OPTIONS environment variable to one of the following:
-server – HotSpot Server VM.
-client – HotSpot Client VM.
Change to the EAServer bin subdirectory.
Run either start-server.sh (UNIX) or start-server.bat (Windows) with the options described in Table 3-9.
Option |
Description |
|---|---|
server |
Specifies the name of the server; the default is the name of the machine on which EAServer is installed. |
-bg |
Windows only. Runs the server in the background. By default, the server runs in a command window. |
-debug |
Runs the server in debug mode. Running a server in debug mode allows you to remotely debug components from tools that support EAServer component debugging, such as JBuilder.
|
-jdk14 |
Starts the server with JDK 1.4. |
-jdk15 |
Starts the server with JDK 1.5. |
-jpda |
Runs the server in Java Platform Debugger Architecture (JPDA) mode. |
-jpdaSuspend |
Used with -jpda, this option suspends the server at start-up time. This allows you to set breakpoints in code that executes at start-up, such as servlets that are configured to load on start-up. You can resume execution of the server with your Java debugger.The default port to use for JPDA debugging is 5005. |
-ejbTrace |
Traces EJB component invocations in the server log. To enable permanently (trace EJB components every time you run the server), set the ejbTrace server property—see “Log/Trace tab”. |
-exRef |
Logs exception cross-references, which is helpful for debugging. |
-jmsTrace |
Traces JMS operations in the server log. All public and protected JMS provider methods are traced. To enable permanently, set the jmsTrace server property—see “Log/Trace tab”. |
-quiet |
Runs the server without echoing messages. |
-rmiTrace |
Traces remote method invocations for IIOP and RMI-IIOP in the server log. To enable permanently, set the rmiTrace server property—see “Log/Trace tab”. |
-rt14 |
Starts the server with Java runtime 1.4. |
-rt15 |
Starts the server with Java runtime 1.5. |
-sqlTrace |
Traces JDBC driver activity in the server log, including JDBC prepared statement operations, parameter and result information for container-managed persistence operations (queries and updates), and transaction commit/rollback operations. To enable permanently, set the sqlTrace server property—see “Log/Trace tab”. |
-txRef |
Logs transaction cross-references, which is helpful for tuning server performance. For each query and transaction, “count” information is logged to a file in the logs/transactions directory. These logs allow you to determine what database interactions occur at runtime for EJBs using JDBC, entity beans using CMP, and MDBs. A new log file is created every five minutes. |
-verbose |
Enables verbose debugging. |
-webTrace |
Traces Web component invocations in the server log. To enable permanently, set the webTrace server property—see “Log/Trace tab”. |
EAServer supports Internet Protocol Version 6 (IPV6). For more information, see “IPV6 support”.
