| Doc ID |
|
SOLN386928 |
| Version: |
|
1.0 |
| Status: |
|
Published |
| Published date: |
|
27 Aug 2026 |
Details
Session Manager upgraded from 10.2.1.1/2 to 10.2.1.3/4 fails all the time
Problem Clarification
Upgrade finished successfully.
But Replication does not work. Stuck several Minutes with Repairing, then switch to Not Polling
Cause
This is a timing issue he HttpProxyMonitor thread touches the DMFactory before DDLBootstrap has finished initializing it
In the mgmt.log you will see the mgmt service keeps restarting with following errors:
<14>Jul 3 07:28:58 asm4-sea.cerium.network Mgmt[1314453]: -07:00 2026 103 1 com.avaya.asm | 0 com.avaya.asm.datamgr.dao.jdbc.DaoConnectionPool jdbc:postgresql://localhost/asmlocal?sslmode=verify-ca&sslfactory=org.postgresql.ssl.DefaultJavaSSLFactory connection pool initialized. Pool size is 3
<12>Jul 3 07:29:00 asm4-sea.cerium.network Mgmt[1314453]: -07:00 2026 108 1 com.avaya.asm | 0 com.avaya.asm.datamgr.ReadWriteLockHandler Thread 135 waited over 2 seconds to acquire READ LOCK for DMFactory dmMapLock: RLocks=0:
We are (priority 5):java.lang.Thread.getStackTrace(Thread.java:1564)
com.avaya.asm.datamgr.ReadWriteLockHandler.acquireReadLock(ReadWriteLockHandler.java:76)
com.avaya.asm.datamgr.DMFactory.getDataMgr(DMFactory.java:919)
com.avaya.asm.datamgr.DMFactory.getDataMgr(DMFactory.java:845)
com.avaya.asm.core.LocalSettings.getDBValue(LocalSettings.java:279)
...
java.lang.Thread.run(Thread.java:750)
org.jboss.threads.JBossThread.run(JBossThread.java:513)
Potential Lock Owner (priority 5):com.avaya.asm.datamgr.DMFactory.getLocalDataSource(DMFactory.java:318)
com.avaya.asm.datamgr.DMFactory.getDataMgr(DMFactory.java:1036)
com.avaya.asm.datamgr.LoadRulesHandler.updateLoadRules(LoadRulesHandler.java:247)
com.avaya.asm.datamgr.LoadRulesHandler.setDefaultLoadRules(LoadRulesHandler.java:204)
com.avaya.asm.datamgr.DMFactory.createDM(DMFactory.java:1101)
com.avaya.asm.datamgr.DMFactory.getDataMgr(DMFactory.java:944)
com.avaya.asm.datamgr.DMFactory.getDataMgr(DMFactory.java:845)
com.avaya.asm.trustmgmt.HttpProxyMonitor.getHttpProxyDAO(HttpProxyMonitor.java:912)
com.avaya.asm.trustmgmt.HttpProxyMonitor.access$800(HttpProxyMonitor.java:41)
com.avaya.asm.trustmgmt.HttpProxyMonitor$MonitorHttpProxyAccessibility.run(HttpProxyMonitor.java:978)
Solution
Please raise a SR to get BBE support
Fixed in 10.2.1.5 with Jira ASM-95687
