session - Number sequences issues -


we have issue, more like, whether worker or client sessions crash , these sessions in process of using number sequences create new record, end blocking number sequence literally , else trying create record using same sequence have client frozen.

when happens, go in numbersequencelist table, spot correct dataareadid , user, , delete row status = 1.

but kind of annoying really. there anything, way can configure aos server release number sequence when client/workers crash ?

for worker sessions, guess can fine tweak code runs in them, client sessions crashing, not can do...

any ideas ?

thanks!

edit: turns out in situation, after restarting aos server, can go in list in number sequence menu, , clean up. prior restart, client freeze trying that. no need directly through sql.

continuous numbers in numbersequencelist automatically cleaned every 24 hours (or set on number sequence). cleanup process quite slow if there many "dead" numbers (hundreds or thousands). may considered hang, not.

things consider:

  • is continuous number sequence needed?
  • do cleanup more frequent (say every half hour instead of default 24 hour)
  • setup cleanup process batch process
  • fix bug in client code using number sequence

also avoid reserving number, use it. instead of anti-pattern:

numberseq idsequence = numberseq::newgetnum(intrastatparameters::numrefintrastatarchiveid(), true); this.intrastatarchiveid = idsequence.num(); idsequence.used(); 

just use number:

this.intrastatarchiveid = numberseq::newgetnum(intrastatparameters::numrefintrastatarchiveid()).num(); 

the makedecisionlater parameter should used in forms, user may decide not use number (by delete or escape). , in case numberseqformhandler class should used anyway.


Comments

Popular posts from this blog

Android layout hidden on keyboard show -

google app engine - 403 Forbidden POST - Flask WTForms -

c - Why would PK11_GenerateRandom() return an error -8023? -