PQ55941: UNABLE TO SAVE GLOBAL SECURITY SETTINGS WHEN USING LTPA CUSTOM REGISTRY | |||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||
APAR status Closed as Permanent restriction. Error description Unable to save global security settings when using LTPA Custom Registry implementation. Keep getting error "Illegal use of 1PC resource in transaction". My Customer Registry code is not explicitly using any transaction and shouldn't need 2PC support. The database (registry) is DB2 UDB 7.2 Enterprise and I am using WebSphere connection pool to get connections. The XA drivers in db2java.zip do not support connection pools. ------------------------------------------------ Note: As of 23 Apr 2003, Version 5 does not support a Data Source within a Custom Registry implementation.Local fix Problem summary **************************************************************** * USERS AFFECTED: All WebSphere Application Server users * * implementing a Custom User Registry and * * attempting to use a Data Source within * * it. * **************************************************************** * PROBLEM DESCRIPTION: Using a Data Source in a Custom * * Registry implementation causes a one * * phase commit error. * **************************************************************** * RECOMMENDATION: * **************************************************************** Using a Data Source in a Custom Registry implementation causes a one phase commit error. This is an implicit architectural limitation in WebSphere. When Custom Registry code is called, the configuration code is already in the middle of a database transaction. For performance reasons, WebSphere uses one phase commit drivers for repository access. One phase commit drivers only allow one active transaction at any given time and the use of a Data Source initiates a new transaction.Problem conclusion This limitation will be removed in the next release of WebSphere, if any. A database will no longer be used for a repository and therefore a transaction will not be active when Custom Registry code is called.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ55941
IBM Group: Software Group
Modified date: Apr 24, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.