Java Prepared Statement - concurrency and performance

From: <nmp93_at_my-deja.com>
Date: Mon, 13 Dec 1999 16:35:22 GMT
Message-ID: <83378b$cjg$1@nnrp1.deja.com>

According to the Oracle documentation, "...any public static Java method can run in the RDBMS as a stored procedure..."

Please correct me if I'm wrong, but doesn't this raise a whole host of concurrency issues. If the method is static, Oracle's JVM will use the 'same' method for all calls made upon a given stored procedure. In a multi-client system there would be the possibility of muddled results - or am I missing the point? Why doesn't the Oracle JVM execute each stored procedure as a separate object instance/thread???

Also, wouldn't a Java Stored Procedure execute quite slowly i.e. you have two lots of JDBC overheads, one from the stored procedure to the oracle database and the JDBC overhead from using the callable statement that calls the stored procedure?

Might it be more effective to RMI or Socket between the stored procedure and the the client or middle tier?

Many thanks in advance.

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Mon Dec 13 1999 - 10:35:22 CST