Re: update WebSphere Security fails with CustomRegistry
Tuesday, October 23, 2001 02:04 PM
This is the solution, I hope that's usefull
for somebody else...
If your CustomRegistry class uses a oracle as registry, you MUST use the 2PC
driver (2-phase commit) oracle.jdbc.xa.client.OracleXADataSource as
Implementation Class of your JDBC Provider (even if you don't use a
XAConnection in your class). I found a similar problem in WebSphere
newsgroup, and solution is the same. If you'll have a problem when
restarting the server, check the following : when using distributed
transactions XA, the connected Oracle user requires SELECT privileges on the
system view: grant select on ba_pending_transactions to (User ID of your JDBC Provider).