Kbase P67884: Dyn 2.1A Many reads in gsm_session_property when starting a
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/17/2004 |
|
Status: Unverified
SYMPTOM(s):
Many db reads in gsm_session_property when starting a new Dynamics session
CAUSE:
Known issue with DB Bound session types like ICFDev or ASICFDev, but not with a thin client session (ICFRunTime). gsm_session_property has about 73 records, but starting a new session can lead to about 8000 db read in this table.
In version 2.1, we went from accepting the config.xml file as authentic, to validating it against the database. This means that every physical session that now starts against a database needs to generate the equivalent of the config.xml file.
The code that does this has to walk the entire session type hierarchy to figure out what properties, services and managers apply to which session types.
Properties are particularly problematic because for each session type we need to go through every property in gsc_session_property and figure out whether there is a corresponding gsm_session_type_property record. This is because the always_used flag needs to be respected for each session type.
It is possible that we could revisit and rearchitect the way that this code works, but this was not considered as a high priority issue when we went to 2.1A.
Now bear in mind that when I say that this happens once during a physical session, on the AppServer this means that it only ever happens when the AppServer is started. It does not happen each time a connection is made.
FIX:
none