65529 - Deadlock or race conditions occur in the OMRHistoryDAO.java log file when you run many data-loader Java programs in the SAS® Model Risk Management UI

Problem Note 65529: Deadlock or race conditions occur in the OMRHistoryDAO.java log file when you run many data-loader Java programs in the SAS® Model Risk Management UI

Code within the OMRHistoryDAO.java file can deadlock when both of the following circumstances are true:

You have a current SAS Model Risk Management UI implementation.
You run many data-loader Java programs that connect to the middle tier, which calls OMRHistoryDAO.java across many threads simultaneously.

When the deadlock occurs, the following error message is generated:

Found one Java-level deadlock:

=============================

"tomcat-http--69":

  waiting to lock monitor 0x00007f6838fe0fd8 (object 0x00000006875e96d8, a

com.sas.metadata.remote.MdObjectListImpl),

  which is held by "tomcat-http--58"

"tomcat-http--58":

  waiting to lock monitor 0x00007f688c02dff8 (object 0x0000000687a7f8e8, a

java.util.Collections$SynchronizedSet),

  which is held by "tomcat-http--69"

Java stack information for the threads listed above:

===================================================

"tomcat-http--69":

      at

com.sas.metadata.remote.MdObjectListImpl.contains(MdObjectListImpl.java:2341)

      - waiting to lock <0x00000006875e96d8> (a

com.sas.metadata.remote.MdObjectListImpl)

      at

com.sas.metadata.remote.MdObjectListImpl.generateObjectAndAssociationRemoveXML(M

dObjectListImpl.java:694)

      at

com.sas.metadata.remote.MdObjectListImpl.generateAssociationWriteXML(MdObjectLis

tImpl.java:593)

      at

com.sas.metadata.remote.AssociationList.generateAssociationWriteXML(AssociationL

ist.java:292)

      at

com.sas.metadata.remote.impl.MdObjectBaseXMLImpl.createUpdateAssociationXML(MdOb jectBaseXMLImpl.java:405)

      at

com.sas.metadata.remote.impl.MdObjectBaseXMLImpl.doCreateUpdateXML(MdObjectBaseX

MLImpl.java:430)

      at

com.sas.metadata.remote.impl.MdObjectBaseXMLImpl.createUpdateRequest(MdObjectBas

eXMLImpl.java:675)

      at

com.sas.metadata.remote.impl.MdObjectBaseXMLImpl.updateMetadataAll(MdObjectBaseX

MLImpl.java:529)

      at

com.sas.metadata.remote.MdObjectStoreImpl.updatedMetadataAll(MdObjectStoreImpl.j

ava:332)

      - locked <0x0000000687a7f8e8> (a java.util.Collections$SynchronizedSet)

      at com.sas.services.information.OMIServer.flush(OMIServer.java:6501)

      - locked <0x00000006879b2600> (a com.sas.services.information.OMIServer)

      at com.sas.services.information.metadata.Metadata.update(Metadata.java:1038)

      - locked <0x0000000687c9f1c0> (a

com.sas.services.information.metadata.favorites.impl.FavoritesFolderImpl)

      at

com.sas.svcs.content.history.dao.omr.OMRHistoryDAO.addHistoryItem(OMRHistoryDAO.

java:130)

. . .more log lines. . .

Click the Hot Fix tab in this note to access the hot fix for this issue.

This hot fix issue synchronizes the calls that are deadlocking.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS Web Infrastructure Platform	Linux for x64	9.4_M5		9.4 TS1M5

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

Type:	Problem Note
Priority:	high

Date Modified:	2020-02-07 13:54:04
Date Created:	2020-02-07 11:33:11

Support

Problem Note 65529: Deadlock or race conditions occur in the OMRHistoryDAO.java log file when you run many data-loader Java programs in the SAS® Model Risk Management UI

Operating System and Release Information