Abstract: The subject matter described herein relates to protecting in-flight transaction requests, where a client device is connected via at least two application servers to a backend server device that is capable of processing redundant transaction requests originated by the client device. A first instance of a transaction request identified by a transaction identifier is received at the backend server device. The first instance of the transaction request is processed and a transaction response is sent to the client device. The transaction response identified by the transaction identifier is saved in a cache. If a subsequent instance of the transaction request is received, the cached transaction response is sent to the client device.

Abstract: A method for aiding resolution of a transaction for use with a transactional processing system comprising a transaction coordinator and a plurality of grouped and inter-connected resource managers, the method comprising the steps of: in response to a communications failure between the transaction coordinator and a first resource manager causing a transaction to have an in-doubt state, connecting, by the transaction coordinator, to a second resource manager; in response to the connecting step, sending by the transaction coordinator to the second resource manager, a resolve request comprising a resolution for the in-doubt transaction; in response to the resolve request, obtaining at the first resource manager, by the second resource manager, a lock to data associated with the in-doubt transaction; and in response to the obtaining step, determining, by the second resource manager, whether the transaction is associated with the first resource manager.

Abstract: A method for optimizing the number of pre-emptive service requests in an application based on identifying a plurality of pre-emptive execution eligible service requests. The method includes identifying one or more locations, associated with one or more service requests, respectively, in an application. Analyzing the one or more service requests based on the one or more locations. Determining if the one or more service requests are eligible for pre-emptive execution based on the analyzing, and responsive to determining the one or more service requests are eligible, outputting, by the one or more processors, one or more identities of the one or more service requests, respectively, for pre-emptive execution.

Abstract: Computer-implemented methods are provided for preparing an application for execution within an application execution environment and for running an application within an application execution environment. The computer-implemented methods create supplementary information for the application. The supplementary information includes an indication of a service request which is to be performed during execution of the application to obtain information from an application service. The computer-implemented methods retrieve the supplementary information for the application, and execute the application within the application execution environment. The methods perform the service request from the application execution environment independently from the execution of the application based on the supplementary information, and receive a response to the service request from the application service at the application execution environment.

Abstract: The subject matter described herein relates to protecting in-flight transaction requests, where a client device is connected via at least two application servers to a backend server device that is capable of processing redundant transaction requests originated by the client device. A first instance of a transaction request identified by a transaction identifier is received at the backend server device. The first instance of the transaction request is processed and a transaction response is sent to the client device. The transaction response identified by the transaction identifier is saved in a cache. If a subsequent instance of the transaction request is received, the cached transaction response is sent to the client device.

Abstract: The subject matter described herein relates to protecting in-flight transaction requests, where a client device is connected via at least two application servers to a backend server device that is capable of processing redundant transaction requests originated by the client device. A first instance of a transaction request identified by a transaction identifier is received at the backend server device. The first instance of the transaction request is processed and a transaction response is sent to the client device. The transaction response identified by the transaction identifier is saved in a cache. If a subsequent instance of the transaction request is received, the cached transaction response is sent to the client device.

Abstract: In response to receipt of a request message from a requester, a reply message is created. The reply message includes a message identifier of the request message copied from the received request message. The reply message is published to each of a group of replicated message queues. The reply message is identifiable by the requester using the copied message identifier of the request message on any one of the group of replicated message queues prior to being consumed by the requester.

Abstract: The subject matter described herein relates to protecting in-flight transaction requests, where a client device is connected via at least two application servers to a backend server device that is capable of processing redundant transaction requests originated by the client device. A first instance of a transaction request identified by a transaction identifier is received at the backend server device. The first instance of the transaction request is processed and a transaction response is sent to the client device. The transaction response identified by the transaction identifier is saved in a cache. If a subsequent instance of the transaction request is received, the cached transaction response is sent to the client device.

Abstract: Computer-implemented methods are provided for preparing an application for execution within an application execution environment and for running an application within an application execution environment. The computer-implemented methods create supplementary information for the application. The supplementary information includes an indication of a service request which is to be performed during execution of the application to obtain information from an application service. The computer-implemented methods retrieve the supplementary information for the application, and execute the application within the application execution environment. The methods perform the service request from the application execution environment independently from the execution of the application based on the supplementary information, and receive a response to the service request from the application service at the application execution environment.

Abstract: Computer-implemented methods are provided for preparing an application for execution within an application execution environment and for running an application within an application execution environment. The computer-implemented methods create supplementary information for the application. The supplementary information includes an indication of a service request which is to be performed during execution of the application to obtain information from an application service. The computer-implemented methods retrieve the supplementary information for the application, and execute the application within the application execution environment. The methods perform the service request from the application execution environment independently from the execution of the application based on the supplementary information, and receive a response to the service request from the application service at the application execution environment.

