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 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: A method for monitoring connections for communicating data is provided. The method includes monitoring communication of data from a device over a connection. A current connection performance parameter for the connection is determined based on the monitoring. The current connection performance parameter is compared with a predetermined threshold. If the current connection performance parameter is less than or equal to the predetermined threshold, the connection is determined to be degraded. An alert may be provided to a user if the connection is determined to be degraded and an alert condition is met.

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: In a network capable of handling a number of concurrent network connections between network nodes, referred to as client and server, the client and server connection managers are customized by adding respective status handler components which add server status information requests, from client to server, and responsive status information, from server to client into message headers of messages being sent between the server and client. The supported server status information types for any given connection are defined when a connection is established through dialogue between the client and server, and then persist for the lifetime of the connection. The customizations of the server and client connection managers are modest and the increase in network traffic over the connection is proportionally very small. Moreover, status information requests can be processed and responded to quickly by attaching to messages that are being sent between the nodes.

Abstract: Aspects include balancing work of tasks at a sending node of a transaction server in a network. A method can include processing a task from the top of a work queue at the sending node, where the task is an instance of a transaction which requires a transaction message to be sent from the sending node using a network connection. The transaction message is divided into chunks of partial transaction sub-messages. For each chunk, it can be dynamically determined whether a pacing response indicator is required based on metrics that monitor the activity in the work queue and a number of chunks of the transaction message already sent.

Abstract: Aspects include balancing work of tasks at a sending node of a transaction server in a network. A method can include processing a task from the top of a work queue at the sending node, where the task is an instance of a transaction which requires a transaction message to be sent from the sending node using a network connection. The transaction message is divided into chunks of partial transaction sub-messages. For each chunk, it can be dynamically determined whether a pacing response indicator is required based on metrics that monitor the activity in the work queue and a number of chunks of the transaction message already sent.

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 system, computer-implemented method and computer program manages connections 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 system, computer-implemented method and computer program manages connections 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 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: 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: A method for monitoring connections for communicating data is provided. The method includes monitoring communication of data from a device over a connection. A current connection performance parameter for the connection is determined based on the monitoring. The current connection performance parameter is compared with a predetermined threshold. If the current connection performance parameter is less than or equal to the predetermined threshold, the connection is determined to be degraded. An alert may be provided to a user if the connection is determined to be degraded and an alert condition is met.

Abstract: A method for monitoring connections for communicating data is provided. The method includes monitoring communication of data from a device over a connection. A current connection performance parameter for the connection is determined based on the monitoring. The current connection performance parameter is compared with a predetermined threshold. If the current connection performance parameter is less than or equal to the predetermined threshold, the connection is determined to be degraded. An alert may be provided to a user if the connection is determined to be degraded and an alert condition is met.

Abstract: Aspects include balancing work of tasks at a sending node of a transaction server in a network. A method can include processing a task from the top of a work queue at the sending node, where the task is an instance of a transaction which requires a transaction message to be sent from the sending node using a network connection. The transaction message is divided into chunks of partial transaction sub-messages. For each chunk, it can be dynamically determined whether a pacing response indicator is required based on metrics that monitor the activity in the work queue and a number of chunks of the transaction message already sent.

Abstract: Aspects include balancing work of tasks at a sending node of a transaction server in a network. A method can include processing a task from the top of a work queue at the sending node, where the task is an instance of a transaction which requires a transaction message to be sent from the sending node using a network connection. The transaction message is divided into chunks of partial transaction sub-messages. For each chunk, it can be dynamically determined whether a pacing response indicator is required based on metrics that monitor the activity in the work queue and a number of chunks of the transaction message already sent.

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.