Symptoms
Order fails on the side of Business Automation with the following error:
Service Renewal Failed: Parallels Operations Automation error #extype_id #1, module_id #db_service, DBService invocation error: IJ000459: Transaction is not active: tx TransactionImple < ac, BasicAction: 0:ffff0a106f46:3125563a:553526a6:41b712 status: ActionStatus.ABORT_ONLY >.
The following errors can be found on the Operations Automation side in poa.log:
Apr 23 08:27:42 linmn01 : DBG [openapi:1.2.3.4:17422 1:30983:eb199b90 SAAS 1849874810]: [ APS::getApplicationInstancesImpl] ===> ENTRY
Apr 23 08:27:42 linmn01 : DBG [openapi:1.2.3.4:17422 RequestProcessor-67863 pau 1849874810]: com.parallels.pa.service.db.ejb.DBServiceBean Could not acquire connection idorg.hibernate.exception.GenericJDBCException: Could not open connection at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:54) ~[hibernate-core-4.2.7.SP1-redhat-3.jar!/:4.2.7.SP1-redhat-3] at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:125) ~[hibernate-core-4.2.7.SP1-redhat-3.jar!/:4.2.7.SP1-redhat-3] at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:110) ~[hibernate-core-4.2.7.SP1-redhat-3.jar!/:4.2.7.SP1-redhat-3]
Apr 23 08:27:42 linmn01 : DBG [openapi:1.2.3.4:17422 RequestProcessor-67863 pau 1849874810]: com.parallels.pa.service.db.ejb.DBServiceBean Executing non-locking query: ' SELECT ai.uuid, ai.app_instance_id, ai.app_id, app_ver, service_instance_id AS root_service_instance_id, uri, app_conf_id, ai.prov_type, a.name, CASE WHEN a.icon_name IS NULL OR a.icon_name = '' THEN '' ELSE COALESCE(a.images_root_path,'') || a.icon_name END AS app_icon_name, master_app_instance_id, ai.owner_id, resource_id, sr.sub_id, ai.status, si.disabled, si.unprovided FROM aps_application_instances ai LEFT JOIN aps_service_instances si ON (ai.app_instance_id = si.app_instance_id) AND (si.is_basic = 'y') JOIN aps_applications a ON ai.app_id = a.app_id LEFT JOIN subs_resources sr ON ai.resource_id = sr.rt_instance_id WHERE ai.app_instance_
Apr 23 08:27:42 linmn01 : DBG [openapi:1.2.3.4:17422 RequestProcessor-67863 pau 1849874810]: com.parallels.pa.service.db.db_serviceImpl Failure in DBServicejavax.ejb.EJBTransactionRolledbackException: Could not open connection at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(CMTTxInterceptor.java:162) ~[jboss-as-ejb3-7.3.0.Final-redhat-14.jar!/:7.3.0.Final-redhat-14] at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:252) ~[jboss-as-ejb3-7.3.0.Final-redhat-14.jar!/:7.3.0.Final-redhat-14] at org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:400) ~[jboss-as-ejb3-7.3.0.Final-redhat-14.jar!/:7.3.0.Final-redhat-14]
Apr 23 08:27:42 linmn01 : DBG [openapi:1.2.3.4:17422 RequestProcessor-67863 pau 1849874810]: com.parallels.pa.corba.ServiceInvoker Rethrowing EJB exception [converted]Plesk.ExSystem: IDL:Plesk/ExSystem:1.0 at com.parallels.pa.service.db.db_serviceImpl$1.convert(db_serviceImpl.java:54) ~[poakernel-ejb.jar:na] at com.parallels.pa.corba.ServiceInvoker.invoke(ServiceInvoker.java:114) [foundation.jar:na]
at com.parallels.pa.corba.ServiceInvoker.invoke(ServiceInvoker.java:92) [foundation.jar:na] at com.parallels.pa.service.db.db_serviceImpl.executeNLQuery(db_serviceImpl.java:132) [poakernel-ejb.jar:na] at Plesk.DBS.db_servicePOA._invoke(db_servicePOA.java:155) [foundation.jar:na] at org.jacorb.poa.RequestProcessor.invokeOperation(RequestProcessor.java:306) [jacorb-2.3.2.redhat-5.jar!/:2.3.2.redhat-5]
Apr 23 08:27:42 linmn01 : DBG [openapi:1.2.3.4:17422 1:30983:eb199b90 SAAS 1849874810]: [ APS::getApplicationInstancesImpl] <=== EXIT (by exception) [0.055768]
Cause
SaaS makes call for this original record com.parallels.pa.service.dns.DNSBaseManagerImpl Entering getDNSRecord, record_id: 260603 and in case it does not exists, SaaS catches the exception and wants to ignore this record. However, DB query that SaaS does after the exception is caught fails with another exception. The issue has been fixed in scope of the hotfix KB125196.
Resolution
Make sure that the hotfix KB125196 is installed on your OA environment.