Re: Experiences setting OPEN_CURSORS for Java applications

2003-10-03 Thread Prem Khanna J
Craig, Thanx for your tool. Right now,let us (developers) use it with Jboss and let u know if there is any issue. Thanx a lt for your support. Regards, Jp. 02-10-2003 21:41:15, Craig Munday [EMAIL PROTECTED] wrote: Jp, I've forwarded you a separate email with the tool included as an

Re: Experiences setting OPEN_CURSORS for Java applications

2003-10-02 Thread Craig Munday
Jp, I've forwarded you a separate email with the tool included as an attached zip file. In answer to your questions: The JDK version is 1.4.1 and above. I do not expect any problems with JBOSS 3.2.1 and higher although I would be interested in hearing about any problems should you come

Re: AW: Experiences setting OPEN_CURSORS for Java applications

2003-10-02 Thread Craig Munday
?). Stefan -Ursprüngliche Nachricht- Von: Craig Munday [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 1. Oktober 2003 02:44 An: Multiple recipients of list ORACLE-L Betreff: Re: Experiences setting OPEN_CURSORS for Java applications Tanel, I've implemented it as a JDBC driver that is installed

AW: AW: Experiences setting OPEN_CURSORS for Java applications

2003-10-02 Thread Stefan Jahnke
: AW: Experiences setting OPEN_CURSORS for Java applications Hi, I'm not sure about the Interceptor pattern. Log4j is a great package and I make use of it within JDBC Expert. I started using the new logging API in JDK 1.4 but found most developers were using Log4j so I changed. Log4j seems

AW: Experiences setting OPEN_CURSORS for Java applications

2003-10-01 Thread Stefan Jahnke
: Craig Munday [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 1. Oktober 2003 02:44 An: Multiple recipients of list ORACLE-L Betreff: Re: Experiences setting OPEN_CURSORS for Java applications Tanel, I've implemented it as a JDBC driver that is installed as a layer between your application

Re: Experiences setting OPEN_CURSORS for Java applications

2003-09-30 Thread Craig Munday
can send you a copy if you are interested - you will have to forward me your JDK version and details about any app server that you are using. Regards, Craig Munday. At 08:34 AM 26/09/2003 -0800, you wrote: I would just like to know what are your experiences setting OPEN_CURSORS for Java

Re: Experiences setting OPEN_CURSORS for Java applications

2003-09-30 Thread Tanel Poder
I've encountered this problem so often that I decided to write a tool (called JDBC Expert) that would help us DBAs (and developers) detect Statement and ResultSet leaks in Java applications. I've found this tool so useful and effective at finding resource leaks that I insist any in house

Re: Experiences setting OPEN_CURSORS for Java applications

2003-09-30 Thread Prem Khanna J
Craig, CMI can send you a copy if you are interested - CMyou will have to forward me your JDK version and details about any app CMserver that you are using. I would , sure , be very much interested in having a copy of that tool. developers here use diff. versions of JDK apache/tomcat/jboss

Re: Experiences setting OPEN_CURSORS for Java applications

2003-09-30 Thread Craig Munday
Tanel, I've implemented it as a JDBC driver that is installed as a layer between your application and the vendor driver that you are using (eg. Oracle, Postgress, SQL Server, etc.) [Java application] - Layer 1 [JDBC Expert] - Layer 2 [Oracle Thin Driver] - Layer 3 | network | [Oracle

Re: Experiences setting OPEN_CURSORS for Java applications

2003-09-30 Thread Tanel Poder
Thanks for the answer. Yep, it seems more like JDBC proxy with analyzing capabilities than a regular traffic analyzer which sits aside sniffs some packets. May I ask, how much time have you spent on writing such thing? I'm planning to write something similar, but on SQL*Net level... Tanel.

Experiences setting OPEN_CURSORS for Java applications

2003-09-26 Thread Hemant K Chitale
I would just like to know what are your experiences setting OPEN_CURSORS for Java applications / middle-tier application servers ? We're rolling out a bunch of applications on WebMethods, Tivoli Identity Manager, Plumtree, Documentum etc --- all non-Oracle clients accessing the database through