[ https://forge.continuent.org/jira/browse/SEQUOIA-220?page=all ] Stephane Giron closed SEQUOIA-220: ----------------------------------
Closing (fix tested by user) > Stored Procedure Names Missing, Causing CallableStatement.execute() To Fail > --------------------------------------------------------------------------- > > Key: SEQUOIA-220 > URL: https://forge.continuent.org/jira/browse/SEQUOIA-220 > Project: Sequoia > Type: Bug > Components: Core > Versions: Sequoia 2.3 > Environment: Sequoia from CVS (Checkout 15:30 PDT, Nov 23), PostgreSQL 7.4.8 > Backends > Reporter: Dylan Hansen > Assignee: Stephane Giron > Priority: Blocker > Fix For: Sequoia 2.5 > > > These issues are directly related: > 1. When a stored procedure call is logged in the recovery log, the stored > procedure name isn't logged. I'm assuming that this will break when a > recovery is tried. Here is an output from some stored procedure calls: > 45 | h2st | (<!%S|j398v2842b190bv90|!%>,<!%S|test/32c32v3avad23|!%>) > | 10 > 47 | h2st | (<!%S|3232v2vaveav2323|!%>,<!%S|0|!%>,<!%I|56|!%>) > | 10 > 2. CallableStatement.execute() fails because of the above issue, when it > goes to execute the request on the backend there are only a list of > parameters, no stored procedure name: > 2005-11-23 16:09:49,941 ERROR controller.loadbalancer.RAIDb1 stored procedure > 504 failed: > Backend GTDatabasenode01 failed (null) > 2005-11-23 16:09:49,942 DEBUG sequoia.controller.scheduler Stored procedure > completed, remaining pending writes: 0 > 2005-11-23 16:09:49,942 WARN controller.RequestManager.h2st SQLException > while executing distributed read stored procedure (stored procedure 504 > failed: > Backend GTDatabasenode01 failed (null) > ). > java.sql.SQLException: stored procedure 504 failed: > Backend GTDatabasenode01 failed (null) > at > org.continuent.sequoia.common.exceptions.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:92) > at > org.continuent.sequoia.controller.loadbalancer.raidb1.RAIDb1.checkTaskCompletion(RAIDb1.java:853) > at > org.continuent.sequoia.controller.loadbalancer.raidb1.RAIDb1.callStoredProcedure(RAIDb1.java:765) > at > org.continuent.sequoia.controller.loadbalancer.raidb1.RAIDb1.callableStatementExecute(RAIDb1.java:684) > at > org.continuent.sequoia.controller.requestmanager.RequestManager.loadBalanceCallableStatementExecute(RequestManager.java:1241) > at > org.continuent.sequoia.controller.virtualdatabase.protocol.DistributedCallableStatementExecute.executeScheduledRequest(DistributedCallableStatementExecute.java:91) > at > org.continuent.sequoia.controller.virtualdatabase.DistributedVirtualDatabase.handleMessageMultiThreaded(DistributedVirtualDatabase.java:887) > at > org.continuent.hedera.adapters.MulticastRequestAdapterThread.run(MulticastRequestAdapterThread.java:75) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://forge.continuent.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
