Hi, My problem involves memory management between mod_perl processes. I am running AxKit 1.5, with PerForm and the *new* session taglib. I am using the Tangram framework for OO<->rdbms interface. This library keeps cached versions of the db objects in memory.
If I limit apache to one process, forms under PerForm stop working (why?). If I don't limit, accessing an AxKit page starts at least one additional apache process, so that I have at least two. Why ? Is this because AxKit is large ? Ok, so now if I make a change in a form which runs in one mod_perl instance, the other mod_perl instance doesn't know about it, and returns me incorrect image of the db state. If I refresh my XSP page continously, the serving mod_perl process alternates. I am able to observe that different mod_perl processes are involved by doing $r->warn($$) from my taglib. I tried to take AxKit out of the equation, and write similar code with plain mod_perl modules. I was not able to get it so that several mod_perl processes are involved. In fact, only one mod_perl process got started this time. How can I workaround this problem so that I can have a running site as soon as possible ? What's the best way to go in the long run ? Thank you, Boris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
