Sap Ag

Sap Se

Ivo Simeonov

Svetoslav H Manolov

Krasimir I Topchiyski

A method is described that comprises executing a non distributed transaction by reading persistent data from a database and performing executions with the persistent data. A prepare command is sent to the database after a change to be made to the persistent data as a consequence of the non distributed transaction's execution is confirmed. A commit command is sent to the database to cause the database to commit the change to the database.

Two phase commit emulation for non distributed transactions

A system method is provided to inspect memory leaks and analyze contents of garbage collection files. In one embodiment, a garbage collection file is selected from a plurality of garbage collection files at a file system. The garbage collection file includes histograms. Each histogram is compared with other histograms in the garbage collection file to identify objects associated with memory leaks The results of such comparison are provided.

Method and system for inspecting memory leaks and analyzing contents of garbage collection files

A system and method is provided to inspect memory leaks and analyze contents of garbage collection files. In one embodiment, a garbage collection file is selected from a plurality of garbage collection files at a file system. The garbage collection file includes histograms. Each histogram is compared with other histograms in the garbage collection file to identify objects associated with memory leaks The results of such comparison are provided.

A system and method for mapping Container Managed Persistence (CMP) persistent object states to Java Data Object (JDO) states. In an embodiment, mapping logic identifies a state of a CMP persistent object. The identified CMP persistent object state is mapped to a JDO state. In an embodiment, the mapping is based, at least in part, on whether the CMP persistent object is associated with a transactional context.

System and method for mapping container managed persistence persistent object states to java data object states

A method is described for managing an application's cached persistent data with different isolation levels. The different isolation levels include: 1) requesting a lock for a first item of database data in response to the first item of database data not being cached and not yet having been used by the application; 2) requesting a lock for a second item of cached database data in response to the second item of database data being updated for a first time by the application; and, 3) requesting a lock for a third item of cached database data in response to it being confirmed that the third item of database data will need to be updated in its database.

Persistent data management with different isolation levels

A method is described in which, during execution of a distributed transaction, a representation of persistent data stored at an entry in a database is placed into a cache. Then, in response to an application's decision that the entry should be removed from the database, the representation is kept in the cache and marked as corresponding to an entry that is to be removed from the database. Then, during execution of the distributed transaction's two-phase commit protocol, the database is informed that the entry is to be removed from the database if the representation was marked as corresponding to an entry that is to be removed from the database when the application completed its execution for the distributed transaction.

Growing community of inventors

Sofia, Bulgaria

Ivo Simeonov