Abstract: An application is executed within an application execution environment. One or more service requests made by the executing application are monitored, and a service requesting profile is created for the application. The service requesting profile defines one or more service requests made by the application. The created service requesting profile for the application is accessed. The service request(s) defined within the accessed service requesting profile are performed independently of the execution of the application. One or more responses are received from the service request(s), and the response(s) from the service request(s) are provided to the application in response to a request from the application to perform the service request.

Abstract: A method for optimizing the number of pre-emptive service requests in an application based on identifying a plurality of pre-emptive execution eligible service requests. The method includes identifying one or more locations, associated with one or more service requests, respectively, in an application. Analyzing the one or more service requests based on the one or more locations. Determining if the one or more service requests are eligible for pre-emptive execution based on the analyzing, and responsive to determining the one or more service requests are eligible, outputting, by the one or more processors, one or more identities of the one or more service requests, respectively, for pre-emptive execution.

Abstract: A method for optimizing the number of pre-emptive service requests in an application based on identifying a plurality of pre-emptive execution eligible service requests. The method includes identifying one or more locations, associated with one or more service requests, respectively, in an application. Analyzing the one or more service requests based on the one or more locations. Determining if the one or more service requests are eligible for pre-emptive execution based on the analyzing, and responsive to determining the one or more service requests are eligible, outputting, by the one or more processors, one or more identities of the one or more service requests, respectively, for pre-emptive execution.

Abstract: A method for optimizing the number of pre-emptive service requests in an application based on identifying a plurality of pre-emptive execution eligible service requests. The method includes identifying one or more locations, associated with one or more service requests, respectively, in an application. Analyzing the one or more service requests based on the one or more locations. Determining if the one or more service requests are eligible for pre-emptive execution based on the analyzing, and responsive to determining the one or more service requests are eligible, outputting, by the one or more processors, one or more identities of the one or more service requests, respectively, for pre-emptive execution.

Abstract: In an approach for adapting traffic signal timing, a computer collects sensor data associated with a first intersection. The computer evaluates the collected sensor data with respect to predefined objectives. The computer determines whether a change in a state of a traffic signal for the first intersection should occur based at least in part on the evaluated collected sensor data with respect to predefined objectives. Responsive to determining the change in the state of the traffic signal for the first intersection should occur, the computer calculates a change to a traffic signal timing. The computer initiates an adaptation to the traffic signal timing based on the calculated change to the traffic signal timing.

Abstract: An application is executed within an application execution environment. One or more service requests made by the executing application are monitored, and a service requesting profile is created for the application. The service requesting profile defines one or more service requests made by the application. The created service requesting profile for the application is accessed. The service request(s) defined within the accessed service requesting profile are performed independently of the execution of the application. One or more responses are received from the service request(s), and the response(s) from the service request(s) are provided to the application in response to a request from the application to perform the service request.

Abstract: In an approach for adapting traffic signal timing, a computer receives a streaming video for one or more paths of a first intersection. The computer identifies traffic within the received streaming video. The computer calculates traffic flow for the one or more paths of the first intersection based on the identified traffic. The computer determines whether a change in a state of a traffic signal for the first intersection should occur based at least in part on the identified traffic and the determined traffic flow with respect to predefined objectives. Responsive to determining the change in the state of the traffic signal for the first intersection should occur, the computer calculates a change to a traffic signal timing based on the determined change in the state of the traffic signal. The computer initiates an adaptation to the traffic signal timing based on the determined change to the traffic signal timing.

Abstract: Computer-implemented methods are provided for preparing an application for execution within an application execution environment and for running an application within an application execution environment. The computer-implemented methods create supplementary information for the application. The supplementary information includes an indication of a service request which is to be performed during execution of the application to obtain information from an application service. The computer-implemented methods retrieve the supplementary information for the application, and execute the application within the application execution environment. The methods perform the service request from the application execution environment independently from the execution of the application based on the supplementary information, and receive a response to the service request from the application service at the application execution environment.

Abstract: In response to receipt of a request message from a requester, a reply message is created. The reply message includes a message identifier of the request message copied from the received request message. The reply message is published to each of a group of replicated message queues. The reply message is identifiable by the requester using the copied message identifier of the request message on any one of the group of replicated message queues prior to being consumed by the requester.

Abstract: In response to receipt of a request message from a requester, a reply message is created. The reply message includes a message identifier of the request message copied from the received request message. The reply message is published to each of a group of replicated message queues. The reply message is identifiable by the requester using the copied message identifier of the request message on any one of the group of replicated message queues prior to being consumed by the requester.