Patent Grant
7676810
Embodiments of the invention generally relate to the field of computer systems and, more particularly, to a system and method for identification of the execution context of a thread.
In computer operations, including client/server systems, a thread is a particular set of instructions. In a Java™ environment, a thread is the basic unit of program execution. A process may include multiple threads running concurrently, possibly with each thread being involved with a different task. Each thread may operate largely independently from the other active threads.
In monitoring operations of a system, the identity of elements that are working with an active thread may be useful information. For example, a thread may be connected with a particular program component or software unit and with a particular transaction. In a Java environment, a transaction is unit of work that modifies data, which may include one or more program statements. However, a thread may work with numerous different components and transactions, with the components and transactions that are connected with the thread varying over time.
In conventional operations, it is not generally possible to directly identify a component or transaction that is working within a thread at a particular time. Therefore, ability to monitor of a system may be limited and operations may need to rely on external evidence of system processes.
A system and method for identification of the execution context of a thread is described.
In a first embodiment of the invention a method comprises associating a program object with a program thread; storing information concerning the program thread in the program object; and retrieving the information concerning the program thread upon request.
In a second embodiment of the invention a system comprises a processor, the processor to execute an application, the execution of the application to include the execution of a program thread; and a memory, the memory to store a program component, the program component to include the information regarding the current execution environment for the program thread.
Embodiments of the invention are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which like reference numerals refer to similar elements.
Embodiments of the invention are generally directed to a system and method for identification of the component execution context of a thread.
Under an embodiment of the invention, a component is attached to the context of a program thread. In this embodiment, the component contains information regarding the execution context. Under an embodiment of the invention, the object comprises a resource set for the thread.
Under an embodiment of the invention, an interface is provided to enable a user of a system to obtain runtime information about the process of request execution. Under an embodiment of the invention, a process provides for retrieving the existing context for a thread to provide execution context data and replacing such context as the execution of the thread proceeds.
Under an embodiment of the invention, the component and transaction that are currently with a particular thread are identified. Under an embodiment of the invention, an object is attached to the thread context of a thread and this object is utilized to maintain identity information for the thread. Under an embodiment of the invention, an object associated with a program thread carries information regarding the application that is working within the thread. The object may be referred to herein as the component execution context.
In a Java environment, a thread is a single sequential flow of control within a program, representing a thread of execution in a program. In a Java virtual machine, an application may have multiple threads of execution running wholly or partially concurrently. A thread may be referred to as an execution context or a lightweight process. A thread may be utilized to isolate tasks.
However, while threads are said to be concurrent, a computer may have only one physical or logical processor, or fewer processors than the number of threads, so threads actually must share a central processing unit (CPU) with other threads. The execution of multiple threads when sharing one or more CPUs in some order is referred to as scheduling. For example, the Java runtime supports a deterministic scheduling algorithm known as fixed priority scheduling. In this environment, each thread has a priority. Threads with higher priority are executed in preference to threads with lower priority according to the scheduling algorithm.
An embodiment of the invention may operate in a Java environment, such as described in the Java 2 Platform, Enterprise Edition J2EE™ environment provided under the J2EE specification, J2EE (Java 2 Platform, Enterprise Edition), including as provided in the J2EE specification, version 1.4, Nov. 24, 2003. An application sewer is a term used to indicate a component sewer that is compliant with the J2EE environment. In such environment, the application sewer dispatches threads to execute submitted work instances.
Under an embodiment of the invention, an interface may be provided to provide runtime information regarding the execution process. Under an embodiment of the invention, an object associated with a program thread may contain one or more methods to provide information regarding the current execution environment at some point in time. Certain conventional methods involve the context of a thread. For example, current( ) returns the current context for the current thread. Under an embodiment of the invention, a method will further allow a user to obtain additional data, which may include the name of the application, component, or method currently working within a thread; to retrieve the transaction associated with the current thread; to identify the isolation level of the underlying back end system; to manage the object; and additional methods regarding the current execution context.
In addition to ensuring the full completion or rollback of statements that it encloses, a transaction isolates the data modified by these statements. The isolation level describes how visible data being updated is to other transactions. Said in another way, the isolation level is the degree to which the intermediate state of the data being modified by a transaction is visible to other concurrent transactions and data being modified by other transactions is visible to it.
In a Java environment, an application is a program, such as a program running on a server system. An application may reside in a container, the container being an entity that manages life cycle, security, deployment, and runtime services for a component. Under an embodiment of the invention, a component execution context may be utilized by various applications contained on a server, including a sewer that is compatible with the J2EE specification. The applications may include applications utilizing components contained in an Enterprise JavaBean™ (EJB) container and a web container. In this context, a component is a software-unit supported by a container, with components generally being either enterprise beans Enterprise JavaBeans, web components, applets, or application clients.
A program object representing the component execution context may comprise a resource set. Generally a resource set is a program object that keeps handle wrappers. Handle wrappers are the wrappers of connection handles opened by an application component to shared and unshared resources. The resource set also contains information about the application, the program component and the method that uses the resources, and the transactions in which the program component is used. In general terms, a wrapper is an object that encapsulates another object and delegates to the object in some way to alter its interface or behavior.
In
In an embodiment of the invention, the component execution context object includes one or methods to allow a user to access information regarding the current execution environment. If an inquiry regarding the component execution context is received 530, the execution context data is provided 535. The thread may be destroyed (halted) or interrupted at some point in its operation, which will indicate that the application will continue as programmed 545. If the thread remains active, the process continues with the thread execution 520 and with the storing of current execution data 525.
The computer 605 further comprises a random access memory (RAM) or other dynamic storage as a main memory 625 to store information and instructions to be executed by the processor 615 through 620. The RAM or other main memory 625 also may be used for storing temporary variables or other intermediate information during execution of instructions by the processors 615 through 620.
A hard drive or other storage device 630 may be used by the computer 605 for storing information and instructions. The storage device 630 may include a magnetic disk or optical disc and its corresponding drive, flash memory or other nonvolatile memory, or other memory device. Such elements may be combined together or may be separate components. The computer 605 may include a read only memory (ROM) 635 or other static storage device for storing static information and instructions for the processors 615 through 620.
A keyboard or other input device 640 may be coupled to the bus 610 for communicating information or command selections to the processors 615 through 620. The input device 640 may include a keyboard, a keypad, a touch-screen and stylus, a voice-activated system, or other input device, or combinations of such devices. The computer may further include a mouse or other cursor control device 645, which may be a mouse, a trackball, or cursor direction keys to communicate direction information and command selections to the processors and to control cursor movement on a display device. The computer 605 may include a computer display device 650, such as a cathode ray tube (CRT), liquid crystal display (LCD), or other display technology, to display information to a user. In some environments, the display device may be a touch-screen that is also utilized as at least a part of an input device. In some environments, the computer display device 650 may be or may include an auditory device, such as a speaker for providing auditory information.
A communication device 650 may also be coupled to the bus 610. The communication device 650 may include a modem, a transceiver, a wireless modem, or other interface device. The computer 605 may be linked to a network or to other device using via an interface 655, which may include links to the Internet, a local area network, or another environment. The computer 605 may comprise a server that connects to multiple devices. In one embodiment the computer 605 comprises a Java compatible server that is connected to user devices and to external resources.
It should be appreciated that reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Therefore, it is emphasized and should be appreciated that two or more references to “an embodiment” or “one embodiment” or “an alternative embodiment” in various portions of this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures or characteristics may be combined as suitable in one or more embodiments of the invention.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure aiding in the understanding of one or more of the various inventive aspects. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5057996 | Cutler et al. | Oct 1991 | A |
| 5421014 | Bucher | May 1995 | A |
| 5613114 | Anderson et al. | Mar 1997 | A |
| 5752031 | Cutler et al. | May 1998 | A |
| 5768587 | Freund et al. | Jun 1998 | A |
| 5790789 | Suarez | Aug 1998 | A |
| 5815727 | Motomura | Sep 1998 | A |
| 5872971 | Knapman et al. | Feb 1999 | A |
| 6003061 | Jones et al. | Dec 1999 | A |
| 6026424 | Circenis | Feb 2000 | A |
| 6026428 | Hutchison et al. | Feb 2000 | A |
| 6125382 | Brobst et al. | Sep 2000 | A |
| 6233585 | Gupta et al. | May 2001 | B1 |
| 6260057 | Eykholt et al. | Jul 2001 | B1 |
| 6269391 | Gillespie | Jul 2001 | B1 |
| 6349312 | Fresko et al. | Feb 2002 | B1 |
| 6411983 | Gallop | Jun 2002 | B1 |
| 6519605 | Gilgen et al. | Feb 2003 | B1 |
| 6639687 | Neilsen | Oct 2003 | B1 |
| 6687729 | Sievert et al. | Feb 2004 | B1 |
| 6691304 | Zhang et al. | Feb 2004 | B1 |
| 6721777 | Sharma | Apr 2004 | B1 |
| 6766349 | Belkin | Jul 2004 | B1 |
| 6778990 | Garcia et al. | Aug 2004 | B2 |
| 6832238 | Sharma et al. | Dec 2004 | B1 |
| 6886041 | Messinger et al. | Apr 2005 | B2 |
| 6976061 | Sharma | Dec 2005 | B1 |
| 6990669 | Ballantyne | Jan 2006 | B1 |
| 7007075 | Coffey | Feb 2006 | B1 |
| 7036110 | Jeyaraman | Apr 2006 | B2 |
| 7036124 | Patterson | Apr 2006 | B1 |
| 7080119 | Felt et al. | Jul 2006 | B2 |
| 7089317 | Jeyaraman et al. | Aug 2006 | B2 |
| 7089584 | Sharma | Aug 2006 | B1 |
| 7100162 | Green et al. | Aug 2006 | B2 |
| 7191441 | Abbott et al. | Mar 2007 | B2 |
| 7206805 | McLaughlin, Jr. | Apr 2007 | B1 |
| 7246353 | Forin et al. | Jul 2007 | B2 |
| 7318128 | Dice | Jan 2008 | B1 |
| 7406542 | Erlingsson | Jul 2008 | B2 |
| 7444620 | Marvin | Oct 2008 | B2 |
| 7493622 | Borkan | Feb 2009 | B2 |
| 7496654 | Corbin et al. | Feb 2009 | B2 |
| 20010056457 | Kikuchi et al. | Dec 2001 | A1 |
| 20020046230 | Dieterich et al. | Apr 2002 | A1 |
| 20020107872 | Hudis et al. | Aug 2002 | A1 |
| 20020144002 | Matena et al. | Oct 2002 | A1 |
| 20030023599 | Garcia et al. | Jan 2003 | A1 |
| 20030074217 | Beisiegel et al. | Apr 2003 | A1 |
| 20030093402 | Upton et al. | May 2003 | A1 |
| 20030145074 | Penick | Jul 2003 | A1 |
| 20030182426 | Hapner et al. | Sep 2003 | A1 |
| 20030191803 | Chinnici et al. | Oct 2003 | A1 |
| 20030229888 | Spotwood et al. | Dec 2003 | A1 |
| 20030236923 | Jeyaraman et al. | Dec 2003 | A1 |
| 20040015859 | Potter et al. | Jan 2004 | A1 |
| 20040015974 | Jeyaraman | Jan 2004 | A1 |
| 20040078495 | Mousseau et al. | Apr 2004 | A1 |
| 20040098726 | Currie et al. | May 2004 | A1 |
| 20040109413 | Hierholzer et al. | Jun 2004 | A1 |
| 20040172639 | Lou et al. | Sep 2004 | A1 |
| 20040215473 | Bhogi et al. | Oct 2004 | A1 |
| 20040244004 | Pardon et al. | Dec 2004 | A1 |
| 20050060169 | Gangadharan et al. | Mar 2005 | A1 |
| 20050222689 | Smith et al. | Oct 2005 | A1 |
| 20050240663 | Wolber et al. | Oct 2005 | A1 |
| 20060041662 | Georgiev et al. | Feb 2006 | A1 |
| 20060075115 | Chitilian et al. | Apr 2006 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20050273783 A1 | Dec 2005 | US |
