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: 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: Reconnection of a client to a server in a transaction processing server cluster having a single address. A connection is established with a first server in the server cluster and units of work are requested at the first server. A failure of the connection to the first server is detected. A connection is established with a second server in the server cluster and units of work at the second server are requested. A reconnection request is received from the first server, in which the first server has unresolved units of work. The connection with the second server is terminated, including completing current units of work. The client is reconnected with the first server and the unresolved units of work with the first server are resynchronized.

Abstract: A connection request including a connection model key and a partner system attribute of the partner system requesting a connection is received at an application server from a partner system. Using a predefined connection model, as 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. 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, a connection is created that includes a first unique connection name derived from the received partner system attribute.

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 method, system, and/or computer program product manages a network connection for use by a plurality of application program processes. A set of application program processes, which utilize a network connection, are categorized into a plurality of categories. An optimum network connection parameter value is identified for each category of application program processes. A network connection is established for use by the set of application program processes. A usage of the network connection is determined by each of the application program processes. A network connection parameter is set for the network connection dependent on a respective usage and optimum network connection parameters of the application program processes.

Abstract: A computer-implemented method of establishing metadata associated with a transaction in a transaction processing system having application logic for executing the transaction, the computer-implemented method includes receiving, from a requestor, request data associated with the transaction, the request data comprising data and metadata. The method also includes peeking, during receiving the request data, of the request data looking for the metadata associated with the transaction and responsive to finding metadata associated with the transaction, directly instantiating an instance of application logic.

Abstract: A connection request including a connection model key and a partner system attribute of the partner system requesting a connection is received at an application server from a partner system. Using a predefined connection model, as 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. 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, a connection is created that includes a first unique connection name derived from the received partner system attribute.

Abstract: A method, computer program product, and system for resolving a potential in-doubt condition of a distributed transaction, is provided. A processor receives a request to commit a transaction for a distributed transaction protocol that includes an applied process, the transaction includes a transfer of a commit decision from a coordinating node to a participating node. The processor checks the service status of the connection to the participating node, and finding the service status of the connection out of service or unavailable, the processor instructs the coordinating node to back-out (rollback) the transaction. Additionally, locality meta-data is used as an indication of reliability of the connection to the participating node, and in response to determining the participating node locality to be a remote network connection, the processor instructs the coordinating node to abort the applied process and send a standard distributed transaction protocol message over unreliable connections.

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: A method for resolving a potential in-doubt condition of a distributed transaction, is provided. A processor receives a request to commit a transaction for a distributed transaction protocol that includes an applied process, the transaction includes a transfer of a commit decision from a coordinating node to a participating node. The processor checks the service status of the connection to the participating node, and finding the service status of the connection out of service or unavailable, the processor instructs the coordinating node to back-out (rollback) the transaction. Additionally, locality meta-data is used as an indication of reliability of the connection to the participating node, and in response to determining the participating node locality to be a remote network connection, the processor instructs the coordinating node to abort the applied process and send a standard distributed transaction protocol message over unreliable connections.

Abstract: Reconnection of a client to a server in a transaction processing server cluster having a single address. A connection is established with a first server in the server cluster and units of work are requested at the first server. A failure of the connection to the first server is detected. A connection is established with a second server in the server cluster and units of work at the second server are requested. A reconnection request is received from the first server, in which the first server has unresolved units of work. The connection with the second server is terminated, including completing current units of work. The client is reconnected with the first server and the unresolved units of work with the first server are resynchronized.

Abstract: A connection request including a connection model key and a partner system attribute of the partner system requesting a connection is received at an application server from a partner system. Using a predefined connection model, as 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. 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, a connection is created that includes a first unique connection name derived from the received partner system attribute.

Abstract: In an approach for connecting an access point in a client region to an access point within a cluster of server regions for a transaction process, a processor receives a connect request to a cluster of server regions sharing a network end point from a client region. A processor reroutes the connect request by a connection balancing mechanism to a network end point corresponding to a server region within the cluster of server regions. A processor transmits connection information to the client region, wherein the connection information allows the client region to connect to the server region within the cluster of server regions. A processor connects the server region within the cluster of server regions to the client region.

Abstract: In an approach for connecting an access point in a client region to an access point within a cluster of server regions for a transaction process, a processor receives a connect request to a cluster of server regions sharing a network end point from a client region. A processor reroutes the connect request by a connection balancing mechanism to a network end point corresponding to a server region within the cluster of server regions. A processor transmits connection information to the client region, wherein the connection information allows the client region to connect to the server region within the cluster of server regions. A processor connects the server region within the cluster of server regions to the client region.

Abstract: A method, system, and/or computer program product manages a network connection for use by a plurality of application program processes. A set of application program processes, which utilize a network connection, are categorized into a plurality of categories. An optimum network connection parameter value is identified for each category of application program processes. A network connection is established for use by the set of application program processes. A usage of the network connection is determined by each of the application program processes. A network connection parameter is set for the network connection dependent on a respective usage and optimum network connection parameters of the application program processes.