uCosminexus Application Server Common Container Functionality Guide

uCosminexus Application Server

Common Container Functionality Guide

3020-3-Y07-10(E)

Contents

Notices

Summary of amendments

Preface

1. Application Server Functionality

1.1 Classification of functionality

1.1.1 Functionality serving as an execution platform for applications

1.1.2 Functionality for operating and maintaining the execution platform of applications

1.1.3 Correspondence between the functionality and manuals

1.2 Correspondence between the purpose of a system and the functionality

1.2.1 Naming management functionality

1.2.2 Functionality for managing resource connections and transactions

1.2.3 Functionality for invoking Application Server from OpenTP1 (TP1 inbound integrated functionality)

1.2.4 JPA functionality used with Application Server

1.2.5 Cosminexus JPA Provider functionality

1.2.6 Cosminexus JMS Provider functionality

1.2.7 JavaMail functionality

1.2.8 CDI functionality used with Application Server

1.2.9 Bean Validation functionality used with Application Server

1.2.10 Managing application attributes

1.2.11 Annotation functionality

1.2.12 Functionality for formatting and deploying J2EE applications

1.2.13 Container extension library functionality

1.3 Description of the functionality mentioned in this manual

1.3.1 Meaning of the classification

1.3.2 Examples of tables describing the classification

1.4 Main functionality changes in Application Server 09-50

2. Naming Management

2.1 Organization of this chapter

2.2 Overview of naming management

2.2.1 Naming management functionality

2.2.2 Naming services

2.3 Binding and looking up objects in the JNDI name space

2.3.1 Types of names used for lookup

2.3.2 Mapping and looking up the JNDI name space

2.3.3 How to check the JNDI name space

2.3.4 Definitions in cosminexus.xml

2.3.5 Execution environment settings

2.4 Looking up with the Portable Global JNDI names

2.4.1 Types of JNDI name spaces

2.4.2 Automatically bound objects

2.4.3 Naming rules for the Portable Global JNDI names

2.4.4 Controlling the registration of Portable Global JNDI names

2.4.5 Looking up with the Portable Global JNDI names when the CTM is used

2.4.6 Resource reference names

2.4.7 Specifying the Portable Global JNDI names in annotations

2.4.8 Definitions in the DD

2.4.9 Execution environment settings

2.5 Looking up with names beginning with HITACHI_EJB

2.6 Assigning an optional name to Enterprise Beans or J2EE resources (User-specified name space functionality)

2.6.1 Objects that can be assigned an optional name

2.6.2 Rules for assigning the optional names

2.6.3 Timing for registering or deleting the optional name

2.6.4 Searching from the client

2.6.5 Setting the optional names for the Enterprise Beans

2.6.6 Setting the optional names for the J2EE resources

2.6.7 Execution environment settings

2.6.8 Precautions for using the user-specified name space functionality

2.7 Searching the CORBA Naming Service by using the round-robin policy

2.7.1 Scope of round-robin search

2.7.2 Operations when performing a round-robin search

2.7.3 Settings required for performing a round-robin search

2.7.4 Settings recommended for using the round-robin search functionality

2.7.5 Notes on performing a round-robin search

2.8 Caching with the naming management functionality

2.8.1 Procedure of caching

2.8.2 Clearing the Cache Used in Naming

2.8.3 Settings for using the caching functionality

2.8.4 Notes on caching in naming

2.9 Detecting errors in a naming service

2.9.1 What is the naming service error detection functionality

2.9.2 Concurrent use of the round-robin search functionality

2.9.3 Behavior of the naming service error detection functionality

2.9.4 Execution environment settings (When the Error Detection functionality is used)

2.9.5 Notes on the naming service error detection functionality

2.10 Switching the CORBA Naming Services

2.11 Re-using the EJB home object references (Functionality for re-connecting to the EJB home objects)

2.11.1 Execution environment settings (J2EE server settings)

2.11.2 Notes on re-using the EJB home object references

3. Resource Connections and Transaction Management

3.1 Organization of this chapter

3.2 Overview of resource connections and transaction management

3.3 Resource connections

3.3.1 How to connect to resources

3.3.2 Types of resource adapters

3.3.3 How to use the resource adapters

3.3.4 Resource adapter functionality

3.3.5 Functionality other than the resource adapter functionality

3.3.6 Implementation for connecting to the resources

3.3.7 How to set up resource adapters

3.3.8 Procedure for resource adapter settings (To deploy and use the resource adapter as a J2EE resource adapter)

3.3.9 Procedure for resource adapter settings (To include and use the resource adapter in the J2EE application)

3.3.10 Procedure for resource adapter settings (To use the resource adapter with Inbound)

3.3.11 Procedure for resource adapter settings (To use connection pool clustering)

3.3.12 Connection settings for using components other than the resource adapters

3.3.13 Notes on the resource adapters

3.4 Managing transactions

3.4.1 Transaction management methods for the resource connections

3.4.2 Local transaction and global transaction

3.4.3 Transaction types available for each resource

3.4.4 Functionality provided with the transaction services

3.4.5 Transaction operations during system exceptions

3.4.6 Obtaining the transaction manager

3.4.7 Overview of processing and the points to remember when using the container-managed transactions (CMT)

3.4.8 Overview of processing and the points to remember when using the UserTransaction interface

3.4.9 Overview of processing and the points to remember when using the resource adapter-specific transaction management interface

3.4.10 Overview of processing and the points to remember when transactions are not used

3.4.11 Notes on the JTA-based transaction implementation

3.4.12 Settings in the execution environment

3.5 Resource sign-on method

3.6 Connecting to a database

3.6.1 Overview of DB Connector-based connections

3.6.2 Available J2EE components and functionality

3.6.3 Connectable databases

3.6.4 Types of DB Connectors (RAR file)

3.6.5 Preconditions and notes on connecting to HiRDB

3.6.6 Preconditions and notes on connecting to Oracle

3.6.7 Preconditions and notes on connecting to SQL Server

3.6.8 Preconditions and notes on connecting to XDM/RD E2

3.6.9 Settings in the execution environment (resource adapter settings)

3.7 Connecting to a database queue

3.7.1 Overview of connections using DB Connector for Cosminexus RM and Cosminexus RM

3.7.2 Features of connections using DB Connector for Cosminexus RM and Cosminexus RM

3.7.3 Available functionality

3.7.4 Connectable databases

3.7.5 Types of DB Connector for Cosminexus RM (RAR file)

3.7.6 Preconditions for connecting to a HiRDB queue

3.7.7 Preconditions for connecting to an Oracle queue

3.7.8 Settings for connecting to a database queue

3.8 Outbound connection with OpenTP1 (SPP or TP1/Message Queue)

3.8.1 Connections using uCosminexus TP1 Connector

3.8.2 Connections using TP1/Message Queue - Access

3.8.3 Connection settings for OpenTP1 and Outbound

3.9 Inbound connection with OpenTP1

3.10 Connection with Cosminexus JMS Provider

3.11 Connecting to the SMTP server

3.12 Using the JavaBeans resources

3.12.1 JavaBeans resource functionality

3.12.2 Procedure for starting the JavaBeans resources

3.12.3 Implementing the JavaBeans resources

3.12.4 Setting up the JavaBeans resources

3.12.5 Replacing the JavaBeans resources

3.13 Connection with other resources

3.13.1 Resource adapters used for connection with other resources

3.13.2 Functionality available for other resource connections

3.14 Functionality for performance tuning

3.14.1 Connection pooling

3.14.2 Functionality available with connection pooling

3.14.3 Connection sharing or association

3.14.4 Statement pooling

3.14.5 Light transaction

3.14.6 In-process transaction service

3.14.7 Caching the DataSource objects

3.14.8 Optimizing the container-managed sign-on for DB Connector

3.14.9 Definitions in cosminexus.xml

3.14.10 Settings in the execution environment

3.15 Functionality for fault tolerance

3.15.1 Detecting the connection errors

3.15.2 Waiting for a connection when connections deplete

3.15.3 Retrying to obtain a connection

3.15.4 Displaying the connection pool information

3.15.5 Clearing the connection pool

3.15.6 Automatically closing the connections

3.15.7 Connection sweeper

3.15.8 Transaction timeout and statement cancellation

3.15.9 Transaction recovery

3.15.10 Output of the SQL statement for troubleshooting

3.15.11 Automatically closing the objects

3.15.12 Definitions in cosminexus.xml

3.15.13 Settings in the execution environment

3.16 Other resource adapter functionality (For the resource adapters conforming to the Connector 1.5 specifications)

3.16.1 Managing the resource adapter lifecycle

3.16.2 Managing the resource adapter work

3.16.3 Message inflow

