Narayana transaction manager (TM) had been integrated into Tomcat in order to enable the use of the XA transactions. If not implemented, there could be deadlocks, especially when MS Sql server is used.Ĭheck that the settings listed in the Database creation and settings to work with Bonita documentation page have been implemented. The current XA transaction timeout limit is too smallīonita requires specific database server settings.or an extra Garbage Collector's threads activity, triggered by a java memory shortage (-Xmx), leaves nothing to java application's threads.either an environmental problem impacts the CPU or Disk I/O.There are performance issues which slow down Java process:.The users are using the portal so that it triggers searches (via the REST API) which need a long time to execute.A client application calls the Engine API or the REST API which triggers searches which need a long time to execute.There are shortage of connection in the pools associated to datasources.Transactions are waiting for locks, when there are deadlocks. These messages in the log files show that there are XA transactions which time out. ARJUNA012095: Abort of action id 0.e invoked while multiple threads active within it.HibernateException: Current transaction is not in progress.HibernateException: Logical connection is closed.ARJUNA016102: The transaction is not active!.The messages in the log files are appended at the end. Component: Bonita | Version: 7.9 What's wrong?
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |