Calling Stored Procedures from Spring

[Russell Peters]

When I try to call a stored procedure from the spring framework, my log files keep increasing in size due to a lot of writes to it and then after about 30 mins I get OutOfMemoryError.
I am using the StoredProcedure class from the spring framework.

Here's what I have so far

Oracle Stored Procedure

 create or replace PROCEDURE VALIDATE_PRC(inRequestId in NUMBER) AS
vRes     NUMBER := null 

BEGIN
  
   vRes := Process_Request(inRequestId, 'VALIDATE')

END VALIDATE_PRC;  

My StoredProcedure class

public class ValidateRequest_PRC extends StoredProcedure {

	private static Logger logger = Logger.getLogger(ValidateRequest_PRC.class);
	private static final String STORED_PROC_NAME = "VALIDATE_PRC";
	
	public ValidateRequest_PRC(JdbcTemplate jdbcTemplate) {
		super(jdbcTemplate, STORED_PROC_NAME);
		//setFunction(true);
		declareParameter(new SqlParameter("requestId", Types.NUMERIC));
		compile();
	}
	
	
	public void execute(int requestId) {
        Map inParams = new LinkedHashMap(1);
        inParams.put("requestId", requestId);

        execute(inParams);
    }
}

Note the commented out line "setFunction(true)". If I uncomment it, I get a SQLException with the following message :

PLS-00306: wrong number or types of arguments in call to VALIDATE_PRC. 

I thought that setFunction(true) should only be for functions. But since I have a procedure, I shouldn't be setting it correct?

My DAO which calls the above StoredProcedure class

ValidateRequest_PRC proc = new ValidateRequest_PRC(jdbcTemplate_);
        proc.execute(anonReqID);

Any help is appreciated.

Thanks in advance..

[Russell Peters]

Update:

I searched google a lot and came across one post which indicated that the ojdbc14 jar file that the server might be using may have a bug which may cause the above issue.

I was using tomcat 6.0.13 which was using ojdbc14 - version 10.1.0.2. I, then ran the code on the weblogic instance and everything worked. Weblogic was using 10.2.0.2 version of the ojdbc14.

I copied over the 10.2.0.2 in my tomcat installation and everything worked. The latest ojdbc14 is at 10.2.0.4 -- I haven't tested it with the latest but if anyone else is experiencing a similar problem, you may want to check out the ojdbc14 versions before mucking around in the code.

Good Luck.