System and method for message driven bean service migration

• US 20030163761A1
• Filed: 02/20/2003
• Published: 08/28/2003
• Est. Priority Date: 02/21/2002
• Status: Abandoned Application

• Current Assignee: BEA Systems Incorporated (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Kramer, Reto, Chen, Michael
• Application Number:
  US10/371,147
• Publication Number:
  US 20030163761A1
• Time in Patent Office: Days
• US Class Current: 714/10
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A system and method for migrating services in a Java server environment, and particularly to a mechanism for migrating message driven beans. In accordance with the present invention, the JMS server and MDB'"'"'s are designed to be migratable from one application server to another. In order to expedite Message Driven Bean (MDB) recovery in a cluster environment before a failed server restarts, the MDB is implemented as a migratable service. This enables the migratable service framework to migrate the MDB and JMS server to another available server in the same cluster. After migration, MDB obtains ownership of the JMS server, and continues to pull the messages from the JMS server on behalf of the failed server. This allows the backup server to read the message from JMS server and continue the service.

Claims

1. A system for migrating message driven bean services in an application server environment, comprising:

a first application server for receiving messages from a client application for operation by a message driven bean at that server;

a failover mechanism for shutting down said first application server;

a migratable message driven bean service that can be migrated from said first application server to a second application server; and

,

wherein a signal from the failover mechanism to shut down said first application server causes said migratable message driven bean service to receive messages from the client at said second application server, for operation by said migrated message driven bean.

2. The system of claim 1 wherein said message driven bean can be registered as a migratable message driven bean to allow it to participate in the migration process.

3. The system of claim 1 wherein said first application server and said second application servers are Java-based application servers.

4. The system of claim 1 wherein said first application server and said second application server are members of a plurality of application servers in a clustered environment.

5. The system of claim 1 wherein said failover mechanism is initiated automatically upon detecting a failure in said first application server.

6. The system of claim 1 wherein said failover mechanism can be initiated manually by a user or administrator.

7. The system of claim 1 wherein said first application server includes a JMS server, which upon migration of said message driven bean service is also migrated to said second application server.

8. A method for migrating message driven beans services in a Java server environment, comprising the steps of:

receiving messages from a client application at a first application server for operation by a message driven bean at that server;

detecting a failure within said first application server or a command to shut down said first application server;

migrating said message driven bean as a service from said first application server to a second application server; and

,

receiving messages from the client at said second application server, for operation by said migrated message driven bean.

9. The method of claim 8 wherein said message driven bean can be registered as a migratable message driven bean to allow it to participate in the migration process.

10. The method of claim 8 wherein said first application server and said second application servers are Java-based application servers.

11. The method of claim 8 wherein said first application server and said second application server are members of a plurality of application servers in a clustered environment.

12. The method of claim 8 wherein said step of migrating upon failure is initiated automatically upon detecting a failure in said first application server.

13. The method of claim 8 wherein said step of migrating upon failure can be initiated manually by a user or administrator.

14. The method of claim 8 wherein said first application server includes a JMS server, which upon migration of said message driven bean service is also migrated to said second application server.