ORA-01453: SET TRANSACTION must be first statement of transaction

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.OracleClient.OracleException: ORA-01453: SET TRANSACTION must be first statement of transaction

Source Error:

Line 412: } Line 413: Line 414: _dataservice.SaveEntity(webs, false); Line 415: Line 416: Response.Redirect("default.aspx");

No much info in your post. (No version info, no code snippet and no stack trace).

Anyway please check the following thread (same exception): http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=15319

likely caused by sharing of dataaccessadapter instance over multiple threads / requests.

Otis wrote:

likely caused by sharing of dataaccessadapter instance over multiple threads / requests.

so should all data services within my project be referenced with a indvidual name I have always called them _dataservice never had a problem before

do you no how to solve this problem

it's not about naming, it's about instance sharing.

As it seems you have the _dataService as a member of the class and then it's shared between callers, right.

What's recommended is to have it locally defined within methods of the class, so it gets used and terminated once out of scope.

Walaa wrote:

it's not about naming, it's about instance sharing.

As it seems you have the _dataService as a member of the class and then it's shared between callers, right.

What's recommended is to have it locally defined within methods of the class, so it gets used and terminated once out of scope.

so remove my dll and place the adapter code inside the scope of the source file then

Not neccesarily - just have each call to your data layer create its own instance of the DataAccessAdapter, rather than having one persisted as a class member

Using the following method ensures the the adapter is always cleaned up properly when you have finished with it.

using (DataAccessAdapter daa = new DataAccessAdapter(connString)
{
   daa.SaveEntity...

}

Matt

MTrinder wrote:

Not neccesarily - just have each call to your data layer create its own instance of the DataAccessAdapter, rather than having one persisted as a class member

Using the following method ensures the the adapter is always cleaned up properly when you have finished with it.

using (DataAccessAdapter daa = new DataAccessAdapter(connString)
{
   daa.SaveEntity...

}

Matt

I do this already with

    public void SaveEntity(IEntity2 entity, bool refetch)
    {

        using (DataAccessAdapter adapter = new DataAccessAdapter())
        {

            adapter.SaveEntity(entity, refetch, true);          
        }
    }

mmm

Would you please provide the LLBLGen Pro runtime library version number. Also we will need the stack trace of the exception.