So you have a Transaction or Connection Pool Problem?

Most of the information here will address how to pursue these issues via a Support Ticket. However, general awareness of these steps can aid greatly in self support.

Review the datasource definitions and verify they follow some established guidelines per the Example Datasource configurations.

Understand some key settings involved in defining a datasource and leverage the CachedConnectionManager or Leak Dumper to identify connection leaks. Make sure connections are validated. Know what JTA means when defining a datasource (and when its safe to be false). Understand how timeouts come into play.

When working with GSS (Red Hat Support) always provide the relevant standalone or domain.xml (identifying the profile if needed). It is also very important to capture TRACE level logging to provide as much context as possible. Note that this can be adjusted on the fly for concerns where verbose logging may affect production. In almost all cases, TRACE level logging and configuration files are needed to understand the issue. Since these are possibly large files you will need to know how to get them to us.