2.14.1 Availability of the functionality in user threads

This section explains the Application Server functionality available in user threads. For details on how to use user threads, see 6.2.1(15) Using user thread.

The following table describes whether each functionality provided in an Application Server is available in user threads:

Table 2-45 Availability of the functionality in user threads

Functionality nameAvailabilityReference
Using servlet APIP(1)
Invoking an Enterprise BeanN--
Naming ServiceY(2)
Resource connectionP(3)
Transaction serviceP
Integrated user managementN--
Log operation and failure detectionY(4)
J2EE application operationsP(5)
Using the container extension libraryY(6)
Legend:
Y: Available
P: Partially available
N: Not available
--: Not applicable

The functionality available in the user threads is further classified into detailed functionality, and whether each functionality is available in servlets or JSPs, and user threads is explained below. The notes on using the functionality in user threads are also explained.

Organization of this subsection
(1) Servlet API
(2) Naming Service
(3) Resource connection and transaction service
(4) Log operation and failure detection
(5) J2EE application operations
(6) Container Extension Library

(1) Servlet API

When you use the servlet API in user threads, you cannot use the request objects and response objects. Use the servlet API only in request processing threads. For details, see the section on Thread Safety in the Servlet Specifications.

(2) Naming Service

The following table describes whether the functionality provided as the Naming Service is available in servlets or JSPs and user threads:

Table 2-46 Availability of the functionality of Naming Service (user threads)

Classification/Functionality nameServlets or JSPsUser threads
JNDI LookupResource adapterDB ConnectorYY
DB Connector for Cosminexus RM and Cosminexus RMYY
TP1/Message Queue - AccessYY
uCosminexus TP1 ConnectorYY
Java MailYY
JavaBeans resourceYY
User transactionYY
Legend:
Y: Available

When you use the Naming Service, do not stop the application when the user threads are running.

(3) Resource connection and transaction service

The following table describes whether the functionality provided as resource connection and transaction service is available in servlets or JSPs and user threads:

Table 2-47 Availability of the functionality of resource connection and transaction management (user threads)

Classification/Functionality nameServlets or JSPsUser threads
Connection poolingConnection pooling by DB ConnectorYY
Connection pooling by DB Connector for Cosminexus RM and Cosminexus RMYY
Connection pooling with uCosminexus TP1 ConnectorYY
Connection pooling to TP1/Message Queue - AccessYY
Connection pooling to SMTP server----
Warming up of connection poolYY
Adjusting the number of connectionsYY
Connection sharingYY
Connection associationYY
Statement pooling (DB Connector)YY
Light transactionYY
In-process transaction serviceYY
DataSource object cachingYY
Optimizing container management sign-on in DB ConnectorYY
Pooling the receiving bufferYY
Detecting a connection failureFailure detection by DB ConnectorYY
Failure detection by DB Connector for Cosminexus RM and Cosminexus RMYY
Detecting connection failure with uCosminexus TP1 Connector----
Detecting connection failure to TP1/Message Queue - Access----
Detecting connection failure of SMTP server----
Waiting to acquire connections in the case of connection depletionYY
Retrying to acquire connectionRetrying connection acquisition by DB ConnectorYY
Retrying connection acquisition by DB Connector for Cosminexus RM and Cosminexus RMYY
Retrying acquisition of connection with uCosminexus TP1 ConnectorYY
Retrying acquisition of connection to TP1/Message Queue - AccessYY
Retrying acquisition of connection to SMTP server----
Connection pool clearYY
Closing and releasing a connectionAutomatic closing of connection (Web container)Y--
Connection sweeperYY
Transaction timeoutYY
Transaction recoveryYY
Automatic conclusion of transaction#YN
SQL output for troubleshootingYY
Connection pool clusteringYY
Legend:
Y: Available
--: Not available
#
This functionality is used for looking up an unconcluded transaction when returning from a method of the servlet.

The precautions when using the resource connection and transaction service in user threads are as follows:

(4) Log operation and failure detection

The following table describes whether the functionality provided as log operation and error detection is available in servlets or JSPs and user threads:

Table 2-48 Availability of the functionality of log operation and failure detection (user threads)

Classification/Functionality nameServlets or JSPsUser threads
Automatic execution of processing by Management eventsYY
Monitoring a system by JP1 eventYY
User log outputYY
Performance analysis traceYY
Monitoring the CTM statisticsYY
Legend:
Y: Available

(5) J2EE application operations

The following table describes whether the functionality provided for operating a J2EE application is available in servlets or JSPs and user threads:

Table 2-49 Availability of the functionality for operating a J2EE application (User threads)

Classification/Functionality nameServlets or JSPsUser threads
Controlling the number of concurrently executing threads in the Web containerY--
Dynamically changing the number of concurrently executing threads in the schedule queueYY
Monitoring the execution time of a J2EE applicationMethod timeout functionalityY--
Method cancellation functionalityY--
Terminating the J2EE applicationNormal terminationYY#1
Forced terminationYY#1
Switching the J2EE applicationSwitching by redeploy functionalityYY#2
Switching by reload functionalityYY
Legend:
Y: Available
--: Not available
#1
Do not stop user threads in the container.
#2
Do not stop user threads in the container when switching the J2EE applications that are started.

(6) Container Extension Library

The container extension library is available in both servlets or JSPs and user threads.