Skip to content

XAware Community

Get the Flash Player to see this player.
Flash Image Rotator Module by Joomlashack.
XAware 5.6
Need Help
Webinars and Events
Advanced Tutorials
Webinars and Events

You are here: Home arrow Forums
XAware Community Forums
Welcome, Guest
Please Login or Register.    Lost Password?
Re:jdbc connection and connection pooling (1 viewing) (1) Guest
Go to bottom Post Reply Favoured: 1
TOPIC: Re:jdbc connection and connection pooling
#5991
prichards (Admin)
Admin
Posts: 319
User Offline Click here to see the profile of this user
Re:jdbc connection and connection pooling 9 Years, 10 Months ago Karma: 18  
The XAware managed connection (JDBC connection) automatically implements pooling of BizDrivers. The pooling can be managed through the xa:poolingparams (see the Designer Help documentation), but I do not see a way to turn pooling "off". Pooling parameters are configured according to the Apache DBCP model, refer to the documentation at http://commons.apache.org/dbcp/configuration.html . There is some additional info and an example at the following post
Re:com.ibm.db2.jcc.DB2Driver & pooling parms.

In my XAware 5 testing, I was able to make multiple connections with different users, however XAware pools the BizDrivers by name including the BizDriver/user/type (but not the password) - you can see the entries in the pool on the JBoss JMX console. Since the password is not included in the pooled entry, an attempt to connect with the same driver will grab the matching driver from the pool for the last attempt. If a valid connection exists, it will connect (even if the password supplied is different) using the current active connection; which seems to be opposite of the problem you are having. But, it will also fail with the same pooled driver info, if the first attempt had a bad password (even though you supply a good password in the next attempt), which may be the issue you are having.

Typically, our customers are using "static" connection information in XAware managed connections - although it can be parameterized to configure for different environments, and so forth - so that a BizDriver represents a connection to that datasource for a given user/password. (Much like setting up JBoss datasource for a connection.) Security is then usually managed at the BizDoc/BizComp level, through the user/roles authorization, rather than at the database level. This allows better sharing of pooled connections, rather than always creating a new connection for each user.

Currently, I don't see a way to disable the pooling (Engineering will have to review) or "force" a new connection each time. It might be possible to call the same admin BizDoc that clears the pool, but that would have to be called at the application level each time you are done with a driver/request. I was able to manually test this by clearing the pool on the console after each request, and seeing each new request succeed or fail (invalid user/password).
 
Report to moderator   Logged Logged  
  The administrator has disabled public write access.
      Topics Author Date
    thread link
jdbc connection and connection pooling
kilyas 2010/06/15 11:14
    thread link
thread linkthread link Re:jdbc connection and connection pooling
kilyas 2010/06/15 11:27
    thread link
thread linkthread link Re:jdbc connection and connection pooling
prichards 2010/07/07 11:30
Go to top Post Reply
Powered by FireBoardget the latest posts directly to your desktop

Community Login

Get the Flash Player to see this player.
Flash Image Rotator Module by Joomlashack.
Commercial
Free Training
QuickStart Packages
Image 4 Title
Image 5 Title

Visit XAware.com