3.16.4 Transaction inflow

3.16.5 Looking up Administered objects

3.16.6 Specifying multiple connection definitions

3.16.7 Application Server-specific Connector 1.5 API specifications

3.16.8 Settings for using the resource adapters conforming to the Connector 1.5 specifications

3.16.9 Examples of property file specification

3.16.10 Notes on using the resource adapters conforming to the Connector 1.5 specifications

3.17 Functionality for connection pool clustering

3.17.1 Connecting to Oracle using Oracle RAC

3.17.2 Overview of connection pool clustering

3.17.3 Resource adapters used

3.17.4 Connection pool clustering operations

3.17.5 Procedure for stopping or starting a connection pool manually

3.17.6 Settings required for clustering a connection pool

3.18 Connection test for resources

3.19 Functionality for operations in the firewall environment

3.19.1 Communication port for transaction recovery

3.19.2 Communication port used by Smart Agent

3.19.3 Settings for operations in the firewall environment

3.20 Notes on starting a transaction with the EJB client applications

3.20.1 Notes on application development

3.20.2 Notes on system setup

3.20.3 Notes on system operations

4. Invoking Application Server from OpenTP1 (TP1 Inbound Integrated Function) (INTENTIONALLY DELETED)

4.1 INTENTIONALLY DELETED

5. How to Use JPA with Application Server

5.1 Organization of this chapter

5.2 Features of JPA

5.2.1 Advantages of applications using JPA

5.2.2 Entity class

5.2.3 JPA provider

5.3 JPA functionality that can be used with Application Server

5.3.1 Available JPA providers

5.3.2 Available components

5.3.3 Supported application formats

5.3.4 Supported class loader configuration

5.3.5 available resource adapters

5.4 EntityManager

5.4.1 Methods provided with EntityManager

5.4.2 Types of EntityManager

5.4.3 Transaction control and EntityManager

5.4.4 Persistence unit

5.5 Persistence context

5.5.1 EntityManager and persistence context

5.5.2 Persistence context when the container-managed EntityManager is used

5.5.3 Persistence context when the application-managed EntityManager is used

5.6 How to obtain the container-managed EntityManager

5.6.1 Method of injecting EntityManager in the application

5.6.2 Method of looking up EntityManager from the application

5.6.3 Overriding the @PersistenceContext definition using the DD

5.7 How to obtain the application-managed EntityManager

5.7.1 Method of injecting EntityManagerFactory in the application

5.7.2 Method of looking up EntityManagerFactory from the application

5.7.3 Overriding the @PersistenceUnit definition using the DD

5.8 Definitions in persistence.xml

5.8.1 Attributes specified in the <persistence-unit> tag

5.8.2 Tags specified under the <persistence-unit> tag

5.9 Allocating persistence.xml

5.10 JPA interfaces

5.10.1 javax.persistence.EntityManager interface

5.10.2 javax.persistence.EntityManagerFactory interface

5.11 Notes on setting up applications

5.11.1 Notes on allocating the entity classes

5.11.2 Reference scope of the persistence unit name

5.11.3 Items checked when the application is deployed

5.11.4 Notes on using the JPA with Application Server

5.11.5 Notes when the Cosminexus JPA functionality is not used

6. Cosminexus JPA Provider

6.1 Organization of this chapter

6.2 Cosminexus JPA Provider

6.2.1 Processing in Cosminexus JPA Provider

6.2.2 Functionality provided by Cosminexus JPA Provider

6.2.3 Preconditions for using Cosminexus JPA Provider

6.2.4 Estimating the number of DB Connector connections

6.3 Updating a database using entities

6.4 Entity operations by EntityManager

6.4.1 Transition of entity states

6.4.2 persist operation for the entities

6.4.3 remove operation for the entities

6.4.4 Obtaining the entities from the database

6.4.5 Synchronization with the database

6.4.6 Separate and merge operations of an entity from the persistence context

6.4.7 managed entity

6.5 Defining the mapping information between the database and Java objects

6.6 Entity relationships

6.6.1 Relationship types

6.6.2 Annotations for relationships

6.6.3 Direction of relationships

6.6.4 Default mapping (bi-directional relationship)

6.6.5 Default mapping (unidirectional relationship)

6.7 Cache functionality of the entity objects

6.7.1 Processing of the cache functionality

6.7.2 Cache reference forms and cache types

6.7.3 Scope of the cache functionality

