Oracle and Java - a useful partnership?

According to the Oracle documentation, "...any public static Javamethod 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/performance 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 of bottlenecks caused by synchronization ---- OR am I missing the point?

Why doesn't the Oracle JVM execute each stored procedure as a separate object instance/thread??? Someone suggested that a different JVM might handle each call on the Stroed Procedure in a separate JVM. Wouldn't the overheads be very high for such an approach??

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

Might it be more effective to RMI or Socket between the stored procedure and the the client or middle tier? But, how could this be done? Call the procedure once to 'activate it' and then it could run waiting for requests.

Many thanks in advance.

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Tue Dec 14 1999 - 03:49:21 CST