My Oracle Support Banner

User Gets 'Login Password has Expired' and Fails to Login after Running Agile for a Few Hours (Doc ID 2741317.1)

Last updated on SEPTEMBER 13, 2021

Applies to:

Oracle Agile PLM Framework - Version and later
Information in this document applies to any platform.


Actual Behavior

After logged into Web Client for one hour or so, operation gets slow and user gets below message even though it has not reached the password expiry date
Login password has expired. Enter the new password
Login password:
New Login password:
Confirm New Login password

Change the password, and try to re-login to Web Client.
Web Client gets below error after giving username and password:
Unable to save change. There is one error

Once the user gets this issue, the other users face the same issue as well

Expected Behavior

User not to be prompted to reset password when the password expiry date has not reached.
User can log into Web Client with the correct username and password


See below error in stdout.log:
com.agile.util.exception.CMAppException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool ContentDataSource to allocate to applications, please increase the size of the pool and retry..

See below error in agileDomain.log:
<Error> <JTA> <{servername}.{domain}> <{servername-Agile}> <Timer-9> <> <BEA1-0528B99B14195216B06E> <086e7061-fe37-42c9-8a05-334b2c2b0ada-0000003f> <1606284857194> <[severity-value: 8] [rid: 0:25770] [partition-id: 0] [partition-name: DOMAIN] > <BEA-110412> <Xid=BEA1-0528B99B14195216B06E(1177162792),Status=Rolled back. [Reason=Unknown],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=1800,useSecure=false,activeThread=Thread[Timer-9,1,Pooled Threads],XAServerResourceInfo[ContentDataSource_agileDomain]=(ServerResourceInfo[ContentDataSource_agileDomain]=(state=rolledback,assigned={servername-Agile}),xar=weblogic.jdbc.wrapper.JTSEmulateXAResourceImpl@2a305c6f,re-Registered = false),SCInfo[agileDomain+{servername-Agile}]=(state=rolledback),properties=({weblogic.transaction.assignableOnlyToEnlistingSCs=[ContentDataSource_agileDomain], weblogic.jdbc.remote.ContentDataSource=t3://{servername}.{domain}:{port}, weblogic.transaction.partitionName=DOMAIN}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL={servername-Agile}+{servername}.{domain}:{port}+agileDomain+t3+ CoordinatorNonSecureURL={servername-Agile}+{servername}.{domain}:{port}+agileDomain+t3+ coordinatorSecureURL=null, XAResources={WSATGatewayRM_{servername-Agile}_agileDomain, tangosol.coherenceTxCCI, WLStore_agileDomain__WLS_{servername-Agile}, eis/oracle/in-memory, ContentDataSource_agileDomain, tangosol.coherenceTx},NonXAResources={})],CoordinatorURL={servername-Agile}+{servername}.{domain}:{port}+agileDomain+t3+) completed heuristically: (ContentDataSource_agileDomain, HeuristicHazard, (javax.transaction.xa.XAException: Two rollbacks failed. The first one threw No more data to read from socket)). The second one threw No more data to read from socket)).>


- Happens on Test instance only where Notification is disabled
- Happens even only one user is accessing to the system
- Account Lockout Notification Task is set to run every 2 min (default setting)
- JTA > Change Timeout Seconds is increased from default 900 to 10800 (3 hours) in WebLogic admin console
- Problem recovers after restarting Application Server, but happens again after running the system for one hour or so



The issue can be reproduced at will with the following steps:

  1. Log into Java Client as admin user, and go to Admin tab > Server Settings > Database, and make sure below is configured:
    Notification Enabled: No
  2. Go to Admin tab > Server Settings > Task Configurations, and make sure below is set for Account Lockout Notification Task
    Task Interval: 2
    Task Lookback Window: 15
    Task Disabled: No
  3. Log into WebLogic admin console, go to agileDomain > JTA, and Change Timeout Seconds from default '900' to '10800'
  4. Log into Web Client, and perform any operations. Keep logged in for one hour or so
  5. Notice the performance gets slower and slower. Eventually the user gets error: Login password has expired. Enter the new password


 JTA Timeout Seconds was increased to avoid custom PX to timeout


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.