94
Views
1
Comments
Error closing the transaction to the database
Question

Has anyone experienced this situation on the FrontEnd the actions are being performed but on the Server side hi have this error


Error closing the transaction to the database: Invalid operation on a closed object
    at Oracle.ManagedDataAccess.Client.OracleTransaction.Commit()
    at OutSystems.HubEdition.Extensibility.Data.TransactionService.GenericTransactionManager.EndTransaction(TransactionInfo transInfo, Boolean commit, Boolean toFreeResources)
    at OutSystems.HubEdition.DatabaseProvider.Oracle.TransactionService.TransactionManager.EndTransaction(TransactionInfo transInfo, Boolean commit, Boolean toFreeResources)
    at OutSystems.HubEdition.Extensibility.Data.TransactionService.GenericTransactionManager.SafeEndTransaction(TransactionInfo transInfo, Boolean commit, Boolean toFreeResources, CloseConnectionTransactionException& closeConnectionException)
    at OutSystems.HubEdition.Extensibility.Data.TransactionService.GenericTransactionManager.SafeEndTransaction(TransactionInfo transInfo, Boolean commit, Boolean toFreeResources, CloseConnectionTransactionException& closeConnectionException)
    at OutSystems.HubEdition.Extensibility.Data.TransactionService.GenericTransactionManager.FreeupResources(Boolean commit)
    at OutSystems.Internal.Db.DatabaseAccess.InnerFreeupResources(Boolean commit)
    at OutSystems.Internal.Db.DatabaseAccess.FreeupResources(Boolean commit)
    at ssGestaoBloco.Global.Application_EndRequest(Object sender, EventArgs e)
    at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
    at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
    at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
    at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)
    at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)
    at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)
    at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
    at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
    at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)
    at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)
    at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
    at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) 

2026-03-04 12-08-39
Luiz Henrique Stanqueviski

Hi Bruno,

Probably some action may be controlled in your application flow that is closing an open session in the database, so, at the end of the process, when the connection is requested to close, it is already closed.

Could you send more details of the process so that we can try to analyze and find the failure point?

Regards.

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.