Abstract: A method for intermediary client reconnection to a preferred server in a high availability server cluster. The method includes monitoring a persistent connection of a logical connection to a preferred server to identify an unavailability of the preferred server, establishing a temporary persistent connection for the logical connection to an available server to replace an unavailable preferred server, prompting attempts to reconnect to the preferred server at intervals, and providing a connection switching pool and simultaneously re-establishing a persistent connection with the preferred server for the logical connection using the connection switching pool while terminating the temporary persistent connection to the available server. The connection switching pool and a main connection pool used by the persistent connection allow for simultaneously maintaining two connections to different servers in a same server cluster for the logical connection.

Abstract: A method, system, computer program product and a computer program for prioritizing queued tasks waiting to access a resource associated with a resource manager in an application server, wherein an incoming task received at the application server from a calling application may have a status indicating that the incoming task is in a final phase during which a response to the calling application is created, the method comprising: receiving the incoming task; identifying the status of the incoming task; in response to identifying that the status of the incoming task is in the final phase, placing the incoming task in a priority queue; analyzing any queued tasks waiting to access the resource in the priority queue and one or more other queues; and processing a queued task from the priority queue in preference to the one or more other queues.

Abstract: Systems, methods, and computer program products for the dynamic management of the capacity of connections to a server. One method includes receiving a request to change a first connection to a server and determining active connections to the server. The method also includes determining a corresponding current capacity of each active connection and determining a new capacity for the first connection and the active connections to the server. The method further includes determining that a spare capacity of the server is insufficient for the first connection. The method also includes allocating a capacity to the first connection based on the request. The method further includes adjusting the current capacity of the active connections, including reducing the current capacity of at least a portion of the active connections in proportion to the respective current capacity of the one or more active connections.

Abstract: Systems, methods, and computer program products for the dynamic management of the capacity of connections to a server. One method includes receiving a request to change a first connection to a server and determining active connections to the server. The method also includes determining a corresponding current capacity of each active connection and determining a new capacity for the first connection and the active connections to the server. The method further includes determining that a spare capacity of the server is insufficient for the first connection. The method also includes allocating a capacity to the first connection based on the request. The method further includes adjusting the current capacity of the active connections, including reducing the current capacity of at least a portion of the active connections in proportion to the respective current capacity of the one or more active connections.

Abstract: Systems, methods, and computer program products for the dynamic management of the capacity of long-lived connections to a server are provided. A request to change a first connection to a server is received. The server has a total capacity to process multiple concurrent requests from one or more clients over respective connections, and each connection is configured with a capacity for communicating concurrent client requests. One or more active connections to the server and corresponding current capacities are determined. A new capacity for one or more connections of the first connection and the active connections to the server is determined based on the request, the total capacity and the current capacities of the one or more active connections.

Abstract: Methods, systems, and computer program products for handling multi-pipe connections is provided. A primary pipe request for a connection between a client and a server is received. The connection includes a plurality of pipes between the client and the server. The primary pipe request includes a number corresponding to the amount of pipes required for the connection. A first response acknowledging the receipt of the primary pipe request is transmitted. The first response includes a token. A plurality of subsequent pipe requests are received for the connection between the client and the server. Each subsequent pipe request includes the token. A subsequent response to each subsequent pipe request is transmitted. A count of the number of pipe requests received is maintained. The established pipes are released after a period of time has elapsed when the number of pipe requests received doesn't reach the number of pipes required for the connection.

Abstract: Methods, systems, and computer program products for handling multi-pipe connections is provided. A primary pipe request for a connection between a client and a server is received. The connection includes a plurality of pipes between the client and the server. The primary pipe request includes a number corresponding to the amount of pipes required for the connection. A first response acknowledging the receipt of the primary pipe request is transmitted. The first response includes a token. A plurality of subsequent pipe requests are received for the connection between the client and the server. Each subsequent pipe request includes the token. A subsequent response to each subsequent pipe request is transmitted. A count of the number of pipe requests received is maintained. The established pipes are released after a period of time has elapsed when the number of pipe requests received doesn't reach the number of pipes required for the connection.

Abstract: A connection request including a connection model key and a partner system attribute of a partner system requesting a connection is received at an application server from the partner system within a distributed system. Using a predefined connection model, a determination is made as to whether the received connection model key and the received partner system attribute respectively match a configured connection model key and a configured authorized partner system attribute within the predefined connection model. A logical connection is created that includes a first unique connection name derived from the received partner system attribute in response to determining that the received connection model key and the received partner system attribute match the respective configured connection model key and the configured authorized partner system attribute within the predefined connection model.

Abstract: A computer-implemented method for data communication. In one example method, a first system sends an enhanced capability exchange (CAPEX) request message to a second system. The CAPEX request message includes a request to change the number of connection pipes on an established socket-based connection between the first system and the second system. The first system receives an enhanced CAPEX response message from the second system. The CAPEX response message accepts the request to change the number of connection pipes on the established connection. The first system changes the number of connection pipes on the established connection in accordance with the accepted request.

Abstract: A transaction processing server and associated clients which send requests to the server via client-server connections. The server has a transaction processing region operable to process requests and issue responses to the requesting client. The server maintains a record of historical processing times taken to process recent client requests. The server has a connection manager that is operable to monitor incoming client requests and extract from them a goal response time, which is a maximum time within which the client expects the request to be processed which is included in each request. The server accepts or rejects each incoming client request based on deciding whether it is likely to be processed within the goal response time. If a request is rejected, the server transmits a rejection message to the originating client.

Abstract: A system for data communication. In one example method, a first system sends an enhanced capability exchange (CAPEX) request message to a second system. The CAPEX request message includes a request to change the number of connection pipes on an established socket-based connection between the first system and the second system. The first system receives an enhanced CAPEX response message from the second system. The CAPEX response message accepts the request to change the number of connection pipes on the established connection. The first system changes the number of connection pipes on the established connection in accordance with the accepted request.

Abstract: A transaction processing server and associated clients which send requests to the server via client-server connections. The server has a transaction processing region operable to process requests and issue responses to the requesting client. The server maintains a record of historical processing times taken to process recent client requests. The server has a connection manager that is operable to monitor incoming client requests and extract from them a goal response time, which is a maximum time within which the client expects the request to be processed which is included in each request. The server accepts or rejects each incoming client request based on deciding whether it is likely to be processed within the goal response time. If a request is rejected, the server transmits a rejection message to the originating client.

Abstract: A status data repository operable with a distributed processing environment including a plurality of processing regions. The status data repository includes a data storage unit adapted to store status data representative of the availability of the plurality of processing regions. The status data repository is adapted to share stored status data with a client device so as to enable the client device to obtain information regarding the availability of one or more of the plurality of processing regions.

Abstract: Systems, methods, and computer program products for the dynamic management of the capacity of long-lived connections to a server are provided. A request to change a first connection to a server is received. The server has a total capacity to process multiple concurrent requests from one or more clients over respective connections, and each connection is configured with a capacity for communicating concurrent client requests. One or more active connections to the server and corresponding current capacities are determined. A new capacity for one or more connections of the first connection and the active connections to the server is determined based on the request, the total capacity and the current capacities of the one or more active connections.

Abstract: A system, computer-implemented method and computer program performs heartbeat messaging for managing connections for data communications. In one example method, an indication of a problem associated with a connection for data communication in a computing system or network is received. In response to receiving the indication, a heartbeat message is sent over the connection. The method monitors for a heartbeat response to the heartbeat message within a predefined heartbeat time interval. If a heartbeat response is received within the predefined heartbeat time interval, the method determines that the indication of a problem associated with the connection is invalid. If a heartbeat response is not received within the predefined heartbeat time interval, the method determines that the indication of a problem associated with the connection is valid.

Abstract: Method and system are provided for overload management of a transaction processing server. The method includes detecting a high load state of a server based on a count of current transactions being processed in the server and activating prioritization of incoming client requests to the server based on prioritization of types of transaction request that reduce the load on the server. The prioritization may include: inspecting incoming client requests to determine their type and allocate a priority level; and forwarding a higher level prioritized request for processing ahead of a lower level priority request.

Abstract: Methods, systems, and computer program products for handling multi-pipe connections is provided. A primary pipe request for a connection between a client and a server is received. The connection includes a plurality of pipes between the client and the server. The primary pipe request includes a number corresponding to the amount of pipes required for the connection. A first response acknowledging the receipt of the primary pipe request is transmitted. The first response includes a token. A plurality of subsequent pipe requests are received for the connection between the client and the server. Each subsequent pipe request includes the token. A subsequent response to each subsequent pipe request is transmitted. A count of the number of pipe requests received is maintained. The established pipes are released after a period of time has elapsed when the number of pipe requests received doesn't reach the number of pipes required for the connection.

Abstract: Methods, systems, and computer program products for handling multi-pipe connections is provided. A primary pipe request for a connection between a client and a server is received. The connection includes a plurality of pipes between the client and the server. The primary pipe request includes a number corresponding to the amount of pipes required for the connection. A first response acknowledging the receipt of the primary pipe request is transmitted. The first response includes a token. A plurality of subsequent pipe requests are received for the connection between the client and the server. Each subsequent pipe request includes the token. A subsequent response to each subsequent pipe request is transmitted. A count of the number of pipe requests received is maintained. The established pipes are released after a period of time has elapsed when the number of pipe requests received doesn't reach the number of pipes required for the connection.

Abstract: Methods, systems, and computer program products for handling multi-pipe connections is provided. A primary pipe request for a connection between a client and a server is received. The connection includes a plurality of pipes between the client and the server. The primary pipe request includes a number corresponding to the amount of pipes required for the connection. A first response acknowledging the receipt of the primary pipe request is transmitted. The first response includes a token. A plurality of subsequent pipe requests are received for the connection between the client and the server. Each subsequent pipe request includes the token. A subsequent response to each subsequent pipe request is transmitted. A count of the number of pipe requests received is maintained. The established pipes are released after a period of time has elapsed when the number of pipe requests received doesn't reach the number of pipes required for the connection.

Abstract: Methods, systems, and computer program products for handling multi-pipe connections is provided. A primary pipe request for a connection between a client and a server is received. The connection includes a plurality of pipes between the client and the server. The primary pipe request includes a number corresponding to the amount of pipes required for the connection. A first response acknowledging the receipt of the primary pipe request is transmitted. The first response includes a token. A plurality of subsequent pipe requests are received for the connection between the client and the server. Each subsequent pipe request includes the token. A subsequent response to each subsequent pipe request is transmitted. A count of the number of pipe requests received is maintained. The established pipes are released after a period of time has elapsed when the number of pipe requests received doesn't reach the number of pipes required for the connection.