6.7.4 Notes on using the cache functionality

6.8 Auto-numbering of the primary key values

6.9 Database operations based on the query language

6.10 Optimistic lock

6.10.1 Optimistic lock processing

6.10.2 Exception processing when optimistic lock fails

6.10.3 Notes on using the optimistic lock

6.11 Pessimistic lock in JPQL

6.12 Creating an entity class

6.12.1 Defining the mapping between an entity class and database

6.12.2 Requirements for creating entity classes

6.12.3 Specifying the access methods for the entity class fields

6.12.4 Creating the accessor method

6.12.5 Types of persistence fields and persistence properties of the entities

6.12.6 Specifying the primary key in the entities

6.12.7 Default mapping rules for the persistence fields and persistence properties

6.13 Procedure for inheriting an entity class

6.13.1 Inheritance class types

6.13.2 Inheritance mapping strategy

6.14 Procedure for using EntityManager and EntityManagerFactory

6.14.1 Entity lifecycle management with EntityManager

6.14.2 How to set up EntityManager and EntityManagerFactory

6.14.3 Notes on the API functions of EntityManager

6.15 Procedure for specifying the callback method

6.15.1 Location for specifying the callback method

6.15.2 Implementing the callback methods

6.15.3 Order of invoking the callback methods

6.16 Procedure for referencing and updating the database with the query language

6.16.1 Procedure for referencing and updating the database with JPQL

6.16.2 Procedure for referencing and updating the database with the native query

6.16.3 Specifying the range of query result items

6.16.4 Specifying the flush mode

6.16.5 Specifying a query hint

6.16.6 Notes on executing a query

6.17 JPQL coding method

6.17.1 JPQL syntax

6.17.2 SELECT statement

6.17.3 SELECT clause

6.17.4 FROM clause

6.17.5 WHERE clause

6.17.6 GROUP BY clause and HAVING clause

6.17.7 ORDER BY clause

6.17.8 Bulk UPDATE statement and Bulk DELETE statement

6.17.9 Notes on using JPQL

6.17.10 Exceptions thrown when queries are used

6.18 Defining persistence.xml

6.19 Settings in the execution environment

7. Cosminexus JMS Provider

7.1 Organization of this chapter

7.2 Overview of Cosminexus JMS Provider

7.2.1 Cosminexus JMS Provider

7.2.2 Location of Cosminexus JMS Provider within Application Server

7.2.3 Overview of the Cosminexus JMS Provider functionality

7.3 Allocating the CJMSP resource adapters and CJMSP Broker

7.3.1 Configuration in which one CJMSP Broker is allocated to one CJMSP resource adapter

7.3.2 Configuration in which one CJMSP Broker is allocated to multiple CJMSP resource adapters

7.4 Types of messaging models

7.4.1 PTP messaging model

7.4.2 Pub/Sub messaging model

7.5 Configuration of messages

7.6 Selecting the received messages using Message Selector

7.7 Mechanism for ensuring a highly-reliable message delivery

7.7.1 Types of problems occurring during message delivery and how to ensure reliability

7.7.2 Using transactions

7.7.3 Controlling the message flow rate

7.8 CJMSP Broker functionality

7.8.1 Connection services

7.8.2 Destination management and routing services

7.8.3 CJMSP Broker performance monitoring

7.8.4 Management information and message persistence services

7.9 CJMSP resource adapter functionality

7.10 Invoking a Message-driven Bean

7.10.1 Features of message processing using the Message-driven Beans

7.10.2 Procedure of invoking the Message-driven Beans

7.10.3 Settings required in the Message-driven Beans

7.10.4 Setting up the transaction context

7.11 Restrictions on implementing applications

7.12 Definitions in the DD

7.13 Flow of execution environment setup

7.14 CJMSP Broker settings

7.14.1 Setting up the common properties and the management command properties of CJMSP Broker

7.14.2 Creating CJMSP Broker

7.14.3 Setting up the individual properties of CJMSP Brokers

7.14.4 Starting CJMSP Broker

7.14.5 Creating destinations

7.15 CJMSP resource adapter settings

7.16 J2EE application settings

7.17 Starting and stopping the system when Cosminexus JMS Provider is used

7.17.1 System starting procedure

7.17.2 System stopping procedure

7.17.3 Checking the CJMSP Broker status

7.18 Checking the troubleshooting information

7.19 Notes on using Cosminexus JMS Provider

