Skip site navigation (1) Skip section navigation (2)

Re: Postgres and Jboss using two postgresql databases

From: Mike Goldner <mgoldner(at)agmednet(dot)com>
To: Håkan Jacobsson <hakan(dot)jacobsson99(at)bredband(dot)net>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Postgres and Jboss using two postgresql databases
Date: 2008-01-02 15:53:38
Message-ID: 1199289218.907.9.camel@mgoldner-desktop (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc
On Wed, 2008-01-02 at 16:15 +0100, Håkan Jacobsson wrote:
> Hi,
> I'm using two postgresql databases (one version 8.0, one 
> version 8.2) with JBoss AS (version 4.2.2.GA).
> We have just migrated to JBoss 4.2.2.GA.
> We get lots of exceptions in the JBoss logfile after 
> migration. Seems there is a problem getting data
> from both databases in the same method (using an EJB3 
> Stateless Session Bean).
> One database call is made via JDBC (through a DataSource 
> object), the next call (to the other database) is done
> via another Stateless Session Bean (throguh the Entity Manager 
> object).
> Earlier (with the older version of JBoss) - this has not been 
> a problem. Searching for an answer I've seen suggestions that 
> the errors might come from the fact that postgresql does not 
> support 'two-phase commit'.
> Any idea what I could do? 8.1 is said to support 'two-phase 
> commit' - I'm not sure how to configure it. Not even sure if 
> this is the source of the problem.
> /Best regards, Håkan Jacobsson
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster

I have a similar situation with 2 datasources.  You should be able to
configure an xa-datasource in JBoss.  

Check out


In response to

pgsql-jdbc by date

Next:From: Håkan JacobssonDate: 2008-01-02 16:25:28
Subject: Ang: Re: Postgres and Jboss using two postgresql databases
Previous:From: Håkan JacobssonDate: 2008-01-02 15:15:22
Subject: Postgres and Jboss using two postgresql databases

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group