Sign In  Sign Up Live-Chat

Disposing the EngineManager and description of locking mechanism

Last post 01-05-2008, 4:59 AM by iret. 4 replies.
Sort Posts: Previous Next
  •  11-26-2007, 3:03 AM 103892

    Disposing the EngineManager and description of locking mechanism

    Dear Community,

    We have a separate connection pool in IIS for ASPOSE. Every time a request is sent by user for workflow we create a new instance of EngineManager and destroy it after completing the task. Since we don't have a proper dispose method in EngineManager, we dispose the instance by assigning it null value. Because of this method the database connections with the EngineManager is not closing properly, which results in high number of open cursors in oracle database.

    What is the proper way to dispose off EngineManager's instance? We need to dispose off EngineManager on immediate basis after completing the task so that we can optimally utilize our connection pool.

    Currently users are facing delay in their request fullfillment.We have received a report from our DBA that out of all the total database wait time ASPOSE WORKFLOW_LOCK takes up around 97%.

     

    Regards,

    Ahsanullah Bughio

     

     
  •  11-29-2007, 9:40 AM 104512 in reply to 103892

    Re: Disposing the EngineManager and description of locking mechanism

    Hello,

    Our engineer is working on this issue. Some questions:

    1. Could you share part of your code about the disposing?

    2. What database are you using? sql 2000 or sql 2005? What's the IIS version?

    3. How many active users in the system?

    We will get back to you shortly.

    Thanks


    Team Lead
    Aspose Guangzhou Team
    About Us

    Contact Us
     
  •  12-03-2007, 8:00 AM 104937 in reply to 104512

    Re: Disposing the EngineManager and description of locking mechanism

    Attachment: Present (inaccessible)
    Dear Iret,
    Here are the answers to your question.

    1. Could you share part of your code about the disposing?
    File (EngineMain.cs) is attached.
    2. What database are you using? sql 2000 or sql 2005? What's the IIS version?
    Neither SQL 2000 nor SQL 2005, we are using oracle 10g.
    3. How many active users in the system?
    Currently 200+, will be increased 2000+ in mid of december.

    regards,

    Ahsanullah Bughio

     
  •  12-10-2007, 9:28 AM 105758 in reply to 104937

    Re: Disposing the EngineManager and description of locking mechanism

    Thanks for your reply.

    Our development team is working on this issue. We will get back to your shortly.

    Best wishes


    Team Lead
    Aspose Guangzhou Team
    About Us

    Contact Us
     
  •  01-05-2008, 4:59 AM 107824 in reply to 105758

    Re: Disposing the EngineManager and description of locking mechanism

    Hello,

    Could you reuse the EngineManager instance? It is designed as a configruation and entry class. Just keep one copy in the life cycle of the system.

    Thanks,


    Team Lead
    Aspose Guangzhou Team
    About Us

    Contact Us
     
View as RSS news feed in XML