US20090043897A1 - System and method for detecting a connection leak in a j2ee connector architecture - Google Patents
System and method for detecting a connection leak in a j2ee connector architecture Download PDFInfo
- Publication number
- US20090043897A1 US20090043897A1 US12/030,655 US3065508A US2009043897A1 US 20090043897 A1 US20090043897 A1 US 20090043897A1 US 3065508 A US3065508 A US 3065508A US 2009043897 A1 US2009043897 A1 US 2009043897A1
- Authority
- US
- United States
- Prior art keywords
- connection
- application component
- connector architecture
- connections
- calling
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/465—Distributed object oriented systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/0223—User address space allocation, e.g. contiguous or non contiguous base addressing
- G06F12/023—Free address space management
- G06F12/0253—Garbage collection, i.e. reclamation of unreferenced memory
Definitions
- the current invention relates generally to connector architectures, and more particularly to detecting connection leaks in a J2EE connector architecture.
- J2EE JavaTM 2 Platform, Enterprise Edition
- Java Microsystems, Inc. of Palo Alto, Calif.
- a J2EE Connector Architecture is useful for the integration of J2EE-compliant application servers with at least one enterprise information system (EIS).
- EIS enterprise information system
- the J2EE Connector Architecture also defines a common client interface (CCI) that can be used to access an EIS.
- CCI defines a client API for interacting with heterogeneous EIS systems, which enables application components and Enterprise Application Integration (EAI) frameworks to drive interactions across heterogeneous EIS systems using a common client API.
- EAI Enterprise Application Integration
- a resource adapter is a segment of code that represents an Enterprise Information System (EIS). More specifically, a resource adaptor is a system-level software driver used by an application server such as WebLogic Server is used to connect to an enterprise information system (EIS).
- EIS enterprise information system
- a resource adapter serves as the “J2EE connector.”
- the connector architecture implementation supports resource adapters developed by EIS vendors and third-party application developers that can be deployed in any application server supporting the Sun Microsystems J2EE Platform Specification, Version 1.3. Resource adapters contain the Java, and if necessary, the native components required to interact with the EIS.
- J2EE Connector Architecture is an architecture for integrating J2EE-compliant application servers with enterprise information systems (EIS). There are two parts to this architecture: an EIS vendor-provided resource adapter and an application server, such as WebLogic Server, by BEA Systems of San Jose, Calif., to which the resource adapter plugs in. This architecture defines a set of contracts, such as transactions, security, and connection management, that both the resource adapter and application server need to support to communicate with one another.
- the J2EE Connector Architecture also defines a Common Client Interface (CCI) for EIS access.
- the CCI defines a client API for interacting with heterogeneous EIS's.
- connection leaks may be detected both automatically and manually.
- Connection pools for an EIS may be configured to more efficiently fulfill connection requests.
- connection pools are pre-populated when the application server starts up.
- connection pools that experience reduced usage are decreased in size.
- Managed connections may be recycled to fulfill connection requests.
- managed connections may be monitored by an administrator. A user may monitor connections such as leaking connections and idle connections and delete connections as needed.
- FIG. 1 is an illustration of a connector architecture in accordance with one embodiment of the present invention.
- FIG. 2 is an illustration of a method for automatically detecting a connection leak in accordance with one embodiment of the present invention.
- FIG. 3 is an illustration of a method for manually detecting a connection leak in accordance with one embodiment of the present invention.
- FIG. 4 is an illustration of a method for configuring a connection pool in accordance with one embodiment of the present invention.
- FIG. 5 is an illustration of a method for controlling connection pool shrinkage in accordance with one embodiment of the present invention.
- FIG. 6 is an illustration of a method for monitoring connections in accordance with one embodiment of the present invention.
- FIG. 7 is an illustration of a method for storing credentials in accordance with one embodiment of the present invention.
- a connector architecture implementation is provided that is J2EE compliant and provides improved connection management capabilities.
- the connector architecture implementation provides a connector leak detection mechanism.
- the connector leak detector may detect connection leaks both automatically and manually.
- the connector architecture implementation is operable to pre-configure a connection pool and manage the growth and reduction of a connection pool.
- the connector architecture implementation may be pre-configured by pre-populating the connection pool.
- Connection pool growth may be managed by connections that are created in response to connection requests.
- a connection pool in the present invention may also be configured to reduce the number of connections in the pool. In one embodiment, the number of connections is reduced if the connection demand decreases. Password credentials allowing access to services are used to provide additional connection management.
- FIG. 1 is an illustration of a connector architecture implementation 100 in accordance with one embodiment of the present invention.
- Connector architecture implementation 100 includes application server 110 , resource adapter 120 , enterprise information system (EIS) 130 , and application component 140 .
- EIS enterprise information system
- the connector architecture implementation is compatible with J2EE.
- the connector architecture implementation may be implemented in an application server and an EIS-specific resource adapter.
- a resource adapter is a system level software driver used by an application server to connect to an EIS.
- a resource adapter may serve as a connector.
- Resource adapters contain the Java and any native components required for the application server to interact with the EIS.
- the connector architecture of the present invention supports resource adapters developed by EIS vendors and third party application developers that can be deployed in any application server supporting the J2EE platform specification.
- An EIS provides the information infrastructure for an enterprise and offers a set of services to its clients. The services may be exposed to clients as local or remote interfaces, or both.
- An application component may be an EJB, JSP, or servlet that is deployed, managed, or executed on an application server.
- the connector architecture implementation 100 of FIG. 1 further includes system level contracts.
- System level contracts exist between the resource adapter and the application server.
- the contracts may relate to connection management or other aspects of the connector architecture.
- Connection management contracts allow an application server the ability to provide a pool of connections to underlying EISs that enable application components to connect to an EIS.
- the connection management relates to connection pool configuration, connection pool management, and connection management.
- connection pool holds all available managed connections to this EIS.
- connector applications may not close the connection object.
- a connection object that is not closed after the application has completed using the connection object is considered a leaking connection.
- FIG. 2 illustrates a method 200 for detecting connection leaks automatically.
- Method 200 begins with start step 210 .
- an application component terminates in step 220 .
- the connection object used by the application component becomes de-referenced.
- the garbage collector calls a connection object in step 230 .
- the “finalize( )” method of a connection object is called by the garbage collector. Operation then continues to step 240 .
- the connector architecture implementation determines if the application component closed the connection object at step 240 .
- the method proceeds to end step 260 . If the application component did not close the connection object and the application server confirms that it is safe, then the connection object is closed in step 250 . In one embodiment, the server automatically closes the connection object in step 250 . The server may close the connection object by calling the resource adapter's “ManagedConnection.cleanup( )” method. The application server then operates as it would have if it received a “ConnectionClosed” event upon a proper closure of the application component connection. After closing the connection object in step 250 , the method ends in step 260 .
- a leak detection system in addition to the automatic leak detection system is desirable.
- the garbage collector may not call the finalize( ) method of the connection object used by the faulty application component. In this situation, additional leak detection methods would be useful for establishing increased connection management efficiency.
- the connector architecture implementation of the present invention also provides for a manual leak detection mechanism.
- the manual leak detection mechanism may be advantageous in detecting leaks when the garbage collector is unreliable and in the case of multiple connection object references.
- a method 300 for manual leak detection performed within the connector architecture of the present invention is shown in FIG. 3 .
- Method 300 begins with start step 310 .
- step 320 the connector architecture implementation determines whether the application component is actively using the connection it has requested.
- An active connection is a connection wherein an application component is currently using a requested connection object by calling methods on it or calling a request for a connection object request. If the application component connection is determined to be active, then operation returns to step 320 . If an application component connection is determined to be inactive, operation continues to step 330 .
- a mechanism is triggered to monitor the time an application component connection is inactive.
- the mechanism is a timer.
- the timer measures the last time a particular connection was active.
- a timer may be configured to transpire in seconds for each connection associated with an EIS.
- step 340 if an inactive connection becomes active while the timer transpires, operation continues to step 320 . While the connection remains inactive, operation continues to step 350 and the timer continues to transpire.
- the particular value is configured as a maximum idle time parameter.
- the maximum idle time parameter is a period of time in which after it has elapsed, the connection is considered expired.
- step 370 the connector architecture implementation determines if there is a demand for a managed connection. In one embodiment, a demand for a managed connection exists if the connection pool has reached a maximum capacity of managed connections and the connector architecture implementation receives a managed connection request. If either no connection request has been made or a connection request has been made but the connection pool may fulfill the request, then operation regarding the particular connection object request continues to step 340 . If the connection pool has no available allocated connections and a connection request is made, operation continues to step 380 . In step 380 , the connector architecture implementation closes the connection object associated with the timer that has exceeded the maximum idle time parameter. The managed connection is now available to service connection requests. Operation of the manual leak detection system then ends in step 390 .
- the connector architecture implementation of the present invention may configure a connection pool for an EIS to aid in fulfilling connection requests.
- the connection pool can be configured for pre-population. Pre-populating the connection pool with an initial number of managed connections is done upon startup of the application server and connector architecture implementation of the present invention. This pre-population prevents experiencing a decrease in performance when the managed connections are later created upon request.
- FIG. 4 illustrates a method 400 for configuring a connection pool in accordance with one embodiment of the present invention. Method 400 begins with start step 405 . Next, the connector architecture implementation of the present invention determines whether or not an EIS is configured in such a manner as to pre-populate the connection pool associated with the EIS with an initial number of managed connections.
- connection pool is populated with managed connections.
- the number of managed connections used to pre-populate a connection pool may be configured by a pre-population parameter.
- the parameter is specific to a particular connection pool associated with the resource adapter.
- the pre-population parameter is an initial-capacity element, located in an XML formatted descriptor file of the connector architecture implementation of the present invention. The initial capacity element specifies how many managed connections a connection pool should be pre-populated with at the deployment of a resource adapter with the application server. In one embodiment of the present invention, pre-population of managed connections may not be done where runtime parameters are required.
- connection increment parameter is then configured in step 430 .
- the connection increment parameter represents the number of managed connections that are created at the time a connection request is made.
- the connection increment parameter allows a user to control the connection pool growth and when to incur the performance and processing costs of connection pool growth.
- the connection increment parameter is a capacity-increment element located in an XML formatted descriptor file of the connector architecture implementation of the present invention.
- a connection request is then received in step 440 .
- a connection request may involve an application component requesting a connection object to an EIS through the resource adapter.
- the connector architecture implementation determines whether the request may be fulfilled with existing available managed connections in step 450 . If the connection request can be fulfilled, then operation continues to step 480 . If the connection request can not be fulfilled with existing and available managed connections, the operation continues to step 460 .
- step 460 it is determined whether creating a new managed connection will exceed a maximum allowed number of managed connections.
- the maximum number of allowed connections is determined by a maximum-capacity element located in an XML formatted descriptor file of the connector architecture implementation of the present invention.
- the maximum number of managed connections may be configured for a single EIS.
- more than one managed connection may be created when a connection request is received and no available managed connections exist.
- the number of managed connections created may correspond to the capacity-increment parameter.
- the connector architecture implementation will attempt to add three managed connections if a connection request can not be fulfilled by existing and available managed connections.
- step 465 the new managed connections are created within the connection pool. If adding the new managed connections does bring the number of managed connections over the maximum allowed for an EIS, then operation continues to step 470 .
- connection architecture implementation determines whether or not managed connections can be recycled in step 470 .
- recycling includes terminating connection objects that are determined to be inactive.
- the connector architecture implementation may determine a connection object is inactive according to the method 300 for manually detecting connection leaks as illustrated in FIG. 3 and discussed above.
- step 370 if it is determined that the timer associated with a connection has transpired and a connection request is received in step 370 , then the connection object will be closed in step 380 and recycled for use in step 470 . If no connection objects exist that can be recycled, then operation continues to step 475 where a warning is logged and the connection request fails. If existing connection objects may be recycled to meet the connection request, the connection request is fulfilled in step 480 . Operation then ends in step 495 .
- the connector architecture implementation of the present invention can manage the reduction of the connection pool.
- the connector architecture implementation may monitor the managed connection usage and reduce the size of the connection pool if the usage has decreased.
- a method 500 for reducing the number of managed connections in accordance with one embodiment of the present invention is illustrated in FIG. 5 .
- Method 500 begins with start step 510 .
- the connector architecture implementation of the present invention determines whether managed connection usage has decreased in step 520 . If the managed connection usage has decreased through the use of fewer managed connections or in some other manner, then operation continues to step 530 . If the managed connection usage has not decreased, then operation returns to step 520 .
- the connector architecture implementation determines if the managed connection usage decrease has existed for a specified period of time.
- the period of time may be configured as a parameter in the shrink-period-minutes element located in an XML formatted descriptor file of the connector architecture implementation.
- the period of time is associated with a single connection pool associated with the resource adapter. If the usage decrease has not existed for the specified period of time, then operation returns to step 520 . If the usage decrease has existed for the specified period of time, operation continues to step 540 .
- the size of the connection pool is decreased in step 540 . In one embodiment, at least one managed connection is closed to reduce the size of the connection pool.
- connection object usage is monitored by taking “snapshots” of connection object usage at intervals of time, the snapshots triggered by a monitor timer.
- shrinking is detected as a result of a comparison of the snapshots, or if the connector architecture determines shrinking should occur, the connection pool is reduced to the higher of the initial-capacity of the pool or the average usage level.
- the method for reduction of the connection pool may be enabled or disabled by the user.
- reduction of the connection pool may be enabled by configuring a shrinking-enabled element located in an XML formatted descriptor file of the connector architecture implementation.
- the connector architecture implementation may also provide for monitoring of managed connections.
- a user may view and monitor managed connections. Types of managed connections to view and monitor may include leaked and idle connections.
- a connection-profiling-enabled element located in an XML formatted descriptor file of the connector architecture implementation indicates whether a connection pool should store the call stacks of where each connection is allocated. In one embodiment, if the connection-profiling-enabled element is configured to be true, the stacks for leaked, and idle connections can be viewed and a user may debug components that fail to close connection objects.
- a method 600 for monitoring of connections in accordance with one embodiment of the present invention is illustrated in FIG. 6 . Method 600 begins with start step 610 .
- a user may choose between viewing information regarding and monitoring leaked connections and idle connections. If leaked connections are to be viewed, then operation continues to step 630 .
- a user may view information regarding leaked connections.
- the leaked connection information may be displayed through a console, a log window, or some other manner.
- the leaked connection information may include run time information of leaked connections, profile information.
- profile information displayed includes dates from the call stack of the connection object usage. This data helps the administrator determine which application or application component caused the leak.
- idle connections are to be viewed, then operation continues to step 640 .
- idle information such as profile information for idle connections may be viewed by a user.
- a user may then decide to delete a connection object in step 650 .
- a leaked connection object may be deleted if the connection object has exceeded a specified idle time and is not involved in a transaction. If no connection is to be deleted, then operation continues to step 670 . If a connection object is to be deleted, then operation continues to step 660 where the connection object is deleted. Next, operation continues to step 670 where a user may view more connections or end the monitoring of managed connections. If a user wishes to further monitor managed connections, operation continues to step 620 . If no further monitoring of managed connections is to occur, operation ends at step 680 .
- the connector architecture implementation provides security management.
- credentials are stored in a javax.securtiy.auth.Subject object to comply with Sun's J2EE Connector Specification, version 1.0 final release.
- a method 700 for storing credentials in accordance with one embodiment of the present invention is shown in FIG. 7 .
- Method 700 begins with start step 710 .
- an EIS resource object is instantiated in step 710 .
- a weblogic.security.Service.EISResource object is instantiated with the following command:
- the command is executed from the security management code of the WebLogic Server.
- the initiating principal for the connection request is obtained in step 730 .
- the initiating principal is obtained by querying the WebLogic Server security code for the user initiated principal associated with the application component making the connection request.
- credentials for the initiating principal are obtained in step 740 .
- the credentials are obtained with the following command:
- a Subject file is then instantiated in step 750 .
- the file is a javax.security.auth.Subject.
- credentials are added to the subject file in step 760 .
- the credentials are added to the private set in the credentials with the following command:
- the Subject file is then completed and method 700 ends at step 770 .
- the connector architecture implementation of the present invention is provided that is J2EE compliant and provides improved connection management capabilities.
- the connector architecture implementation provides a connector leak detection mechanism.
- the connector leak detector may detect connection leaks both automatically and manually.
- the connector architecture implementation is operable to pre-configure a connection pool and manage the growth and reduction of a connection pool.
- the connector architecture may be pre-configured by pre-populating the connection pool.
- Connection pool growth may be managed by connections that are created in response to connection requests.
- a connection pool in the present invention may also be configured to reduce the number of connections in the pool. In one embodiment, the number of connections is reduced if the connection demand decreases. Password credentials allowing access to services are used to provide additional connection management.
- the present invention may be conveniently implemented using a conventional general purpose or a specialized digital computer or microprocessor programmed according to the teachings of the present disclosure, as will be apparent to those skilled in the computer art.
- the present invention includes a computer program product which is a storage medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the processes of the present invention.
- the storage medium can include, but is not limited to, any type of disk including floppy disks, optical discs, DVD, CD-ROMs, microdrive, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data.
- the present invention includes software for controlling both the hardware of the general purpose/specialized computer or microprocessor, and for enabling the computer or microprocessor to interact with a human user or other mechanism utilizing the results of the present invention.
- software may include, but is not limited to, device drivers, operating systems, and user applications.
- computer readable media further includes software for performing the methods of the present invention.
- ⁇ Included in the programming (software) of the general/specialized computer or microprocessor are software modules for implementing the teachings of the present invention, including, but not limited to, separating planes of a source image, averaging at least one of foreground and background colors, replacing colors, and compensating for error introduced by color replacement in one plane by feeding error into a second plane, storage, communication of results, and reconstructing an image according to the processes of the present invention.
Abstract
A connector architecture implementation that is J2EE compliant and provides improved connection management capabilities. The connector architecture implementation provides a connector leak detection mechanism that detects connection leaks both automatically and manually. The connector architecture implementation pre-configures and manages the growth and reduction of a connection pool. The connector architecture implementation may be pre-configured by pre-populating the connection pool. Connection pool growth may be managed by generating connections in response to connection requests. A connection pool may also be configured to reduce the number of connections in the pool. The number of connections may be reduced if the connection demand decreases. Password credentials allowing access to services are used to provide additional connection management.
Description
- This application is a divisional of pending U.S. patent application Ser. No. 10/248,744 entitled “J2EE CONNECTOR ARCHITECTURE,” by Deborah C. June, et al., filed Feb. 13, 2003, which claims the benefit of U.S. Provisional Patent Application No. 60/406,745 filed Aug. 29, 2002, which applications are incorporated herein.
- The current application hereby incorporates by reference the material in the following patent applications:
- U.S. patent Application No. 60/354,738, entitled “J2EE COMPONENT EXTENSION ARCHITECTURE,” filed Feb. 6, 2002; and
- U.S. Patent Application No. 60/397,916, entitled “SYSTEM AND METHOD FOR IMPLEMENTING J2EE CONNECTOR ARCHITECTURE,” filed Jul. 23, 2002.
- A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
- The current invention relates generally to connector architectures, and more particularly to detecting connection leaks in a J2EE connector architecture.
- The Java™ 2 Platform, Enterprise Edition (J2EE), from Sun Microsystems, Inc. of Palo Alto, Calif., defines a standard for developing multi-tier enterprise applications. A J2EE Connector Architecture is useful for the integration of J2EE-compliant application servers with at least one enterprise information system (EIS). There are typically two parts to this architecture: an EIS vendor-provided resource adapter and an application server to which the resource adapter plugs in. The J2EE Connector Architecture also defines a common client interface (CCI) that can be used to access an EIS. A CCI defines a client API for interacting with heterogeneous EIS systems, which enables application components and Enterprise Application Integration (EAI) frameworks to drive interactions across heterogeneous EIS systems using a common client API.
- A resource adapter is a segment of code that represents an Enterprise Information System (EIS). More specifically, a resource adaptor is a system-level software driver used by an application server such as WebLogic Server is used to connect to an enterprise information system (EIS). A resource adapter serves as the “J2EE connector.” The connector architecture implementation supports resource adapters developed by EIS vendors and third-party application developers that can be deployed in any application server supporting the Sun Microsystems J2EE Platform Specification, Version 1.3. Resource adapters contain the Java, and if necessary, the native components required to interact with the EIS.
- J2EE Connector Architecture is an architecture for integrating J2EE-compliant application servers with enterprise information systems (EIS). There are two parts to this architecture: an EIS vendor-provided resource adapter and an application server, such as WebLogic Server, by BEA Systems of San Jose, Calif., to which the resource adapter plugs in. This architecture defines a set of contracts, such as transactions, security, and connection management, that both the resource adapter and application server need to support to communicate with one another. The J2EE Connector Architecture also defines a Common Client Interface (CCI) for EIS access. The CCI defines a client API for interacting with heterogeneous EIS's.
- What is needed is an improved connector architecture implementation system that is more efficient and allows an administrator to monitor and make changes to connections within the application server as needed.
- A connector architecture implementation is provided that includes advantageous features in connection management as well as other areas. In one embodiment of the present invention, connector leaks may be detected both automatically and manually. Connection pools for an EIS may be configured to more efficiently fulfill connection requests. In one embodiment, connection pools are pre-populated when the application server starts up. In another embodiment, connection pools that experience reduced usage are decreased in size. Managed connections may be recycled to fulfill connection requests. In another embodiment, managed connections may be monitored by an administrator. A user may monitor connections such as leaking connections and idle connections and delete connections as needed.
-
FIG. 1 is an illustration of a connector architecture in accordance with one embodiment of the present invention. -
FIG. 2 is an illustration of a method for automatically detecting a connection leak in accordance with one embodiment of the present invention. -
FIG. 3 is an illustration of a method for manually detecting a connection leak in accordance with one embodiment of the present invention. -
FIG. 4 is an illustration of a method for configuring a connection pool in accordance with one embodiment of the present invention. -
FIG. 5 is an illustration of a method for controlling connection pool shrinkage in accordance with one embodiment of the present invention. -
FIG. 6 is an illustration of a method for monitoring connections in accordance with one embodiment of the present invention. -
FIG. 7 is an illustration of a method for storing credentials in accordance with one embodiment of the present invention. - A connector architecture implementation is provided that is J2EE compliant and provides improved connection management capabilities. In one embodiment of the present invention, the connector architecture implementation provides a connector leak detection mechanism. The connector leak detector may detect connection leaks both automatically and manually. In another embodiment of the present invention, the connector architecture implementation is operable to pre-configure a connection pool and manage the growth and reduction of a connection pool. The connector architecture implementation may be pre-configured by pre-populating the connection pool. Connection pool growth may be managed by connections that are created in response to connection requests. A connection pool in the present invention may also be configured to reduce the number of connections in the pool. In one embodiment, the number of connections is reduced if the connection demand decreases. Password credentials allowing access to services are used to provide additional connection management.
-
FIG. 1 is an illustration of aconnector architecture implementation 100 in accordance with one embodiment of the present invention.Connector architecture implementation 100 includesapplication server 110,resource adapter 120, enterprise information system (EIS) 130, andapplication component 140. In one embodiment of the present invention, the connector architecture implementation is compatible with J2EE. The connector architecture implementation may be implemented in an application server and an EIS-specific resource adapter. - A resource adapter is a system level software driver used by an application server to connect to an EIS. A resource adapter may serve as a connector. Resource adapters contain the Java and any native components required for the application server to interact with the EIS. In one embodiment, the connector architecture of the present invention supports resource adapters developed by EIS vendors and third party application developers that can be deployed in any application server supporting the J2EE platform specification. An EIS provides the information infrastructure for an enterprise and offers a set of services to its clients. The services may be exposed to clients as local or remote interfaces, or both. An application component may be an EJB, JSP, or servlet that is deployed, managed, or executed on an application server.
- The
connector architecture implementation 100 ofFIG. 1 further includes system level contracts. System level contracts exist between the resource adapter and the application server. The contracts may relate to connection management or other aspects of the connector architecture. Connection management contracts allow an application server the ability to provide a pool of connections to underlying EISs that enable application components to connect to an EIS. In one embodiment of the present invention, the connection management relates to connection pool configuration, connection pool management, and connection management. - In connector systems, multiple applications may attempt to establish a connection with the EIS. One connection pool holds all available managed connections to this EIS. Sometimes, after connecting to and using the services of an EIS, connector applications may not close the connection object. A connection object that is not closed after the application has completed using the connection object is considered a leaking connection.
- In one embodiment of the present invention, leak detection is performed automatically by leveraging the garbage collector.
FIG. 2 illustrates amethod 200 for detecting connection leaks automatically.Method 200 begins withstart step 210. Next, an application component terminates instep 220. Once an application component terminates, the connection object used by the application component becomes de-referenced. After the application component terminates, the garbage collector calls a connection object instep 230. In one embodiment, the “finalize( )” method of a connection object is called by the garbage collector. Operation then continues to step 240. In one embodiment, the connector architecture implementation then determines if the application component closed the connection object atstep 240. If the application component was determined to have closed the connection, or if the application server determines it is not safe to close the connection object, (for example, another application has a reference to the connection object), the method proceeds to endstep 260. If the application component did not close the connection object and the application server confirms that it is safe, then the connection object is closed instep 250. In one embodiment, the server automatically closes the connection object instep 250. The server may close the connection object by calling the resource adapter's “ManagedConnection.cleanup( )” method. The application server then operates as it would have if it received a “ConnectionClosed” event upon a proper closure of the application component connection. After closing the connection object instep 250, the method ends instep 260. - In some instances, a leak detection system in addition to the automatic leak detection system is desirable. For example, the garbage collector may not call the finalize( ) method of the connection object used by the faulty application component. In this situation, additional leak detection methods would be useful for establishing increased connection management efficiency.
- The connector architecture implementation of the present invention also provides for a manual leak detection mechanism. The manual leak detection mechanism may be advantageous in detecting leaks when the garbage collector is unreliable and in the case of multiple connection object references. A
method 300 for manual leak detection performed within the connector architecture of the present invention is shown inFIG. 3 .Method 300 begins withstart step 310. Next, instep 320 the connector architecture implementation determines whether the application component is actively using the connection it has requested. An active connection is a connection wherein an application component is currently using a requested connection object by calling methods on it or calling a request for a connection object request. If the application component connection is determined to be active, then operation returns to step 320. If an application component connection is determined to be inactive, operation continues to step 330. Instep 330, a mechanism is triggered to monitor the time an application component connection is inactive. In one embodiment, the mechanism is a timer. The timer measures the last time a particular connection was active. In one embodiment, a timer may be configured to transpire in seconds for each connection associated with an EIS. Instep 340, if an inactive connection becomes active while the timer transpires, operation continues to step 320. While the connection remains inactive, operation continues to step 350 and the timer continues to transpire. Instep 360, it is determined whether or not the timer has reached a particular value. In one embodiment, the particular value is configured as a maximum idle time parameter. The maximum idle time parameter is a period of time in which after it has elapsed, the connection is considered expired. If the value of the timer is less then the maximum idle time parameter instep 360, operation continues to step 340. If the value of the timer has reached the maximum idle time parameter, then operation continues to step 370. Instep 370, the connector architecture implementation determines if there is a demand for a managed connection. In one embodiment, a demand for a managed connection exists if the connection pool has reached a maximum capacity of managed connections and the connector architecture implementation receives a managed connection request. If either no connection request has been made or a connection request has been made but the connection pool may fulfill the request, then operation regarding the particular connection object request continues to step 340. If the connection pool has no available allocated connections and a connection request is made, operation continues to step 380. Instep 380, the connector architecture implementation closes the connection object associated with the timer that has exceeded the maximum idle time parameter. The managed connection is now available to service connection requests. Operation of the manual leak detection system then ends instep 390. - In addition to detecting connection leaks, the connector architecture implementation of the present invention may configure a connection pool for an EIS to aid in fulfilling connection requests. In one embodiment, the connection pool can be configured for pre-population. Pre-populating the connection pool with an initial number of managed connections is done upon startup of the application server and connector architecture implementation of the present invention. This pre-population prevents experiencing a decrease in performance when the managed connections are later created upon request.
FIG. 4 illustrates amethod 400 for configuring a connection pool in accordance with one embodiment of the present invention.Method 400 begins withstart step 405. Next, the connector architecture implementation of the present invention determines whether or not an EIS is configured in such a manner as to pre-populate the connection pool associated with the EIS with an initial number of managed connections. If the connection pool is not to be pre-populated, then operation continues to step 430. If pre-population is to occur, then operation continues to step 420. Instep 420, the connection pool is populated with managed connections. In one embodiment, the number of managed connections used to pre-populate a connection pool may be configured by a pre-population parameter. The parameter is specific to a particular connection pool associated with the resource adapter. In one embodiment of the present invention, the pre-population parameter is an initial-capacity element, located in an XML formatted descriptor file of the connector architecture implementation of the present invention. The initial capacity element specifies how many managed connections a connection pool should be pre-populated with at the deployment of a resource adapter with the application server. In one embodiment of the present invention, pre-population of managed connections may not be done where runtime parameters are required. - A connection increment parameter is then configured in
step 430. The connection increment parameter represents the number of managed connections that are created at the time a connection request is made. The connection increment parameter allows a user to control the connection pool growth and when to incur the performance and processing costs of connection pool growth. In one embodiment, the connection increment parameter is a capacity-increment element located in an XML formatted descriptor file of the connector architecture implementation of the present invention. - A connection request is then received in
step 440. In one embodiment, a connection request may involve an application component requesting a connection object to an EIS through the resource adapter. Once a connection request is received, the connector architecture implementation determines whether the request may be fulfilled with existing available managed connections instep 450. If the connection request can be fulfilled, then operation continues to step 480. If the connection request can not be fulfilled with existing and available managed connections, the operation continues to step 460. - In
step 460, it is determined whether creating a new managed connection will exceed a maximum allowed number of managed connections. In one embodiment, the maximum number of allowed connections is determined by a maximum-capacity element located in an XML formatted descriptor file of the connector architecture implementation of the present invention. The maximum number of managed connections may be configured for a single EIS. In one embodiment, more than one managed connection may be created when a connection request is received and no available managed connections exist. In particular, the number of managed connections created may correspond to the capacity-increment parameter. Thus, if the connection increment parameter has a value of three, then the connector architecture implementation will attempt to add three managed connections if a connection request can not be fulfilled by existing and available managed connections. In any case, if adding managed connections in the amount of the connection increment parameter does not bring the number of managed connections associated with an EIS over the maximum managed connections allowed for that EIS, then operation continues to step 465 where the new managed connections are created within the connection pool. If adding the new managed connections does bring the number of managed connections over the maximum allowed for an EIS, then operation continues to step 470. - The connection architecture implementation determines whether or not managed connections can be recycled in
step 470. In one embodiment, recycling includes terminating connection objects that are determined to be inactive. The connector architecture implementation may determine a connection object is inactive according to themethod 300 for manually detecting connection leaks as illustrated inFIG. 3 and discussed above. In particular, instep 370, if it is determined that the timer associated with a connection has transpired and a connection request is received instep 370, then the connection object will be closed instep 380 and recycled for use instep 470. If no connection objects exist that can be recycled, then operation continues to step 475 where a warning is logged and the connection request fails. If existing connection objects may be recycled to meet the connection request, the connection request is fulfilled instep 480. Operation then ends instep 495. - In addition to managing the growth of a connection pool, the connector architecture implementation of the present invention can manage the reduction of the connection pool. In one embodiment of the present invention, the connector architecture implementation may monitor the managed connection usage and reduce the size of the connection pool if the usage has decreased. A
method 500 for reducing the number of managed connections in accordance with one embodiment of the present invention is illustrated inFIG. 5 .Method 500 begins withstart step 510. Next, the connector architecture implementation of the present invention determines whether managed connection usage has decreased instep 520. If the managed connection usage has decreased through the use of fewer managed connections or in some other manner, then operation continues to step 530. If the managed connection usage has not decreased, then operation returns to step 520. Instep 530, the connector architecture implementation determines if the managed connection usage decrease has existed for a specified period of time. In one embodiment of the present invention, the period of time may be configured as a parameter in the shrink-period-minutes element located in an XML formatted descriptor file of the connector architecture implementation. The period of time is associated with a single connection pool associated with the resource adapter. If the usage decrease has not existed for the specified period of time, then operation returns to step 520. If the usage decrease has existed for the specified period of time, operation continues to step 540. The size of the connection pool is decreased instep 540. In one embodiment, at least one managed connection is closed to reduce the size of the connection pool. The connector architecture implementation may close a number of managed connections to establish a number of managed connections to efficiently satisfy ongoing connection requests In one embodiment, connection object usage is monitored by taking “snapshots” of connection object usage at intervals of time, the snapshots triggered by a monitor timer. When shrinking is detected as a result of a comparison of the snapshots, or if the connector architecture determines shrinking should occur, the connection pool is reduced to the higher of the initial-capacity of the pool or the average usage level. In one embodiment, the method for reduction of the connection pool may be enabled or disabled by the user. In one embodiment, reduction of the connection pool may be enabled by configuring a shrinking-enabled element located in an XML formatted descriptor file of the connector architecture implementation. - The connector architecture implementation may also provide for monitoring of managed connections. In one embodiment of the present invention, a user may view and monitor managed connections. Types of managed connections to view and monitor may include leaked and idle connections. In one embodiment of the present invention, a connection-profiling-enabled element located in an XML formatted descriptor file of the connector architecture implementation indicates whether a connection pool should store the call stacks of where each connection is allocated. In one embodiment, if the connection-profiling-enabled element is configured to be true, the stacks for leaked, and idle connections can be viewed and a user may debug components that fail to close connection objects. A
method 600 for monitoring of connections in accordance with one embodiment of the present invention is illustrated inFIG. 6 .Method 600 begins withstart step 610. Next, a user may choose between viewing information regarding and monitoring leaked connections and idle connections. If leaked connections are to be viewed, then operation continues to step 630. Instep 630, a user may view information regarding leaked connections. The leaked connection information may be displayed through a console, a log window, or some other manner. The leaked connection information may include run time information of leaked connections, profile information. In one embodiment, profile information displayed includes dates from the call stack of the connection object usage. This data helps the administrator determine which application or application component caused the leak. If idle connections are to be viewed, then operation continues to step 640. Instep 640, idle information such as profile information for idle connections may be viewed by a user. After viewing connection information insteps step 650. In one embodiment, a leaked connection object may be deleted if the connection object has exceeded a specified idle time and is not involved in a transaction. If no connection is to be deleted, then operation continues to step 670. If a connection object is to be deleted, then operation continues to step 660 where the connection object is deleted. Next, operation continues to step 670 where a user may view more connections or end the monitoring of managed connections. If a user wishes to further monitor managed connections, operation continues to step 620. If no further monitoring of managed connections is to occur, operation ends atstep 680. - The connector architecture implementation provides security management. In one embodiment of the present invention, credentials are stored in a javax.securtiy.auth.Subject object to comply with Sun's J2EE Connector Specification, version 1.0 final release. A
method 700 for storing credentials in accordance with one embodiment of the present invention is shown inFIG. 7 .Method 700 begins withstart step 710. Next, an EIS resource object is instantiated instep 710. In one embodiment, a weblogic.security.Service.EISResource object is instantiated with the following command: -
new EISResource(java.lang.String applicationName, java.lang.String moduleName, java.lang.String eisName) - The command is executed from the security management code of the WebLogic Server. Next, the initiating principal for the connection request is obtained in
step 730. In one embodiment, the initiating principal is obtained by querying the WebLogic Server security code for the user initiated principal associated with the application component making the connection request. Then, credentials for the initiating principal are obtained instep 740. In one embodiment, the credentials are obtained with the following command: -
weblogic.security.Service.PrincipalAuthenticator(String initiatingPrincipal,weblogic.security.Service.Resource eisResource) - A Subject file is then instantiated in
step 750. In one embodiment, the file is a javax.security.auth.Subject. Then, credentials are added to the subject file instep 760. In one embodiment, the credentials are added to the private set in the credentials with the following command: - Subject.getPrivateCredentials( ).add(Credential)
- The Subject file is then completed and
method 700 ends atstep 770. - The connector architecture implementation of the present invention is provided that is J2EE compliant and provides improved connection management capabilities. In one embodiment of the present invention, the connector architecture implementation provides a connector leak detection mechanism. The connector leak detector may detect connection leaks both automatically and manually. In another embodiment of the present invention, the connector architecture implementation is operable to pre-configure a connection pool and manage the growth and reduction of a connection pool. The connector architecture may be pre-configured by pre-populating the connection pool. Connection pool growth may be managed by connections that are created in response to connection requests. A connection pool in the present invention may also be configured to reduce the number of connections in the pool. In one embodiment, the number of connections is reduced if the connection demand decreases. Password credentials allowing access to services are used to provide additional connection management.
- In addition to an embodiment consisting of specifically designed integrated circuits or other electronics, the present invention may be conveniently implemented using a conventional general purpose or a specialized digital computer or microprocessor programmed according to the teachings of the present disclosure, as will be apparent to those skilled in the computer art.
- Appropriate software coding can readily be prepared by skilled programmers based on the teachings of the present disclosure, as will be apparent to those skilled in the software art. The invention may also be implemented by the preparation of application specific integrated circuits or by interconnecting an appropriate network of conventional component circuits, as will be readily apparent to those skilled in the art.
- The present invention includes a computer program product which is a storage medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the processes of the present invention. The storage medium can include, but is not limited to, any type of disk including floppy disks, optical discs, DVD, CD-ROMs, microdrive, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data.
- Stored on any one of the computer readable medium (media), the present invention includes software for controlling both the hardware of the general purpose/specialized computer or microprocessor, and for enabling the computer or microprocessor to interact with a human user or other mechanism utilizing the results of the present invention. Such software may include, but is not limited to, device drivers, operating systems, and user applications. Ultimately, such computer readable media further includes software for performing the methods of the present invention.
- Included in the programming (software) of the general/specialized computer or microprocessor are software modules for implementing the teachings of the present invention, including, but not limited to, separating planes of a source image, averaging at least one of foreground and background colors, replacing colors, and compensating for error introduced by color replacement in one plane by feeding error into a second plane, storage, communication of results, and reconstructing an image according to the processes of the present invention.
- Other features, aspects and objects of the invention can be obtained from a review of the figures and the claims. It is to be understood that other embodiments of the invention can be developed and fall within the spirit and scope of the invention and claims.
- The foregoing description of embodiments of the present invention has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Obviously, many modifications and variations will be apparent to the practitioner skilled in the art. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, thereby enabling others skilled in the art to understand the invention for various embodiments and with various modifications that are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the following claims and their equivalents.
Claims (16)
1. A method of automatically detecting a connection leak in a connector architecture implementation comprising:
terminating an application component, the application component forming a connection with an enterprise information system;
calling a connection object;
determining if the connection used by an application component is closed; and
closing the connection.
2. The method of claim 1 wherein calling a connection object includes a garbage collector calling the connection object.
3. The method of claim 2 wherein calling a connection object includes the garbage collector calling a method of the connection object.
4. The method of claim 1 wherein closing the connection includes an application server automatically closing the connection.
5. The method of claim 4 wherein closing the connection includes the application server calling a method from the resource adapter.
6. A method of manually detecting a connection leak in a connector architecture implementation comprising:
determining that an application component is inactive and not actively using a connection between the application component and an enterprise information system;
receiving a connection request; and
determining whether the application component has been inactive for a first time period before said receiving a connection request.
7. The method of claim 6 further comprising:
closing the connection if the application component has been inactive for a first time period before said receiving a connection request.
8. The method of claim 6 wherein determining whether the application component has been inactive for a certain time period includes providing a timer, the timer configured to start when the application component is determined to be inactive.
9. A computer-readable storage medium, storing instructions for automatically detecting a connection leak in a connector architecture implementation, the instructions comprising:
terminating an application component, the application component forming a connection with an enterprise information system;
calling a connection object;
determining if the connection used by an application component is closed; and
closing the connection.
10. The computer-readable storage medium of claim 9 wherein calling a connection object includes a garbage collector calling the connection object.
11. The computer-readable storage medium of claim 10 wherein calling a connection object includes the garbage collector calling a method of the connection object.
12. The computer-readable storage medium of claim 9 wherein closing the connection includes an application server automatically closing the connection.
13. The computer-readable storage medium of claim 12 wherein closing the connection includes the application server calling a method from the resource adapter.
14. A computer-readable storage medium of manually detecting a connection leak in a connector architecture implementation comprising:
determining that an application component is inactive and not actively using a connection between the application component and an enterprise information system;
receiving a connection request; and
determining whether the application component has been inactive for a first time period before said receiving a connection request.
15. The computer-readable storage medium of claim 14 further comprising:
closing the connection if the application component has been inactive for a first time period before said receiving a connection request.
16. The computer-readable storage medium of claim 14 wherein determining whether the application component has been inactive for a certain time period includes providing a timer, the timer configured to start when the application component is determined to be inactive.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/030,655 US20090043897A1 (en) | 2002-08-29 | 2008-02-13 | System and method for detecting a connection leak in a j2ee connector architecture |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US40674502P | 2002-08-29 | 2002-08-29 | |
US10/248,744 US7698434B2 (en) | 2002-08-29 | 2003-02-13 | J2EE connector architecture |
US12/030,655 US20090043897A1 (en) | 2002-08-29 | 2008-02-13 | System and method for detecting a connection leak in a j2ee connector architecture |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/248,744 Division US7698434B2 (en) | 2002-08-29 | 2003-02-13 | J2EE connector architecture |
Publications (1)
Publication Number | Publication Date |
---|---|
US20090043897A1 true US20090043897A1 (en) | 2009-02-12 |
Family
ID=31980999
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/248,744 Expired - Lifetime US7698434B2 (en) | 2002-08-29 | 2003-02-13 | J2EE connector architecture |
US12/030,655 Abandoned US20090043897A1 (en) | 2002-08-29 | 2008-02-13 | System and method for detecting a connection leak in a j2ee connector architecture |
US12/030,660 Expired - Lifetime US8463922B2 (en) | 2002-08-29 | 2008-02-13 | Method for storing credentials in a J2EE connector architecture |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/248,744 Expired - Lifetime US7698434B2 (en) | 2002-08-29 | 2003-02-13 | J2EE connector architecture |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/030,660 Expired - Lifetime US8463922B2 (en) | 2002-08-29 | 2008-02-13 | Method for storing credentials in a J2EE connector architecture |
Country Status (3)
Country | Link |
---|---|
US (3) | US7698434B2 (en) |
AU (1) | AU2003268215A1 (en) |
WO (1) | WO2004021125A2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050120117A1 (en) * | 2003-11-26 | 2005-06-02 | International Business Machines Corporation | Efficient connection pool validation |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7080145B2 (en) * | 2003-02-28 | 2006-07-18 | Bea Systems, Inc. | Method for performing resource pool maintenance by maintaining resources in several deques |
US7263554B2 (en) | 2003-02-28 | 2007-08-28 | Bea Systems, Inc. | Method and system for performing resource pool maintenance by refreshing resources based on the pool resource test |
US7080126B2 (en) * | 2003-02-28 | 2006-07-18 | Bea Systems, Inc. | Computer program product for performing resource pool maintenance by maintaining resources in several deques |
US7734677B2 (en) * | 2005-09-29 | 2010-06-08 | International Business Machines Corporation | Method, system and program product for dynamically integrating backend systems into a J2EE application server environment |
US20080270974A1 (en) * | 2007-04-30 | 2008-10-30 | Krasimir Topchiyski | Enterprise JavaBeans Metadata Model |
US8539504B2 (en) * | 2007-08-30 | 2013-09-17 | International Business Machines Corporation | Heterogeneous architecture in pooling management |
US8949421B2 (en) * | 2009-07-29 | 2015-02-03 | Teradata Us, Inc. | Techniques for discovering database connectivity leaks |
US20110179303A1 (en) * | 2010-01-15 | 2011-07-21 | Microsoft Corporation | Persistent application activation and timer notifications |
US8626928B2 (en) | 2010-11-22 | 2014-01-07 | International Business Machines Corporation | Disassociating and freeing managed connections based on usage patterns |
WO2012093193A1 (en) * | 2011-01-07 | 2012-07-12 | Nokia Corporation | Method and apparatus for statistical handling of connections |
US10389652B2 (en) | 2014-12-19 | 2019-08-20 | International Business Machines Corporation | Connection pool management |
US9794372B2 (en) * | 2015-04-07 | 2017-10-17 | At&T Intellectual Property I, L.P. | Connection management service |
US11176155B2 (en) * | 2019-12-13 | 2021-11-16 | Paypal, Inc | Self-adjusting connection pool in a distributed system |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6721777B1 (en) * | 2000-05-24 | 2004-04-13 | Sun Microsystems, Inc. | Modular and portable deployment of a resource adapter in an application server |
US20060080435A1 (en) * | 2004-06-07 | 2006-04-13 | Tankov Nikolai D | Resource adapter deployment |
US20080270600A1 (en) * | 2007-04-30 | 2008-10-30 | Nikolai Tankov | Method for Connection Leak Detection and Prevention |
US7454492B2 (en) * | 2005-08-26 | 2008-11-18 | International Business Machines Corporation | Method and apparatus for configuring and modeling server information in an enterprise tooling environment |
US7484224B2 (en) * | 2002-05-02 | 2009-01-27 | Bae Systems, Inc. | Adapter deployment without recycle |
US7506342B2 (en) * | 2002-07-23 | 2009-03-17 | Bea Systems, Inc. | System and method for implementing J2EE connector architecture |
US7546606B2 (en) * | 2001-10-18 | 2009-06-09 | Bea Systems, Inc. | System and method using a connector architecture for application integration |
Family Cites Families (113)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4714996A (en) * | 1985-11-26 | 1987-12-22 | International Business Machines Corporation | Impact calculation for version management in a distributed information service |
US5163148A (en) * | 1989-08-11 | 1992-11-10 | Digital Equipment Corporation | File backup system for producing a backup copy of a file which may be updated during backup |
US5319773A (en) * | 1990-05-16 | 1994-06-07 | International Business Machines Corporation | Asynchronous resynchronization of a commit procedure |
US5249290A (en) * | 1991-02-22 | 1993-09-28 | At&T Bell Laboratories | Method of and apparatus for operating a client/server computer network |
IL100987A (en) | 1991-02-27 | 1995-10-31 | Digital Equipment Corp | Method and apparatus for compiling code |
US5212793A (en) * | 1991-09-04 | 1993-05-18 | International Business Machines Corp. | Generic initiators |
US6026452A (en) * | 1997-02-26 | 2000-02-15 | Pitts; William Michael | Network distributed site cache RAM claimed as up/down stream request/reply channel for storing anticipated data and meta data |
US5586260A (en) | 1993-02-12 | 1996-12-17 | Digital Equipment Corporation | Method and apparatus for authenticating a client to a server in computer systems which support different security mechanisms |
US5553242A (en) * | 1993-11-03 | 1996-09-03 | Wang Laboratories, Inc. | Client/server connection sharing |
US5787246A (en) * | 1994-05-27 | 1998-07-28 | Microsoft Corporation | System for configuring devices for a computer system |
EP0694837A1 (en) * | 1994-07-25 | 1996-01-31 | International Business Machines Corporation | Dynamic workload balancing |
US5751967A (en) | 1994-07-25 | 1998-05-12 | Bay Networks Group, Inc. | Method and apparatus for automatically configuring a network device to support a virtual network |
US5682478A (en) * | 1995-01-19 | 1997-10-28 | Microsoft Corporation | Method and apparatus for supporting multiple, simultaneous services over multiple, simultaneous connections between a client and network server |
US5802291A (en) * | 1995-03-30 | 1998-09-01 | Sun Microsystems, Inc. | System and method to control and administer distributed object servers using first class distributed objects |
US5903731A (en) * | 1995-06-14 | 1999-05-11 | Us West Technologies, Inc. | System and associated method for re-engineering a telecommunications network support system with object-oriented translators |
DE69610168D1 (en) * | 1995-06-30 | 2000-10-12 | Ibm | Single sign-on method and apparatus in a distributed computing environment |
US5748975A (en) | 1995-07-06 | 1998-05-05 | Sun Microsystems, Inc. | System and method for textual editing of structurally-represented computer programs with on-the-fly typographical display |
US5835769A (en) | 1995-09-19 | 1998-11-10 | Sun Microsystems, Inc. | Apparatti and computer program products for integrating editors with applications |
US5774689A (en) * | 1995-09-22 | 1998-06-30 | Bell Atlantic Network Services, Inc. | Network configuration management system for digital communication networks |
US6212556B1 (en) * | 1995-11-13 | 2001-04-03 | Webxchange, Inc. | Configurable value-added network (VAN) switching |
US5910180A (en) * | 1995-11-21 | 1999-06-08 | Diamond Multimedia Systems, Inc. | Context virtualizing device driver architecture |
US5765171A (en) * | 1995-12-29 | 1998-06-09 | Lucent Technologies Inc. | Maintaining consistency of database replicas |
US5761507A (en) * | 1996-03-05 | 1998-06-02 | International Business Machines Corporation | Client/server architecture supporting concurrent servers within a server with a transaction manager providing server/connection decoupling |
US6182109B1 (en) * | 1996-03-08 | 2001-01-30 | International Business Machines Corporation | Dynamic execution unit management for high performance user level network server system |
US5894554A (en) * | 1996-04-23 | 1999-04-13 | Infospinner, Inc. | System for managing dynamic web page generation requests by intercepting request at web server and routing to page server thereby releasing web server to process other requests |
US6173327B1 (en) * | 1996-07-11 | 2001-01-09 | Jeroen De Borst | Object-oriented method and apparatus for information delivery |
US5805798A (en) | 1996-10-29 | 1998-09-08 | Electronic Data Systems Corporation | Fail-safe event driven transaction processing system and method |
GB2320112B (en) | 1996-12-07 | 2001-07-25 | Ibm | High-availability computer server system |
US5933838A (en) * | 1997-03-10 | 1999-08-03 | Microsoft Corporation | Database computer system with application recovery and recovery log sequence numbers to optimize recovery |
US6353923B1 (en) | 1997-03-12 | 2002-03-05 | Microsoft Corporation | Active debugging environment for debugging mixed-language scripting code |
CA2201278C (en) | 1997-03-27 | 2001-02-20 | Ibm Canada Limited-Ibm Canada Limitee | Hierarchical metadata store for an integrated development environment |
US6189046B1 (en) * | 1997-03-27 | 2001-02-13 | Hewlett-Packard Company | Mechanism and method for merging cached location information in a distributed object environment |
US6134673A (en) * | 1997-05-13 | 2000-10-17 | Micron Electronics, Inc. | Method for clustering software applications |
US5909689A (en) * | 1997-09-18 | 1999-06-01 | Sony Corporation | Automatic update of file versions for files shared by several computers which record in respective file directories temporal information for indicating when the files have been created |
JP3901806B2 (en) * | 1997-09-25 | 2007-04-04 | 富士通株式会社 | Information management system and secondary server |
US6356931B2 (en) | 1997-10-06 | 2002-03-12 | Sun Microsystems, Inc. | Method and system for remotely browsing objects |
US6425005B1 (en) * | 1997-10-06 | 2002-07-23 | Mci Worldcom, Inc. | Method and apparatus for managing local resources at service nodes in an intelligent network |
US5926775A (en) * | 1997-10-08 | 1999-07-20 | National Instruments Corporation | Mini driver software architecture for a data acquisition system |
US6018805A (en) * | 1997-12-15 | 2000-01-25 | Recipio | Transparent recovery of distributed-objects using intelligent proxies |
US6453356B1 (en) * | 1998-04-15 | 2002-09-17 | Adc Telecommunications, Inc. | Data exchange system and method |
US6122629A (en) * | 1998-04-30 | 2000-09-19 | Compaq Computer Corporation | Filesystem data integrity in a single system image environment |
US6105067A (en) * | 1998-06-05 | 2000-08-15 | International Business Machines Corp. | Connection pool management for backend servers using common interface |
US6243753B1 (en) * | 1998-06-12 | 2001-06-05 | Microsoft Corporation | Method, system, and computer program product for creating a raw data channel form an integrating component to a series of kernel mode filters |
US6338089B1 (en) * | 1998-10-06 | 2002-01-08 | Bull Hn Information Systems Inc. | Method and system for providing session pools for high performance web browser and server communications |
US6304879B1 (en) * | 1998-11-25 | 2001-10-16 | Microsoft Corporation | Dynamic data cache for object-oriented computing environments |
US6389462B1 (en) * | 1998-12-16 | 2002-05-14 | Lucent Technologies Inc. | Method and apparatus for transparently directing requests for web objects to proxy caches |
US6438705B1 (en) * | 1999-01-29 | 2002-08-20 | International Business Machines Corporation | Method and apparatus for building and managing multi-clustered computer systems |
US6453321B1 (en) * | 1999-02-11 | 2002-09-17 | Ibm Corporation | Structured cache for persistent objects |
US6269373B1 (en) * | 1999-02-26 | 2001-07-31 | International Business Machines Corporation | Method and system for persisting beans as container-managed fields |
US6430564B1 (en) * | 1999-03-01 | 2002-08-06 | Hewlett-Packard Company | Java data manager for embedded device |
US6523130B1 (en) * | 1999-03-11 | 2003-02-18 | Microsoft Corporation | Storage system having error detection and recovery |
US6466972B1 (en) * | 1999-03-31 | 2002-10-15 | International Business Machines Corporation | Server based configuration of network computers via machine classes |
US6539381B1 (en) | 1999-04-21 | 2003-03-25 | Novell, Inc. | System and method for synchronizing database information |
EP1049307A1 (en) * | 1999-04-29 | 2000-11-02 | International Business Machines Corporation | Method and system for dispatching client sessions within a cluster of servers connected to the World Wide Web |
US6463503B1 (en) * | 1999-05-12 | 2002-10-08 | International Business Machines Corporation | Method and system for increasing concurrency during staging and destaging in a log structured array |
US6343287B1 (en) * | 1999-05-19 | 2002-01-29 | Sun Microsystems, Inc. | External data store link for a profile service |
US6411956B1 (en) * | 1999-06-14 | 2002-06-25 | Sun Microsystems, Inc. | Method for distributed transaction support using JDBC 1.0 drivers |
US6405219B2 (en) * | 1999-06-22 | 2002-06-11 | F5 Networks, Inc. | Method and system for automatically updating the version of a set of files stored on content servers |
US6963857B1 (en) * | 1999-07-12 | 2005-11-08 | Jsa Technologies | Network-accessible account system |
US7100195B1 (en) * | 1999-07-30 | 2006-08-29 | Accenture Llp | Managing user information on an e-commerce system |
CA2280588C (en) * | 1999-08-20 | 2005-07-05 | Leonard W. Theivendra | Code wrapping to simplify access to and use of enterprise java beans |
US6356933B2 (en) * | 1999-09-07 | 2002-03-12 | Citrix Systems, Inc. | Methods and apparatus for efficiently transmitting interactive application data between a client and a server using markup language |
US6553387B1 (en) * | 1999-11-29 | 2003-04-22 | Microsoft Corporation | Logical volume configuration data management determines whether to expose the logical volume on-line, off-line request based on comparison of volume epoch numbers on each extents of the volume identifiers |
US20020010781A1 (en) * | 1999-12-30 | 2002-01-24 | Tuatini Jeffrey Taihana | Shared service messaging models |
US6854120B1 (en) * | 2000-01-14 | 2005-02-08 | International Business Machines Corporation | Accessing a ERP application over the internet using strongly typed declarative language files |
US6757708B1 (en) | 2000-03-03 | 2004-06-29 | International Business Machines Corporation | Caching dynamic content |
US6775703B1 (en) * | 2000-05-01 | 2004-08-10 | International Business Machines Corporation | Lease based safety protocol for distributed system with multiple networks |
US6832238B1 (en) * | 2000-05-24 | 2004-12-14 | Sun Microsystems, Inc. | Local transaction management |
US7089584B1 (en) * | 2000-05-24 | 2006-08-08 | Sun Microsystems, Inc. | Security architecture for integration of enterprise information system with J2EE platform |
US6687848B1 (en) * | 2000-05-31 | 2004-02-03 | Sun Microsystems, Inc. | Techniques for preventing information loss in a business to business message in an enterprise computer system |
US7171692B1 (en) * | 2000-06-27 | 2007-01-30 | Microsoft Corporation | Asynchronous communication within a server arrangement |
US6505200B1 (en) | 2000-07-06 | 2003-01-07 | International Business Machines Corporation | Application-independent data synchronization technique |
US7099926B1 (en) | 2000-07-06 | 2006-08-29 | International Business Machines Corporation | Object caching and update queuing technique to improve performance and resource utilization |
AU2001280489A1 (en) * | 2000-07-07 | 2002-01-21 | Consilient, Inc. | Method and apparatus for providing process-container platforms |
US6732237B1 (en) | 2000-08-29 | 2004-05-04 | Oracle International Corporation | Multi-tier caching system |
US6651140B1 (en) * | 2000-09-01 | 2003-11-18 | Sun Microsystems, Inc. | Caching pattern and method for caching in an object-oriented programming environment |
US6542845B1 (en) * | 2000-09-29 | 2003-04-01 | Sun Microsystems, Inc. | Concurrent execution and logging of a component test in an enterprise computer system |
US20050223392A1 (en) * | 2000-12-01 | 2005-10-06 | Cox Burke D | Method and system for integration of software applications |
US20020073188A1 (en) * | 2000-12-07 | 2002-06-13 | Rawson Freeman Leigh | Method and apparatus for partitioning system management information for a server farm among a plurality of leaseholds |
US6675261B2 (en) * | 2000-12-22 | 2004-01-06 | Oblix, Inc. | Request based caching of data store data |
US7188145B2 (en) * | 2001-01-12 | 2007-03-06 | Epicrealm Licensing Llc | Method and system for dynamic distributed data caching |
US20030212987A1 (en) * | 2001-02-28 | 2003-11-13 | Demuth Steven J. | Client container for building EJB-hosted java applications |
US20020161860A1 (en) * | 2001-02-28 | 2002-10-31 | Benjamin Godlin | Method and system for differential distributed data file storage, management and access |
GB2373069B (en) * | 2001-03-05 | 2005-03-23 | Ibm | Method, apparatus and computer program product for integrating heterogeneous systems |
US7240101B2 (en) * | 2001-04-02 | 2007-07-03 | International Business Machines Corporation | Method and apparatus for efficiently reflecting complex systems of objects in XML documents |
US6711579B2 (en) * | 2001-04-20 | 2004-03-23 | Sree Ayyanar Spinning And Weaving Mills Limited | Data storage schema independent programming for data retrieval using semantic bridge |
US7203756B2 (en) * | 2001-04-27 | 2007-04-10 | International Business Machines Corporation | Mechanism to cache references to Java RMI remote objects implementing the unreferenced interface |
US7543066B2 (en) * | 2001-04-30 | 2009-06-02 | International Business Machines Corporation | Method and apparatus for maintaining session affinity across multiple server groups |
US7152090B2 (en) * | 2001-06-01 | 2006-12-19 | Sun Microsystems, Inc. | Metadata-aware enterprise application integration framework for application server environment |
US6567809B2 (en) * | 2001-06-08 | 2003-05-20 | International Business Machines Corporation | Disabling and reloading enterprise java beans using database trigger programs |
US7571215B2 (en) * | 2001-07-16 | 2009-08-04 | Bea Systems, Inc. | Data replication protocol |
WO2003009610A1 (en) | 2001-07-18 | 2003-01-30 | Telcontar | System and method for initiating responses to location-based events |
US6766324B2 (en) | 2001-07-20 | 2004-07-20 | International Business Machines Corporation | System and method for defining, configuring and using dynamic, persistent Java classes |
US6944785B2 (en) * | 2001-07-23 | 2005-09-13 | Network Appliance, Inc. | High-availability cluster virtual server system |
US7568000B2 (en) * | 2001-08-21 | 2009-07-28 | Rosemount Analytical | Shared-use data processing for process control systems |
US7249131B2 (en) * | 2001-09-06 | 2007-07-24 | Initiate Systems, Inc. | System and method for dynamically caching dynamic multi-sourced persisted EJBs |
US6826601B2 (en) * | 2001-09-06 | 2004-11-30 | Bea Systems, Inc. | Exactly one cache framework |
US6983465B2 (en) | 2001-10-11 | 2006-01-03 | Sun Microsystems, Inc. | Method and apparatus for managing data caching in a distributed computer system |
EP2309384A1 (en) * | 2001-10-29 | 2011-04-13 | Accenture Global Services GmbH | A generic connector between vitria and an EJB compliant API for an application |
US20030105837A1 (en) * | 2001-11-30 | 2003-06-05 | Yury Kamen | Interception for optimal caching of distributed applications |
US6949590B2 (en) * | 2002-01-10 | 2005-09-27 | University Of Washington | Hydrogels formed by non-covalent linkages |
US6898587B2 (en) * | 2002-01-18 | 2005-05-24 | Bea Systems, Inc. | System and method for performing commutative operations in data access systems |
US7392302B2 (en) * | 2002-02-21 | 2008-06-24 | Bea Systems, Inc. | Systems and methods for automated service migration |
US20030182426A1 (en) * | 2002-03-21 | 2003-09-25 | Sun Microsystems, Inc. | Apparatus and method of lazy connection transaction enlistment |
US7089317B2 (en) | 2002-03-21 | 2006-08-08 | Sun Microsystems, Inc. | Architecture for plugging messaging systems into an application server |
US7490334B2 (en) * | 2002-04-25 | 2009-02-10 | Sun Microsystems, Inc. | Resource adapter with modular system management interface |
US6804686B1 (en) | 2002-04-29 | 2004-10-12 | Borland Software Corporation | System and methodology for providing fixed UML layout for an object oriented class browser |
WO2003093964A1 (en) * | 2002-05-01 | 2003-11-13 | Bea Systems, Inc. | Enterprise application platform |
US20030233631A1 (en) * | 2002-06-13 | 2003-12-18 | Ambrose Curry | Web services development method |
US20040059735A1 (en) | 2002-09-10 | 2004-03-25 | Gold Russell Eliot | Systems and methods for enabling failover in a distributed-object computing environment |
US20040153558A1 (en) | 2002-10-31 | 2004-08-05 | Mesut Gunduc | System and method for providing java based high availability clustering framework |
TW556873U (en) * | 2002-11-27 | 2003-10-01 | Hon Hai Prec Ind Co Ltd | Locking device for disk driver |
US7962915B2 (en) * | 2005-03-18 | 2011-06-14 | International Business Machines Corporation | System and method for preserving state for a cluster of data servers in the presence of load-balancing, failover, and fail-back events |
-
2003
- 2003-02-13 US US10/248,744 patent/US7698434B2/en not_active Expired - Lifetime
- 2003-08-27 AU AU2003268215A patent/AU2003268215A1/en not_active Abandoned
- 2003-08-27 WO PCT/US2003/026891 patent/WO2004021125A2/en not_active Application Discontinuation
-
2008
- 2008-02-13 US US12/030,655 patent/US20090043897A1/en not_active Abandoned
- 2008-02-13 US US12/030,660 patent/US8463922B2/en not_active Expired - Lifetime
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6721777B1 (en) * | 2000-05-24 | 2004-04-13 | Sun Microsystems, Inc. | Modular and portable deployment of a resource adapter in an application server |
US7546606B2 (en) * | 2001-10-18 | 2009-06-09 | Bea Systems, Inc. | System and method using a connector architecture for application integration |
US7484224B2 (en) * | 2002-05-02 | 2009-01-27 | Bae Systems, Inc. | Adapter deployment without recycle |
US7506342B2 (en) * | 2002-07-23 | 2009-03-17 | Bea Systems, Inc. | System and method for implementing J2EE connector architecture |
US20060080435A1 (en) * | 2004-06-07 | 2006-04-13 | Tankov Nikolai D | Resource adapter deployment |
US7454492B2 (en) * | 2005-08-26 | 2008-11-18 | International Business Machines Corporation | Method and apparatus for configuring and modeling server information in an enterprise tooling environment |
US20080270600A1 (en) * | 2007-04-30 | 2008-10-30 | Nikolai Tankov | Method for Connection Leak Detection and Prevention |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050120117A1 (en) * | 2003-11-26 | 2005-06-02 | International Business Machines Corporation | Efficient connection pool validation |
US8041821B2 (en) * | 2003-11-26 | 2011-10-18 | International Business Machines Corporation | Connection pool management |
Also Published As
Publication number | Publication date |
---|---|
AU2003268215A8 (en) | 2004-03-19 |
US20040045008A1 (en) | 2004-03-04 |
AU2003268215A1 (en) | 2004-03-19 |
US20090043892A1 (en) | 2009-02-12 |
US7698434B2 (en) | 2010-04-13 |
WO2004021125A2 (en) | 2004-03-11 |
US8463922B2 (en) | 2013-06-11 |
WO2004021125A3 (en) | 2004-05-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8463922B2 (en) | Method for storing credentials in a J2EE connector architecture | |
US6067634A (en) | System and method for resource recovery in a distributed system | |
US6266678B1 (en) | System and method for dynamically viewing contents of a data file | |
US7302609B2 (en) | Method and apparatus for executing applications on a distributed computer system | |
US7725766B2 (en) | System for synchronizing replicas of a database | |
US20080134182A1 (en) | Computer readable storage medium for protection against interleaving transactions using a transaction manager | |
US7529818B2 (en) | System and method for performing validation of a configuration | |
US20110078687A1 (en) | System and method for supporting resource enlistment synchronization | |
US20020087734A1 (en) | System and method for managing dependencies in a component-based system | |
EP1171817A2 (en) | Data distribution in a server cluster | |
US6959392B1 (en) | Information providing system and method for providing information | |
US7287075B2 (en) | System for monitoring managed server health | |
US8458725B2 (en) | Computer implemented method for removing an event registration within an event notification infrastructure | |
US8448182B2 (en) | System and method for pause and resume message operations on destinations | |
US7281027B2 (en) | Distributed processing system and network monitoring system | |
US6728895B1 (en) | System and method for resource recovery in a distributed system | |
US8255502B2 (en) | Dynamic domain administration utility | |
EP1484859B1 (en) | Control method with opaque user identifier administration for complete delivering of a multi-server service | |
WO2005114398A2 (en) | Production redeployment through application versioning | |
WO2021254112A1 (en) | Methods for reporting usage, and network function and storage medium | |
JP3760749B2 (en) | Connection management method, computer system, and computer-readable recording medium recording a program for realizing the method | |
EP3661140A1 (en) | Method for applying for common service resource, related device, and system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |