<div>Thanx for the guidance. </div>
<div> </div>
<div>I did figure out that the whole problem was happening because of threads trying to access the ZODB. For the time being, I got rid of that, and had a separate sheduler event which queries the background threads to get update information and put it in the ZODB. It seems to work well.
</div>
<div> </div>
<div>With regards,</div>
<div>-Shailesh</div>
<div><br><br> </div>
<div><span class="gmail_quote">On 1/8/07, <b class="gmail_sendername">Stephan Richter</b> <<a href="mailto:srichter@cosmos.phy.tufts.edu">srichter@cosmos.phy.tufts.edu</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Wednesday 03 January 2007 05:46, Shailesh Kumar wrote:<br>> In my application, some background threads are being created. But when a
<br>> thread finishes up its work, a strange exception is thrown:<br>> The callstack doesn't show any part of my application code.<br><br>You have to use threads very carefully, if they modify the database. The<br>
correct way is to create a new connection to the ZODB do your work, commit<br>the transaction and close the connection. Pretty much copy what the publisher<br>does. Another alternative is to create a new publisher request of course.
<br><br>Regards,<br>Stephan<br>--<br>Stephan Richter<br>CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student)<br>Web2k - Web Software Design, Development and Training<br></blockquote></div><br>