8. Using JavaMail

8.1 Organization of this chapter

8.2 Session properties

8.2.1 Session properties for connecting to the SMTP server

8.2.2 Session properties for connecting to the POP3 server

8.3 Notes on using JavaMail

9. Using CDI with Application Server

9.1 Organization of this chapter

9.2 Overview of the CDI

9.3 Application development using the CDI

9.3.1 CDI-target applications

9.3.2 Injective relationship of the CDI-target J2EE modules

9.3.3 Notes on development

9.4 Setting up the class path (Development environment settings)

9.4.1 File storage destinations

9.4.2 Class path settings

9.5 Settings for using the CDI (Changing the security settings)

9.6 Using the debug log (check development log)

9.7 Setting up the execution environment

9.8 Notes on using the CDI

10. Using Bean Validation with Application Server

10.1 Organization of this chapter

10.2 Overview of Bean Validation

10.3 Applicable scope of Bean Validation

10.4 Bean Validation functionality and Bean Validation operations

10.5 Procedures for using Bean Validation

10.5.1 Procedures for using Bean Validation from JSF

10.5.2 Procedures for using Bean Validation from CDI

10.6 Using the debug log (check development log)

10.7 Output of information when the validation.xml contents are invalid

10.8 Notes on the implementation of Bean Validation

11. Managing Application Attributes

11.1 Organization of this chapter

11.2 Managing attributes

11.3 Applications containing cosminexus.xml

11.3.1 cosminexus.xml

11.3.2 Advantages of using the applications containing cosminexus.xml

11.3.3 Creating the applications containing cosminexus.xml

11.3.4 Creating cosminexus.xml

11.3.5 Example of creating cosminexus.xml

11.3.6 Operations of the applications containing cosminexus.xml

11.3.7 Procedure of migrating from the applications not containing cosminexus.xml

11.4 Omitting the DD

11.4.1 Configuration of applications that can be executed with Application Server

11.4.2 Differences in functionality depending on the presence of application.xml

11.4.3 Rules for determining the modules when application.xml exists

11.4.4 Rules for determining the modules when application.xml does not exist

11.4.5 Operations for Web applications in which web.xml is omitted

11.4.6 Display name specified when the DD is omitted

11.4.7 Operations for creating application.xml when application.xml is omitted

11.4.8 Notes on adding resources in the J2EE applications when application.xml is omitted

12. Using Annotations

12.1 Organization of this chapter

12.2 Specifying annotations

12.2.1 Merits of using annotations and the annotations that can be specified

12.2.2 Using the library JAR class with a declared annotation

12.2.3 Implementing the Enterprise Beans when an annotation is specified

12.3 Classes to be loaded and the class path required for loading

12.4 Using the DI

12.4.1 Types of resources that can be specified in the @Resource annotation

12.4.2 Resolving the resource references using the @Resource annotation

12.4.3 Operations during DI failure

12.4.4 Notes

12.5 Controlling the annotation references

12.5.1 Purpose and scope of the functionality for controlling the annotation references

12.5.2 Timing for referencing annotations

12.5.3 Definitions in the DD (module settings)

12.5.4 Changing the settings for the functionality for controlling the annotation references

12.6 Updating the contents defined in the annotations

12.6.1 Updating the annotations

12.6.2 Overwriting the annotations using the DD

12.6.3 Referencing and updating the definitions with the server management commands

12.7 Notes on using annotations

13. Formats and Deployment of J2EE Applications

13.1 Organization of this chapter

13.2 Executable J2EE application formats

13.3 Archive-format J2EE applications

13.4 Exploded archive-format J2EE applications

13.4.1 Overview of the exploded archive format

13.4.2 Configuration of the application directory

13.4.3 Settings for using the exploded archive-format J2EE applications (changing the security settings)

13.4.4 Notes on using the exploded archive format

13.5 Deploying and un-deploying J2EE applications

13.5.1 Deploying and un-deploying J2EE applications in the archive format

13.5.2 Deploying and un-deploying J2EE applications in the exploded archive-format

13.5.3 Deploying the EAR files and ZIP files in the exploded archive format

13.5.4 Setting up the J2EE application properties

13.6 Replacing J2EE applications

13.7 Redeploying J2EE applications

13.7.1 Replacing J2EE applications by redeploying

13.7.2 Statuses and replacement of J2EE applications

13.7.3 Notes on replacing J2EE applications by redeploying

