Re: A Very Serious problem -- The cursor SQLCUR7 is not in a prepared state

2003-06-26 Thread anuradha devi
: anuradha devi [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 7:27 AM Subject: A Very Serious problem -- The cursor SQLCUR7 is not in a prepared state Hi all, We are working on a web application which was developed on OJB0.9.5. The system is very well

Re: FW: java.net.MalformedURLException: no protocol: repository.dtd -- solved

2003-06-24 Thread anuradha devi
: repository.dtd Not sure this will help, ... In the past, I have received this exception when I was using a old version of Xerces with a package that was expecting a new version. Thoughts? Jim Shingler -Original Message- From: anuradha devi [mailto:[EMAIL PROTECTED] Sent

A Very Serious problem -- The cursor SQLCUR7 is not in a prepared state

2003-06-24 Thread anuradha devi
Hi all, We are working on a web application which was developed on OJB0.9.5. The system is very well working normally. When it comes performance testing, when 3 users tried to hit the system concurrently with 2 as maximum no. of connections at one point we got the following exception. [IBM][CLI

illegal multi-threaded access detected

2003-06-23 Thread anuradha devi
Hi, We are working on a web application which is built on OJB0.9.5. Particularly we are using ODMG for transaction maintainance and PB API for database operations. When we are performing load test on our application we are getting this error. Has anyone faced this problem earlier or anyone has any

RE: java.net.MalformedURLException: no protocol: repository.dtd

2003-06-23 Thread anuradha devi
Hi Tom, It still gives me the same problem. Any other solution for this.. Pls let me know Thanks --- Thomas Dudziak [EMAIL PROTECTED] wrote: In the CVS source, the doctype declaration is somewhat different (and this works though I don't know whether the used XML parser is Xerces or

RE: java.net.MalformedURLException: no protocol: repository.dtd

2003-06-23 Thread anuradha devi
Hi Tom, It still gives me the same problem. Any other solution for this.. Pls let me know Thanks --- Thomas Dudziak [EMAIL PROTECTED] wrote: In the CVS source, the doctype declaration is somewhat different (and this works though I don't know whether the used XML parser is Xerces or