diff b/w the connection pool and XA data source

connection Pool :

The reason for using connection pool is ...Opening and maintaining a database connection for each user, especially requests made to a dynamic database-driven website application, is costly and wastes resources.

So to avoid this the connection pool uses a cache of database connections maintained so that the connections can be reused when future requests to the database are required.




XA : its basically when you have to use a two-phase commit , An XA transaction, in the most general terms, is a "global transaction" that may span multiple resources.

So this would mean for eg if there are two DB which needs to be commited at the same time .. so in this case you would use an XA drivers