13.8 Detecting updates and reloading the J2EE applications

13.8.1 How to reload the J2EE applications

13.8.2 Scope of reloading

13.8.3 Class loader configuration used for reloading

13.8.4 Operations when an error occurs

13.8.5 Files for update detection

13.8.6 Update detection interval for J2EE applications

13.8.7 Interval for updating the J2EE application configuration file

13.8.8 Reloading the Web applications

13.8.9 Reloading the JSPs

13.8.10 Relationship with the other functionality

13.8.11 Reloading the J2EE applications using commands

13.8.12 Settings for detecting updates and reloading the J2EE applications

13.8.13 Notes and restrictions related to reloading

13.9 WAR applications

13.9.1 Support range of the operation commands for WAR applications

13.9.2 Executable WAR application formats

13.9.3 Replacing WAR applications

13.9.4 Names of WAR applications

13.9.5 Determining the context root

13.9.6 Reading the cosminexus.xml file

14. Container Extension Library

14.1 Organization of this chapter

14.2 Using the container extension library

14.3 Container extension library functionality

14.3.1 Determining the usage of the container extension library

14.3.2 Procedure of creating and using the container extension library

14.3.3 Settings for using the container extension library functionality

14.4 Server start and stop hook functionality

14.4.1 Invocation order of the server start and stop hook processing

14.4.2 Implementing the server start and stop hook functionality

14.4.3 Specifying the class path for using the server start and stop hook functionality

14.5 Invoking the CORBA objects through Smart Agent

14.5.1 Notes on the implementation of the CORBA object invocation processing

14.5.2 Notes on the packaging of the CORBA object invocation processing

14.6 Constraints on using the container extension library and server start and stop hook functionality

15. Notes on Implementation of Applications

15.1 Notes on using the thread-local variables

15.2 Notes on Developer's Kit for Java

15.2.1 Notes common to Application Server versions

15.2.2 Notes related to the differences in specifications with JDK 1.4.2 provided in Application Server Version 6

15.2.3 Notes related to the differences in specifications with JDK 5.0 provided in Application Server Version 7 and Version 8

15.3 Notes on using loggers beginning with sun.rmi

Appendix

A. Character Codes

A.1 Character codes handled in an application

A.2 Character code conversion between the browser and application

B. Configuration of the Class Loader

B.1 Default class loader configuration

B.2 Class loader configuration for local call optimization

B.3 Class path set in the class loader

C. Contract Between the JPA Provider and EJB Container

C.1 Runtime-related contract

C.2 Deployment-related contract

D. BNF for JPQL

E. Use Cases for Cosminexus JMS Provider

E.1 Preconditions common to all the use cases

E.2 Prerequisite process model

E.3 Environment setup for using Cosminexus JMS Provider

E.4 Adding applications that use Cosminexus JMS Provider

E.5 Deleting applications that use Cosminexus JMS Provider

E.6 Starting the Cosminexus JMS Provider services (for the initial startup)

E.7 Starting the Cosminexus JMS Provider services (for restarting a running system)

E.8 Checking the state of the CJMSP resource adapters and CJMSP Broker

E.9 Checking the message delivery status and the action to be taken for accumulated messages (Procedure for pausing CJMSP Broker)

E.10 Checking the message delivery status and the action to be taken for accumulated messages (Procedure for stopping an application)

E.11 Terminating the Cosminexus JMS Provider services

E.12 Compressing the destinations

E.13 Changing the destination size

E.14 Deleting the persistence subscribers

E.15 Monitoring the CJMSP Broker status

E.16 Checking the CJMSP Broker details

E.17 Checking the destination status

E.18 Checking the persistence subscriber status

E.19 Analysis of errors in the CJMSP resource adapters

E.20 Analysis when CJMSP Broker stops due to an error

E.21 Analysis when there is no response from a Cosminexus JMS Provider service

E.22 Recovery when an error occurs in a CJMSP resource adapter

E.23 Recovery when CJMSP Broker stops due to an error

E.24 Recovery when there is no response from a Cosminexus JMS Provider service

E.25 Deleting the Cosminexus JMS Provider service instances

F. Main Functionality Changes in Each Version

F.1 Main functionality changes in 09-00

F.2 Main functionality changes in 08-70

F.3 Main functionality changes in 08-53

F.4 Main functionality changes in 08-50

F.5 Main functionality changes in 08-00

G. Glossary

Index