Hi:
Tried using postgresql driver build 400 in placed of build 407. Got the
following error in both controller when enabling:
--------------------------------------------
n: Failed to get information about database schema: java.sql.SQLException:
Unable to fetch columns for table public.seq_document_sec_settings
08:50:06,687 WARN DatabaseBackend.System_DB.System_DB1 Failed to get
exported keys for table public.seq_document_sec_settings
org.postgresql.util.PSQLException: ERROR: current transaction is aborted,
commands ignored until end of transaction block
at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1471)
at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1256)
at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:175)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:389)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:314)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:221)
at
org.postgresql.jdbc2.AbstractJdbc2DatabaseMetaData.getImportedExportedKeys(AbstractJdbc2DatabaseMetaData.java:3237)
at
org.postgresql.jdbc2.AbstractJdbc2DatabaseMetaData.getExportedKeys(AbstractJdbc2DatabaseMetaData.java:3591)
at
org.continuent.sequoia.controller.backend.DatabaseSQLMetaData.getExportedKeys(DatabaseSQLMetaData.java:697)
at
org.continuent.sequoia.controller.backend.DatabaseSQLMetaData.createDatabaseSchema(DatabaseSQLMetaData.java:180)
at
org.continuent.sequoia.controller.backend.DatabaseBackendMetaData.createDatabaseSchemaDynamically(DatabaseBackendMetaData.java:918)
at
org.continuent.sequoia.controller.backend.DatabaseBackendMetaData.getDatabaseSchema(DatabaseBackendMetaData.java:954)
at
org.continuent.sequoia.controller.backend.DatabaseBackend.checkDatabaseSchema(DatabaseBackend.java:1798)
at
org.continuent.sequoia.controller.backend.DatabaseBackend.refreshSchema(DatabaseBackend.java:2111)
at
org.continuent.sequoia.controller.backend.DatabaseBackend.getDatabaseSchema(DatabaseBackend.java:1914)
at
org.continuent.sequoia.controller.loadbalancer.BackendTaskQueues.fetchNextQueryFromBackendTotalOrderQueue(BackendTaskQueues.java:785)
at
org.continuent.sequoia.controller.loadbalancer.BackendTaskQueues.getNextCommitRollbackToExecute(BackendTaskQueues.java:1783)
at
org.continuent.sequoia.controller.loadbalancer.BackendWorkerThread.run(BackendWorkerThread.java:182)
08:50:06,690 WARN DatabaseBackend.System_DB.System_DB1 Failed to get
imported keys for table public.seq_document_sec_settings
org.postgresql.util.PSQLException: ERROR: current transaction is aborted,
commands ignored until end of transaction block
at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1471)
at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1256)
at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:175)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:389)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:314)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:221)
at
org.postgresql.jdbc2.AbstractJdbc2DatabaseMetaData.getImportedExportedKeys(AbstractJdbc2DatabaseMetaData.java:3237)
at
org.postgresql.jdbc2.AbstractJdbc2DatabaseMetaData.getImportedKeys(AbstractJdbc2DatabaseMetaData.java:3533)
at
org.continuent.sequoia.controller.backend.DatabaseSQLMetaData.getImportedKeys(DatabaseSQLMetaData.java:757)
at
org.continuent.sequoia.controller.backend.DatabaseSQLMetaData.createDatabaseSchema(DatabaseSQLMetaData.java:181)
at
org.continuent.sequoia.controller.backend.DatabaseBackendMetaData.createDatabaseSchemaDynamically(DatabaseBackendMetaData.java:918)
at
org.continuent.sequoia.controller.backend.DatabaseBackendMetaData.getDatabaseSchema(DatabaseBackendMetaData.java:954)
at
org.continuent.sequoia.controller.backend.DatabaseBackend.checkDatabaseSchema(DatabaseBackend.java:1798)
at
org.continuent.sequoia.controller.backend.DatabaseBackend.refreshSchema(DatabaseBackend.java:2111)
at
org.continuent.sequoia.controller.backend.DatabaseBackend.getDatabaseSchema(DatabaseBackend.java:1914)
at
org.continuent.sequoia.controller.loadbalancer.BackendTaskQueues.fetchNextQueryFromBackendTotalOrderQueue(BackendTaskQueues.java:785)
at
org.continuent.sequoia.controller.loadbalancer.BackendTaskQueues.getNextCommitRollbackToExecute(BackendTaskQueues.java:1783)
at
org.continuent.sequoia.controller.loadbalancer.BackendWorkerThread.run(BackendWorkerThread.java:182)
08:50:06,693 WARN DatabaseBackend.System_DB.System_DB1 Unable to gather
schema from database meta data: java.sql.SQLException: Failed to get
information about database schema: java.sql.SQLException: Unable to fetch
columns for table public.seq_document_sec_settings
08:50:06,712 WARN DatabaseBackend.System_DB.System_DB1 Failed to get
exported keys for table public.seq_document_sec_settings
org.postgresql.util.PSQLException: ERROR: current transaction is aborted,
commands ignored until end of transaction block
at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1471)
at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1256)
at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:175)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:389)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:314)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:221)
at
org.postgresql.jdbc2.AbstractJdbc2DatabaseMetaData.getImportedExportedKeys(AbstractJdbc2DatabaseMetaData.java:3237)
at
org.postgresql.jdbc2.AbstractJdbc2DatabaseMetaData.getExportedKeys(AbstractJdbc2DatabaseMetaData.java:3591)
at
org.continuent.sequoia.controller.backend.DatabaseSQLMetaData.getExportedKeys(DatabaseSQLMetaData.java:697)
at
org.continuent.sequoia.controller.backend.DatabaseSQLMetaData.createDatabaseSchema(DatabaseSQLMetaData.java:180)
at
org.continuent.sequoia.controller.backend.DatabaseBackendMetaData.createDatabaseSchemaDynamically(DatabaseBackendMetaData.java:918)
at
org.continuent.sequoia.controller.backend.DatabaseBackendMetaData.getDatabaseSchema(DatabaseBackendMetaData.java:954)
at
org.continuent.sequoia.controller.backend.DatabaseBackend.checkDatabaseSchema(DatabaseBackend.java:1798)
at
org.continuent.sequoia.controller.backend.DatabaseBackend.refreshSchema(DatabaseBackend.java:2111)
at
org.continuent.sequoia.controller.backend.DatabaseBackend.getDatabaseSchema(DatabaseBackend.java:1914)
at
org.continuent.sequoia.controller.loadbalancer.BackendTaskQueues.fetchNextQueryFromBackendTotalOrderQueue(BackendTaskQueues.java:785)
at
org.continuent.sequoia.controller.loadbalancer.BackendTaskQueues.getNextEntryToExecute(BackendTaskQueues.java:1693)
at
org.continuent.sequoia.controller.loadbalancer.BackendWorkerThread.run(BackendWorkerThread.java:185)
08:50:06,714 WARN DatabaseBackend.System_DB.System_DB1 Failed to get
imported keys for table public.seq_document_sec_settings
org.postgresql.util.PSQLException: ERROR: current transaction is aborted,
commands ignored until end of transaction block
at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1471)
at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1256)
at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:175)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:389)
at
------------------------------------------------------------------------------------------------------
Thanks for your help.
Mylein Blanca Uy
Condensed Matter Physics Laboratory
National Institute of Physics
University of the Philippines, Diliman
Quezon City, 1101, Philippines
----- Original Message ----
From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
To: [email protected]
Sent: Thursday, 25 October, 2007 9:20:05 PM
Subject: Sequoia Digest, Vol 26, Issue 38
Send Sequoia mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://forge.continuent.org/mailman/listinfo/sequoia
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Sequoia digest..."
Today's Topics:
1. Future of Sequoia project -- toward a more community-oriented
project (Robert Hodges)
2. Re: Re: Error with Write Request: (ERROR: could not determine
data type of parameter $5) (Emmanuel Cecchet)
3. Re: Future of Sequoia project -- toward a more
community-oriented project (Emmanuel Cecchet)
4. Re: cannot gather schema from backends(RAID2 with two MS SQL
SERVER backends ) (Emmanuel Cecchet)
5. Re: Future of Sequoia project -- toward a more
community-oriented project (Robert Hodges)
----------------------------------------------------------------------
Message: 1
Date: Wed, 24 Oct 2007 21:11:39 -0700
From: Robert Hodges <[EMAIL PROTECTED]>
Subject: [Sequoia] Future of Sequoia project -- toward a more
community-oriented project
To: Sequoia general mailing list <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
Hi everyone,
As many members of this list are aware, Continuent
(www.continuent.com) has maintained Sequoia and related projects for
some years now. We have made most of the recent changes in the
code. Current infrastructure like CVS, wiki pages, JIRA, email
lists, etc. are maintained on our hosts, which are currently hosted
in New York City at a location that offers very good network access
from both the US and Europe. We build and market commercial
software that is built on Sequoia, so this effort has benefited us at
the same time that it helped supply software to the open source
community.
As a number of you have no doubt noticed, we have been focussing more
on commercial products built on Sequoia and hence much less involved
on the open source side in the last few months. This has led to a
drop in activity on the code and, I think, made the project less
interesting to existing and new project members. There are fewer
members participating on the mailing lists and fewer bugs being
fixed. This concerns me and I hope other people because the Sequoia
project has been very popular in the past and the software serves a
useful purpose. It has been downloaded many tens of thousands of
times, which is not bad considering its specialized nature.
It would therefore be beneficial to have a discussion about how to
create a more vigorous community that serves the needs of everyone
who would like to use Sequoia. To start this discussion, I would
like to describe our own plans, some of which will directly impact
our involvement in Sequoia and its related projects.
1.) Product direction. We are actively working on a set of products
that will initially extend our current commercial uni/cluster
products but will eventually replace them. The Myosotis product
represents a part of that strategy. You'll notice it is licensed
under GPL. It is our intention to license the new products under
GPL using the MySQL model--you can use it for open source stuff but
if you want to get out of the GPL terms you buy a license. It's a
common business model that helps make house payments.
2.) Sequoia development. We plan to continue adding features and
bug fixes to Sequoia because they are required to fix our commercial
products. However, as we develop the new products it's very hard to
play the same role we have had previously, which was essentially to
do most of the development and open source support. In addition to
the question of resources, it's a matter of focus. You can't do
multiple things at once and do them right.
So at this point a couple of things could happen. One is that as
our support decreases someone could decide to fork the codeline and
create a version that is more attuned to the needs of open source
users. The code is licensed under Apache, so as long as you don't
change the license terms anyone can do this. However, an
alternative path, and I think a better one for everyone, would be to
figure out how to make the Sequoia project more community-oriented as
opposed to having it essentially owned by a single company,
Continuent. My model for this is the PostgreSQL project, which is
exceedingly active but owned by nobody.
I would like to toss out a few suggestions from the Continuent side.
We have made a number of improvements to the code, such as developing
a large suite of tests, that represent considerable extensions to the
current code that is released in open source. We would be open to
donating these over a period of time to the community so that it
would be possible for a group of interested persons (including us) to
maintain the code and move it forward in directions that benefit all
members. We also host the codelines and other infrastructure and
are happy to continue doing that indefinitely. Finally, for people
in Western Europe, we have a number of pieces of spare equipment,
mostly rack mountable Compaq hosts, that we would be willing to
donate to community members to help them step up to roles in
development, testing, and documentation of Sequoia. If you want to
sign up for work in the community and can get to Grenoble, they are
yours. (Limit two per customer, please.)
These are just a few of the ideas from our side. I would like to
know what other people think about these ideas and what we can do
together to move Sequoia forward. Please post your ideas to the
mailing list or feel free to contact me directly. At this point any
idea is fair game.
I look forward to hearing from everyone.
Thanks, Robert
Robert Hodges, CTO, Continuent, Inc.
Email: [EMAIL PROTECTED]
Mobile: +1-510-501-3728 Skype: hodgesrm
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://forge.continuent.org/pipermail/sequoia/attachments/20071024/ae3553da/attachment.html
------------------------------
Message: 2
Date: Thu, 25 Oct 2007 14:26:01 +0200
From: Emmanuel Cecchet <[EMAIL PROTECTED]>
Subject: Re: [Sequoia] Re: Error with Write Request: (ERROR: could not
determine data type of parameter $5)
To: Sequoia general mailing list <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi Mylein,
> I am actually using the java app directly with postgres and it is
> working fine. The only thing that i am considering is that, we are
> using postgres driver build 400 before, while with sequoia we are
> using build 407.
> Can we use 400 with sequoia?
Sure, they should not be any issue using this build with Sequoia.
Did you try your java app directly with build 407 to see if it works?
Keep us posted with your findings,
Emmanuel
------------------------------
Message: 3
Date: Thu, 25 Oct 2007 14:30:31 +0200
From: Emmanuel Cecchet <[EMAIL PROTECTED]>
Subject: Re: [Sequoia] Future of Sequoia project -- toward a more
community-oriented project
To: Sequoia general mailing list <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi Robert,
> 1.) Product direction. We are actively working on a set of products
> that will initially extend our current commercial uni/cluster
products
> but will eventually replace them. The Myosotis product represents a
> part of that strategy. You'll notice it is licensed under GPL. It
> is our intention to license the new products under GPL using the
MySQL
> model--you can use it for open source stuff but if you want to get
out
> of the GPL terms you buy a license. It's a common business model
that
> helps make house payments.
Does that also mean that new additions to the Sequoia code base will be
contributed under a GPL license? The whole Sequoia package would then
become APL/GPL dual-licensed?
Would that also mean that contributors will have to give up their
copyright to Continuent (like it is the case for MySQL) for their
contributions so that Continuent could dual-license GPL/commercial its
products?
Thanks for the clarification,
Emmanuel
--
Emmanuel Cecchet - Research scientist
EPFL - LABOS/DSLAB - IN.N 317
Phone: +41-21-693-7558
------------------------------
Message: 4
Date: Thu, 25 Oct 2007 14:47:54 +0200
From: Emmanuel Cecchet <[EMAIL PROTECTED]>
Subject: Re: [Sequoia] cannot gather schema from backends(RAID2 with
two MS SQL SERVER backends )
To: Sequoia general mailing list <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=GB2312
Hi David,
Which driver are you using? Which version?
Did you try with FreeTDS?
> I configured sequoia controller with two MS SQL SERVER 2000
> backends,implementing RAID2 .
> When i force enable the two backends,the controller cannot gather
> schema,and when i start sql client,and "show tables",the controller
> output is
> ...
> 2007-10-25 08:59:31,609 ERROR DatabaseBackend.myDB.hq Views are not
> supported by this driver. Getting tables only.
> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for
> JDBC]Can't start a cloned connection while in manual transaction
mode.
> at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown
Source)
> at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown
Source)
> at com.microsoft.jdbc.base.BaseConnection.getImplConnection(Unknown
> Source)
> at com.microsoft.jdbc.base.BaseStatement.setupImplConnection(Unknown
> Source)
> at com.microsoft.jdbc.base.BaseStatement.<init>(Unknown Source)
> at com.microsoft.jdbc.base.BaseConnection.createStatement(Unknown
Source)
> at com.microsoft.jdbc.base.BaseConnection.createStatement(Unknown
Source)
> at com.microsoft.jdbc.base.BaseDatabaseMetaData.getTables(Unknown
Source)
Thanks for your feedback,
Emmanuel
--
Emmanuel Cecchet - Research scientist
EPFL - LABOS/DSLAB - IN.N 317
Phone: +41-21-693-7558
------------------------------
Message: 5
Date: Thu, 25 Oct 2007 06:19:32 -0700
From: Robert Hodges <[EMAIL PROTECTED]>
Subject: Re: [Sequoia] Future of Sequoia project -- toward a more
community-oriented project
To: Sequoia general mailing list <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
Hi Emmanuel,
No, Sequoia is Apache licensed and should remain that way. Our
contributions will continue to use the Apache license.
For new products, yes, we would ask people to give up copyright.
Cheers, Robert
Robert Hodges, CTO, Continuent, Inc.
Email: [EMAIL PROTECTED]
Mobile: +1-510-501-3728 Skype: hodgesrm
On Oct 25, 2007, at 5:30 AM, Emmanuel Cecchet wrote:
> Hi Robert,
>
>> 1.) Product direction. We are actively working on a set of
>> products that will initially extend our current commercial uni/
>> cluster products but will eventually replace them. The Myosotis
>> product represents a part of that strategy. You'll notice it is
>> licensed under GPL. It is our intention to license the new
>> products under GPL using the MySQL model--you can use it for open
>> source stuff but if you want to get out of the GPL terms you buy a
>> license. It's a common business model that helps make house
>> payments.
> Does that also mean that new additions to the Sequoia code base
> will be contributed under a GPL license? The whole Sequoia package
> would then become APL/GPL dual-licensed?
> Would that also mean that contributors will have to give up their
> copyright to Continuent (like it is the case for MySQL) for their
> contributions so that Continuent could dual-license GPL/commercial
> its products?
>
> Thanks for the clarification,
> Emmanuel
>
> --
> Emmanuel Cecchet - Research scientist
> EPFL - LABOS/DSLAB - IN.N 317
> Phone: +41-21-693-7558
>
> _______________________________________________
> Sequoia mailing list
> [email protected]
> https://forge.continuent.org/mailman/listinfo/sequoia
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://forge.continuent.org/pipermail/sequoia/attachments/20071025/7ff36316/attachment.html
------------------------------
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
End of Sequoia Digest, Vol 26, Issue 38
***************************************
Sick of deleting your inbox? Yahoo!7 Mail has free unlimited storage.
http://au.docs.yahoo.com/mail/unlimitedstorage.html
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
