Activities of "Priyanka"

Sorry, should be CompleteAsync. (because there is no IDE code prompt here)

ok, thank you for the solution. It is working.

Hi,

you need to roll back the main transaction, and create a new transaction to record the log.

try 
{ 
   await _repositpry.InsertAsync(...xxxx, autoSave: true) 
} 
catch(exception e) 
{ 
   await _unitOfWorkManager.Current.RollbackAsync(); 
} 
final 
{ 
  using (var uow = UnitOfWorkManager.Begin(requiresNew: true, isTransactional: true)) 
  {  
       ..... 
        
       await uow.CommitAsync(); 
  } 
} 

Hi, Thank you for the solution but uow.CommitAsync() is having compile time error

Can we use CompleteAsync? What is the difference between commit and complete here in this case ?

i meant something like this here;

https://github.com/serilog-mssql/serilog-sinks-mssqlserver

does that work for you?

Log event is already there, we have case where our service is called by external user so we are keeping log of that service where we need to keep request message, response message, current status, messageId etc and this table data is accessible to user to know the status of request hence we are keeping in separate table. Please help me with the solution to insert data in my log table without any exception of try block transaction.

why don't you configure a serilog sink to db? and just call Logger.LogError or something?

We have requirement to keep log in DB. While Inserting in DBlog table I'm getting the same exception which I want to log in DB table.

I have a service where I'm doing Insert and update in Mutiple table and in case of any exception, I'm logging in DB log table in finally section. I'm getting this exception in Insert or update "String or binary data would be truncated in table 'Addresses', column 'Street'. Truncated value: 'Severe depressive episode without psychotic symptoms, not specified as arising in the postnatal peri' , now when I'm logging the error in DB log table, on insert of log table I'm getting the same exception. My Log method for DB log have attribute- [UnitOfWork(IsDisabled = true)], seems like on log insert it is trying to complete the whole transaction, how to resolve this?

ABP Framework version: v5.3.2

UI Type:React

Database System: EF Core (SQL Server)

Tiered (for MVC) or Auth Server Separated (for Angular): yes

Exception message and full stack trace:NA

Steps to reproduce the issue: Call Insert where some exception is there and in Finally call insert to log the exception in logTable.

sure, but what is the difference between both, as per my understanding we can call LoggedOutModel after overriding.

What is the difference if we call below mention functions: await httpContext.RequestServices.GetRequiredService<AbpSignInManager>().SignOutAsync(); await httpContext.RequestServices.GetRequiredService<LoggedOutModel>().OnGetAsync();

ABP Framework version: v5.3.2

UI Type:React

Database System: EF Core (SQL Server)

Tiered (for MVC) or Auth Server Separated (for Angular): yes

Exception message and full stack trace:NA

Steps to reproduce the issue: Login and Logout

Hi,

So, preventing concurrent logins from different browsers is working now but the previous browser did not redirect to the login page

You can redirect:

if (httpContext.User.Identity != null && httpContext.User.Identity.AuthenticationType == "Identity.Application") 
{ 
    await httpContext.RequestServices.GetRequiredService<AbpSignInManager>().SignOutAsync(); 
    //await httpContext.ChallengeAsync("Identity.Application"); 
     
    var redirectUrl = "..."; 
    httpContext.Response.Redirect(redirectUrl); 
    return; 
} 

I tried this but it is stuck in infinite loop, it is redirecting to login and somehow it is coming again on this condition, condition is satisfied and redirecting again and this whole process is keep going.

sorry, you can't do that in the LoggedOutModel class

Ok, thanks for your support.

Yes, you can do that in the LoggedOutModel class

If we can, then could you please help how can we?

Showing 101 to 110 of 126 entries
Made with ❤️ on ABP v8.2.0-preview Updated on March 25, 2024, 15:11