From users-return-8957-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org Fri May 04 05:53:56 2007 Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 26713 invoked from network); 4 May 2007 05:53:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 May 2007 05:53:56 -0000 Received: (qmail 26189 invoked by uid 500); 4 May 2007 05:54:03 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 25926 invoked by uid 500); 4 May 2007 05:54:01 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 25917 invoked by uid 99); 4 May 2007 05:54:01 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 May 2007 22:54:01 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates 72.21.53.35 as permitted sender) Received: from [72.21.53.35] (HELO talk.nabble.com) (72.21.53.35) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 May 2007 22:53:53 -0700 Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1HjqjV-0003oz-8h for users@activemq.apache.org; Thu, 03 May 2007 22:53:33 -0700 Message-ID: <10317322.post@talk.nabble.com> Date: Thu, 3 May 2007 22:53:33 -0700 (PDT) From: Dogbert To: users@activemq.apache.org Subject: Sybase: FOR UPDATE can not be used in a SELECT ??? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: ffeuerstein@gmx.net X-Virus-Checked: Checked by ClamAV on apache.org Hi there. I am using Snapshot 'apache-activemq-4.2-SNAPSHOT-20070501.230521-46' and trying to use Sybase as persistence layer. My driver already got recognized "INFO JDBCPersistenceAdapter - Database driver recognized: [jconnect__tm__for_jdbc__tm_]" and the SybaseJDBCAdapter is used as well. The tables are created just fine at initial startup. I got a hanging transaction in the database and tried to find the source for that. In the 'normal' output everything seems to be just fine. After I recognized that there is also a logfile I got following additional information: com.sybase.jdbc2.jdbc.SybSQLException: FOR UPDATE can not be used in a SELECT which is not part of the declaration of a cursor or which is not inside a stored procedure. at com.sybase.jdbc2.tds.Tds.processEed(Tds.java:3281) at com.sybase.jdbc2.tds.Tds.nextResult(Tds.java:2548) at com.sybase.jdbc2.jdbc.ResultGetter.nextResult(ResultGetter.java:69) at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:220) at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:203) at com.sybase.jdbc2.jdbc.SybStatement.executeLoop(SybStatement.java:1785) at com.sybase.jdbc2.jdbc.SybStatement.execute(SybStatement.java:1777) at com.sybase.jdbc2.jdbc.SybPreparedStatement.execute(SybPreparedStatement.java:630) at org.apache.commons.dbcp.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.java:117) at org.apache.commons.dbcp.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.java:117) at org.apache.activemq.store.jdbc.DefaultDatabaseLocker.start(DefaultDatabaseLocker.java:60) at org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.start(JDBCPersistenceAdapter.java:176) ... Has anybody any idea what that can be???? Many thanks in advanced! Best regards, D. -- View this message in context: http://www.nabble.com/Sybase%3A-FOR-UPDATE-can-not-be-used-in-a-SELECT-----tf3690341s2354.html#a10317322 Sent from the ActiveMQ - User mailing list archive at Nabble.com.