Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of gary.tully@gmail.com
 designates 209.85.216.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1328722350877-4370212.post@n4.nabble.com>
References: <1328722350877-4370212.post@n4.nabble.com>
Date: Thu, 9 Feb 2012 11:46:24 +0000
Message-ID: 
 <CAH+vQmNyonbByzQdORjEr_3pp9V_xELgOQ9Fs5svAnoBnh_jwA@mail.gmail.com>
Subject: Re: Supressing PostgreSQL exceptions for creating tables when tables
 already exist
From: Gary Tully <gary.tully@gmail.com>
To: dev@activemq.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

there is a boolean attribute createTablesOnStartup on the
jdbcpersistenceadapter, you could set that to false on subsequent
starts once  the tables are created.

On 8 February 2012 17:32, io42 <ingrid.olson@desknetinc.com> wrote:
> I have a postgres data store working that persists ActiveMQ messages, but
> every time that I run my system (which starts up an embedded broker) I ge=
t a
> lot of long exception messages asserting that my JDBC tables could not be
> created because they could already exist. =A0Is there any way to suppress
> these exception details from showing up in the logging? =A0This issue alr=
eady
> appears to have been previously identified
> (https://issues.apache.org/jira/browse/AMQ-3189), but I have yet to disco=
ver
> if anyone has come up with a solution or workaround. =A0Below is some of =
the
> sample output I keeps seeing.
>
>
> Example output:
>
> 08 Feb 2012 11:22:13 - Could not create JDBC tables; they could already
> exist. Failure was: CREATE TABLE ACTIVEMQ_MSGS(ID BIGINT NOT NULL, CONTAI=
NER
> VARCHAR(250), MSGID_PROD VARCHAR(250), MSGID_SEQ BIGINT, EXPIRATION BIGIN=
T,
> MSG BYTEA, PRIMARY KEY ( ID ) ) Message: ERROR: relation "activemq_msgs"
> already exists SQLState: 42P07 Vendor code: 0
> 08 Feb 2012 11:22:13 - Failure details: ERROR: relation "activemq_msgs"
> already exists
> org.postgresql.util.PSQLException: ERROR: relation "activemq_msgs" alread=
y
> exists
> 08 Feb 2012 11:22:13 - Failure details: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> org.postgresql.util.PSQLException: ERROR: current transaction is aborted,
> commands ignored until end of transaction block
> =A0 =A0 =A0 =A0at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecut=
orImpl.java:2102)
> =A0 =A0 =A0 =A0at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl=
.java:1835)
> =A0 =A0 =A0 =A0at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:2=
57)
> =A0 =A0 =A0 =A0at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statemen=
t.java:500)
> =A0 =A0 =A0 =A0at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc=
2Statement.java:374)
> =A0 =A0 =A0 =A0at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statemen=
t.java:366)
> =A0 =A0 =A0 =A0at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Met=
hod)
> =A0 =A0 =A0 =A0at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Sou=
rce)
> =A0 =A0 =A0 =A0at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown=
 Source)
> =A0 =A0 =A0 =A0at java.lang.reflect.Method.invoke(Unknown Source)
> =A0 =A0 =A0 =A0at
> org.postgresql.ds.jdbc23.AbstractJdbc23PooledConnection$StatementHandler.=
invoke(AbstractJdbc23PooledConnection.java:455)
> .
> .
> .
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Supre=
ssing-PostgreSQL-exceptions-for-creating-tables-when-tables-already-exist-t=
p4370212p4370212.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.


--=20
http://fusesource.com
http://blog.garytully.com