I want to create some REST web services which will be called frequently by other applications (making calls at each 4-5 seconds).
During the day there can be several instances active (20-30) which will use those web services. In conclusion there will be many database calls.
What's the best solution to avoid seeing JDBC connection failure in weblogic console and to use connection pooling properly?
1. Use createRootApplicationModule and after that call release
2. Get the datasource instance and after that do whatever business (get VOs, methods etc.)
...or there is another solution?
Edited by: DorinS on 03.11.2011 12:02
If the POJO you use to expose the service stays in memory then you don't need to close the AM reference. However, what you really want to do is to use JDBC Datasources with your AM configuration so the server manages a pool of database connections the AM then reaches out to