Base solution for your next web application
Starts in:
01 DAYS
01 HRS
01 MIN
01 SEC
Open Closed

Cannot see the error message detail #1357


User avatar
0
justin created

I am not able to see the detail of error message after a call is made to a service endpoint via abp dynamic web api. it does not hit any breakpoints it does not have any in log file . it only shows a pop up saying [object object ] internal server error . i also added code below in my web project and it does not execute it either. it seems the error does not bubble up throught the web application and its consumed by abp modules. i am using abp 0.91

public class MyExceptionHandler : IEventHandler<AbpHandledExceptionData>, ITransientDependency
    {
        public ILogger Logger { get; set; }

        public void HandleEvent(AbpHandledExceptionData eventData)
        {
            Logger.Info(eventData.EventSource.ToString(), eventData.Exception);
        }
    }


3 Answer(s)
  • User Avatar
    0
    justin created

    i was able to GUESS what my problem was , but ABP should be able to throw those exception above. it was in DI layer i think. because i had my class defined as

    public partial class PersonDataRepository : , IPersonDataRepository
    {
    
    }
    
    
    public interface IPersonDataRepositoryExtended : IPersonDataRepository
    {
    
    }
    public partial class PersonDataRepository :  IPersonDataRepositoryExtended, ISingletonDependency
    {
    
    }
    
    
    and i had depndency on IPersonDataRepositoryExtended
    
  • User Avatar
    0
    ismcagdas created
    Support Team

    All the errors should be logged to Logs.txt under Logs folder of your solution normally. But, I couldn't understand why it didn't write logs. Can you explain your case a little bit more, so we can try the same case.

  • User Avatar
    0
    guillaumej created

    I had the same kind of problem (forgot an IApplicationService so DI was not working), and I think it was not handled by ABP because the error came before ABP error handling was set up.

    BTW, in unit tests, the error was clearly visible.