Ticket #1206 (closed defect: fixed)

Opened 1 year ago

Last modified 11 months ago

Sitegroup cache gets confused in staging/live situations

Reported by: bergie Assigned to: piotras
Priority: blocker Milestone: 8.09.6 Ragnaroek
Component: Midgard Apache Version: 8.09 Ragnaroek
Keywords: Cc:

Description

When using staging/live in setup where both live and staging databases are running in same Apache process the cache can get confused if sitegroup has different IDs in live and staging database.

You get something like: 

midgard-core (pid:22548):(debug):query=SELECT id,password FROM person WHERE username='diasadmin' AND sitegroup=17 AND person.metadata_deleted=0 
midgard-core (pid:22548):(info):Authentication type: NORMAL
...
midgard-core (pid:22548):(info):Setting sitegroup 'dias' (id: 11)

See how the SG changes from 17 (the one in current DB being used) to 11 (the other database).

Change History

07/07/09 10:42:00 changed by jval

I'm not familiar with this issue in any way, but sounds like the cache should be per vhost (it's apparently currently just global). Midgard database is defined per vhost, so naturally caching should also be per vhost.

07/28/09 20:58:47 changed by piotras

  • status changed from new to assigned.

Forgot to mention ticket in commit. Fix applied in r22523.

10/05/09 14:51:58 changed by piotras

  • status changed from assigned to closed.
  • resolution set to fixed.

Already fixed

10/20/09 20:01:13 changed by jval

Ah this was not about preparse apparently. Forget my comment because preparse caching happens per db and that's fine.