I just had a thought ... do the same threading issues occur in the PersistenceBroker API?
Anyone, anyone? ;-) -- Jason ----- Original Message ----- From: Jason Mihalick To: [EMAIL PROTECTED] Sent: Saturday, September 28, 2002 8:09 AM Subject: Threading problems in the ODMG API -- HELP needed Can anyone confirm whether the following messages kindly posted by Andrey Chernyh ([EMAIL PROTECTED]) is the only solution to the multithreading issues associated with Databases and Transactions in the ODMG API? http://archives.apache.org/eyebrowse/ReadMsg?[EMAIL PROTECTED] e.org&msgNo=1748 http://archives.apache.org/eyebrowse/ReadMsg?[EMAIL PROTECTED] e.org&msgId=458647 Using the standard OJB instance in an app server such as Tomcat results in the infamous "TransactionImpl created with null DatabaseImpl" error when creating Transactions on a per (http) request basis. I have temporarily "fixed" the problem in Tomcat by setting minProcessors=0 and maxProcessors=1, which forces Tomcat to only spawn a single HttpProcessor thread (but, simultaneously, forces connection requests from multiple users to be backed up until the HttpProcessor can handle them ... one at a time). For more information on setting those parameters see http://jakarta.apache.org/tomcat/tomcat-4.0-doc/config/http11.html Thanks in advance, Jason -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
