Oracle International Corporation

Qingsheng Zhang

Todd Jeffery Little

Xugang Shen

Yongshun Jin

Jim Yongshun Jin

Sheng Zhu

Shi Zhou

Jared Li

Weiguo Zhu

Shun Li

Pierce Shi

Jim Jin

In accordance with an embodiment, described herein is a system and method for implementing a distributed ledger a blockchain cloud service. The blockchain cloud service can include nodes of the distributed ledger and a management console component. The management console component can include a web application running in a script runtime environment, a plurality of backend of APIs for communicating with various nodes of the blockchain cloud service, and a plurality of client APIs configured to be invoked by a client application. The plurality of client APIs uses one or more of the plurality of backend APIs in provisioning the distributed ledger as a blockchain cloud service, and in managing the managing the blockchain cloud service.

System and method for providing an interface for a blockchain cloud service

In accordance with an embodiment, described herein is a system and method for making requests to a specific server in a transactional processing environment with a multiple servers, single queue (MSSQ) configuration. Each server in a MSSQ set can be associated with a secondary request queue, and can include a main thread, a secondary thread, and an internal memory queue. Each server can use an application programming interface (API) to advertise one or more non-unanimous services on a secondary request queue associated with that server. The secondary thread of a particular server is configured to dequeue, from the secondary request queue associated with the particular server, a request message for a non-unanimous service, and stores the dequeued message in the internal memory queue. The main thread of the particular server checks the internal memory queue before checking the main request queue for messages to process.

System and method for providing MSSQ notifications in a transactional processing environment

A system and method can support a tightly-coupled global transaction. One or more transaction servers operate to span the global transaction with a plurality of branches across a plurality of transaction domains, wherein each said branch is associated with an individual branch qualifier, and each said transaction domain is associated with a different global transaction identifier (GTRID). Furthermore, the transaction servers can configure the plurality of branches in the global transaction to share a common global transaction identifier (ID), and associate a composite branch qualifier with at least one branch of the global transaction in a transaction domain, wherein the composite branch qualifier includes a global transaction identifier (GTRID) that is associated with the transaction domain and an individual branch qualifier that is associated with the at least one branch.

System and method for sharing global transaction identifier (GTRID) in a transactional middleware environment

A system and method can support application interoperation in a transactional middleware environment. A first transaction server operates to initiate a global transaction, wherein the first transaction server that is associated with a first format identifier (ID), and wherein the global transaction includes a plurality of branches and each said branch is associated with an individual branch qualifier. Furthermore, the first transaction server can direct at least one branch of the global transaction from the first transaction server to a second transactional server, wherein each said transactional server is associated with a second format identifier (ID), and configure a plurality of branches in the global transaction to share a common format identifier (ID).

System and method for supporting application interoperation in a transactional middleware environment

A system and method can provide high throughput transactions in a transactional system. A system and method can, via a transaction manager, obtain information on a plurality of resource managers. The transaction manager can further manage a plurality of transaction branches, where each of the plurality of transaction branches can be associated with a different one of the plurality of resource managers. The methods and systems can associate a transaction identifier with each of the plurality of transaction branches, which can result in a plurality of transaction identifiers, where each of the plurality of transaction identifiers can include a branch identifier for each of the plurality of transaction branches. The methods and systems can perform one or more transactional operations on the plurality of transaction branches based on the different transaction identifiers.

System and method for providing single group multiple branches based on instance awareness

A system and method can support transaction processing in a transactional environment. A transactional system operates to route a request to a transactional server, wherein the transactional server is connected to a resource manager (RM) instance. Furthermore, the transactional system can assign an affinity context to the transactional server, wherein the affinity context indicates the RM instance that the transactional server is associated with, and the transactional system can route one or more subsequent requests that are related to the request to the transactional server based on the affinity context.

System and method for supporting transaction affinity based on resource manager (RM) instance awareness in a transactional environment

A system and method can support an adaptive self-tuning locking mechanism in a transactional middleware machine environment. The system allows each process in a plurality of processes to perform one or more test-and-set (TAS) operations in order to obtain a lock for data in a shared memory. Then, the system can obtain a spin failed rate for a current tuning period, wherein a spin failure happens when a process fails to obtain the lock after performing a maximum number of rounds of TAS operations that are allowed. Furthermore, the system can adaptively configuring a spin count for a next tuning period based on the obtained spin failure rate, wherein the spin count specifies the maximum number of rounds of TAS operations that are allowed for the next tuning period.

System and method for supporting an adaptive self-tuning locking mechanism in a transactional middleware machine environment

A system and method can support transaction processing in a transactional environment. A transactional server operates to receive resource manager (RM) instance information from a data source that is associated with one or more RM instances, wherein the received instance information allows the transactional server to be aware of which RM instance that the transactional server is currently connected to. Furthermore, the transactional server operates to save the received instance information into one or more tables that are associated with the transactional server. Then, the transactional server can process a global transaction based on the instance information saved in the one or more tables.

System and method for supporting resource manager (RM) instance awareness in a transactional environment

A system and method can support transaction processing in a transactional environment. A coordinator for a global transaction operates to propagate a common transaction identifier and information for a resource manager instance to one or more participants of the global transaction in the transactional environment. The coordinator allows said one or more participants, which share resource manager instance with the coordinator, to use the common transaction identifier, and can process the global transaction for said one or more participants that share the resource manager instance using one transaction branch.

System and method for supporting common transaction identifier (XID) optimization based on resource manager (RM) instance awareness in a transactional environment

A system and method can support processing a transaction with a plurality of transaction branches. A transaction manager operates to send, to a resource manager, a prepare request for each said transaction branch in the plurality of transaction branches with the exception of at least one transaction branch. Furthermore, after receiving an indication from the resource manager that the received preparation requests are handled successfully (i.e. the transaction branch is read-only and has been committed), the transaction manager operates to send a commit request to commit said at least one transaction branch, which is on hold, to the resource manager.

Growing community of inventors

Beijing, China

Qingsheng Zhang