Migrating data access applications to Liberty

For data access applications, you need to change configurations when you migrate a data source from the WebSphere® Application Server traditional to Liberty.

Connection Manager behavioral differences between traditional WebSphere Application Server traditional and Liberty
  • Applications that run on WebSphere Application Server traditional or Liberty and acquire shared or unshared connections from a data source and follow the get/use/close connection pattern behave the same on both profiles. It is recommended that all applications follow the programing model of get/use/close connections.
  • However, if an application does not close connections, shared connections behave the same on both profiles. But, unlike WebSphere Application Server traditional, unshared connections that remain open on Liberty are not automatically closed and can lead to performance issues or connection wait timeouts from the connection manager.
  • If performance issues or connection wait timeouts occur after you migrate from WebSphere Application Server traditional to Liberty, check whether the application is using unshared connections and not closing them. If so, changing the application to close the connection is required to resolve these issues.