Some of us have seen an unexplainable error message with the following messages which for me surfaces when running a suite of integration tests:
1. com.atomikos.jdbc.AtomikosSQLException: Cannot initialize AtomikosDataSourceBean
2. Caused by: javax.naming.NamingException: Another resource already exists with name oracleXADatasource - pick a different name
You can solve this problem by reducing the number of pooled connections to the database. I made it work by reducing from 15 to 5 connections.
The problem as I understood it was that the time taken to shutdown the AtomikosDataSourceBean and all the pooled connections between each integration test was longer when you have 15 connections.
When the next test starts the previous test may not have had the opportunity to unload the bean properly, thus leaving it in a dirtied state.
Hope this helps.
This topic is archived. No further replies will be accepted.Other recent topics