Telegram_2020-04-13T17

<< Click to Display Table of Contents >>

Navigation:  Telegram > 2020 > 04 > 13 >

Telegram_2020-04-13T17

Telegram link

 

2020-04-13T17:38:59

 

1- \session data from different users were mixed\

 

This only happens if you have global objects/state being shared. Have you tested your application without pooling with multiple users?

 


 

Telegram link

 

2020-04-13T17:47:57

 

Yes, I did.

 

The problem is we can not allow so many connections on this DB.

 

The mixing problem is reduced right know. I may say, it's eradicated (hope so). I have rewrited the unlockdatamodule to close and rollback before releasing DM to the pool.

 

The calling form does not save any reference to the DM and subsequent calls on this same form can not use a DM without LockDatamodule first.

 

The thing is that this way of work is generating http error 500 on dll web app with a small amount of users and I think is because I am not using the pooling mechanism in a correct way. Are there any best practices on this?

 

I should not use it?

 

Should I move the DataModule instance to UserSession and maintain an open connection for every loggued user?

 

Thank you