added a comment -
2005-03-04 15:06 cloudcontextsecurity: multiple usernode update crashes webapp
cloudcontextsecurtiy has a feature that every time a user logs in, the lastlogon field of the mmbaseusers node is being updated. this is great except when you have a page in your website that gets a lot of hits and that opens a cloud as a certain user (not anonymous). in that case every request handling thread will que up to update that same mmbaseusers node, resulting in the death of your webapp.
solution:
- if you remove the lastlogon field from the mmbaseusers builder, the problem is gone, becouse the code checks for the existance of the field before the update takes place.
If you remove the field after installing cloud context security, you have to drop the 'not null' constraint on the lastlogon field in the database manually.
Bug
Resolved
Major
cloudcontextsecurtiy has a feature that every time a user logs in, the lastlogon field of the mmbaseusers node is being updated. this is great except when you have a page in your website that gets a lot of hits and that opens a cloud as a certain user (not anonymous). in that case every request handling thread will que up to update that same mmbaseusers node, resulting in the death of your webapp.
solution:
- if you remove the lastlogon field from the mmbaseusers builder, the problem is gone, becouse the code checks for the existance of the field before the update takes place