New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems using XA Driver in AppServer when looking up a Connection (like JDBC-86) [JDBC131] #172
Comments
Commented by: Roman Rokytskyy (rrokytskyy) Can you describe your configuration? I.e. how did you configure the Glassfish, etc. In general it should be possible to close the connection in a finally block, and in this case connection will be returned back to the pool... |
Commented by: Torsten Strasser (strator) I deployed a connection pool with the following settings: Datasource classname: org.firebirdsql.pool.sun.AppServerXADataSource Pool-size: 8 - 64 databaseName: <//localhost:3050/C:\development\projects\stuff\xxxx.FDB> The datasource is looked up by an POJO class via JNDI which lives inside an stateles EJB (in this case I don't use dependency injection). This szenario gives the same errors like described in JDBC 86. When I remove the code for closing the connection, it runs without problems, but It doesn't matter if I use the XA driver or the usual pooling driver. The only driver which works is the org.firebirdsql.pool.sun.AppServerDataSource. When I use the resource adapter (I deployed the RAR into glassfish) and use it as a datasource with XA transactions, it also runs without |
Modified by: @mrotteveelassignee: Roman Rokytskyy [ rrokytskyy ] => Mark Rotteveel [ avalanche1979 ] |
Modified by: @mrotteveel |
Modified by: @mrotteveelFix Version: Jaybird 2.2 [ 10053 ] |
Modified by: @mrotteveel |
Modified by: @mrotteveelsummary: Problems using XY Driver in AppServer when looking up a Connection (like JDBC86) => Problems using XA Driver in AppServer when looking up a Connection (like JDBC86) |
Modified by: @mrotteveelstatus: Open [ 1 ] => In Progress [ 3 ] |
Modified by: @mrotteveelstatus: In Progress [ 3 ] => Open [ 1 ] |
Commented by: @mrotteveel Resolved by JDBC176 if you replace the current XADataSource with org.firebirdsql.ds.FBXADataSource. The implementations in org.firebirdsql.pool and org.firebirdsql.pool.sun won't be fixed and may be removed in Jaybird 2.3 or later. |
Modified by: @mrotteveelstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Torsten Strasser (strator)
Is related to JDBC86
Relate to JDBC176
When getting a connection from a XA datasource retrieved via a JNDI lookup within an ejb, exceptions like in JDBC86 occure. The solution is to
not close the connection (i. e. in a finally block) after finishing the operations. In my opinion, in a managed environment like in an
appsever where connection pooling is used, the close-operation should do nothing and it should definitly not cause an exception.
The text was updated successfully, but these errors were encountered: