International Business Machines Corporation

Kyndryl, Inc.

Lohitashwa Thyagaraj

Rajesh C Lalgowdar

Sanjay Mecheri Kesavan

Venkataraghavan Lakshminarayanachar

Ian Robinson

Justin T Fries

Chethan Bhat

Nir Naaman

Nataraj Nagaratnam

Rahul Gupta

Venugopala K Vemula

Sujeet Mishra

Ruchir P Jha

Trent Gray-Donald

Lohith Ravi

Venkata Kiran Kumar Darbha

Savitha Joshi

Sonali Samantaray

Sharath C Basavanna

Douglas J Griffith

Andrew James Stanford-Clark

Richard Jay Cohen

Vijay R Kalangumvathakkal

Debasisha Padhi

Naveen G Balani

Paul Andrew Titheridge

Kavitha Suresh Kumar

Sowmya H Dayananda

Amar Devegowda

Darbha V Kumar

Urwashi Sharma

Neeraj K Gopalakrishna

Amrutha S Shenoy

A method, system, and computer program product for prioritizing endpoints to be checked during a change window based on certain criteria. The method may include receiving a request for processing from a plurality of servers. The method may also include determining a priority for each server of the plurality of servers based on specified criteria, where the specified criteria includes at least compliance-check history. The method may also include determining whether each server belongs to one or more groups. The method may also include determining a notification order for the plurality of servers based on the priority and whether each server belongs to the one or more groups. The method may also include sending a notification to each server in the notification order.

Prioritize endpoint selection based on criteria

There is provided a method for recalling a message. The method comprises receiving a message from a publisher, sending the message to a durable subscriber for queuing pending consumption by a subscriber. When a message recall request identifying the message is received, the unconsumed message is deleted from the durable subscriber.

Message recall

Release and re-acquisition of each of a first shared lock on an outer database ownership table and a second shared lock on an inner database ownership table is alternated by a messaging engine processor that executes a messaging engine to permit database maintenance operations to be performed while maintaining the ownership of the database. At least one period of inactivity of both the outer database ownership table and the inner database ownership table is provided that allows at least one database tool to execute to perform at least one database maintenance task during the execution of the messaging engine.

Management of long-running locks and transactions on database tables

A computer-implemented method includes sending one or more network packets. Each of the one or more network packets includes a network packet header. The computer implemented method further includes receiving a negative acknowledgement list comprising the network packets not received. The computer-implemented method further includes, responsive to the receiving of a negative acknowledgment list: For each network packet of the negative acknowledgment list, transforming the network packet header into a modified packet header to yield a modified packet. The computer-implemented method further includes combining each modified packet into a modified packet list. The computer-implemented method further includes generating one or more repair packets. Each of the one or more repair packets further include a repair packet header and a portion of the modified packet list. The computer-implemented method further includes sending the one or more repair packets. A corresponding computer system and computer program product are also disclosed.

Adaptive network communication protocols

Applications retrieve physical messages from one of either a co-located, passive messaging engine within the same datacenter as the application, or a nearest passive messaging engine from a different datacenter instead of from the active messaging engine. In that way, the active messaging engine does not deliver the physical message directly from its local storage.

Message retrieval in a distributed computing network

An exclusive lock is acquired on each of an outer database ownership table and an inner database ownership table to obtain ownership of a database. The exclusive locks are converted to a pair of overlapping shared locks on each of the outer database ownership table and the inner database ownership table, where release and re-acquisition of each of the pair of overlapping shared locks on the outer database ownership table and the inner database ownership table permits database maintenance operations to be performed while maintaining the ownership of the database.

A method is provided for providing unit of work continuity between a client device and a server when the client device initially fails to complete an ongoing unit of work. The method includes temporarily storing, in a temporary storage location in the server, in-doubt messages sent to the server for the ongoing unit of work, when the client device disconnects from the server without committing the ongoing unit of work so that the client device does not have to resend the in-doubt messages to the server. The method further includes utilizing unique hash-codes to identify the in-doubt messages the client device had earlier sent so that the server can retrieve the in-doubt messages from the temporary storage location and include the in-doubt messages as part of the ongoing unit of work to be committed by the client device. The ongoing unit of work is only part of an entire transaction.

Providing unit of work continuity in the event initiating client fails over

Establishment of an exclusive lock on each of an outer database ownership table and an inner database ownership table is attempted. In response to establishing the exclusive lock on each of the outer database ownership table and the inner database ownership table, a switch is made to a pair of overlapping shared locks on each of the outer database ownership table and the inner database ownership table. Release and re-acquisition of each of the pair of overlapping shared locks on the outer database ownership table and the inner database ownership table is alternated.

A method, system, and computer usable program product for improved manufacturing and distribution to avoid counterfeit products in a supply chain are provided in the illustrative embodiments. For manufacturing to avoid a counterfeit product, a product to be manufactured is selected. Production volume information is determined, the production volume information including a number of units of the product to be produced. An identifier of a manufacturer of the product, an identifier of the product, and the production volume information are sent and several sets of identifiers are received. Each set of identifiers include identifiers corresponding to a customer reference number (CRN), a customer acknowledgment number (CAN), and a merchant acknowledgment number (MAN). One set of identifiers is uniquely associated with one unit of the product being produced. A unit of the product is manufactured such that the unit includes a corresponding set of identifiers.

Manufacturing and distribution to avoid counterfeit products

A method, system, and computer usable program product for mitigating distribution or consumption of counterfeit products in a supply chain are provided in the illustrative embodiments. A first set of identifiers is generated to associate with a product to be manufactured. The first set of identifiers includes identifiers corresponding to a customer reference number (CRN), a customer acknowledgment number (CAN), and a merchant acknowledgment number (MAN). The first set of identifiers is associated with the product and a status indicator. The status indicator is set to a first value representative of the product being an original product and the product being available for sale. The first set of identifiers is transmitted to another second application.

Mitigating distribution and consumption of counterfeit products

A method, system, and computer usable program product for pre and post purchase identification of counterfeit products in a supply chain are provided in the illustrative embodiments. A customer reference number (CRN) associated with a unit of product is identified. The unit of product has associated therewith a unique set of identifiers including the CRN, a customer acknowledgment number (CAN), and a merchant acknowledgment number (MAN). The CRN is sent to a second application and a message is received from the second application in response to sending the CRN. If the message includes a second CAN that is not the same as the CAN associated with the unit, the unit is determined to be a counterfeit product.

Pre and post purchase identification of counterfeit products

According to one exemplary embodiment, a method for selectively resending a first message in a publish-subscribe message distribution model is provided. The method may include receiving the first message having a first message ID associated with the first message. The method may include sending the first message to a plurality of subscribers. The method may include receiving a rolled back first message. The method may include determining if the first message ID matches a second message ID associated with a second message. The method may include creating a first subscriber list associated with the first message. The method may include storing the first message in a data structure. The method may include appending a second subscriber list associated with the second message with a subscriber. The method may include sending the second message to the first subscriber or the first message to the first subscriber.

Growing community of inventors

Bengaluru, India

Lohitashwa Thyagaraj