Thanks Eric
-Laura
On 11/30/11 9:27 AM, Eric Dalquist wrote:
I think this is a 4.0.2 specific bug. We tried adding in a DB based
distributed locking system and it appears that the cross-db testing I
did missed this error. For doing basic testing and setup you can
ignore the message. The exception is coming from a background process
that purges old event data from the database. This will be fixed in
4.0.3 which will be released at the end of December.
-Eric
On 11/30/11 7:06 AM, Laura McCord wrote:
I had been testing out version 4.0.0 with the 8.2-507.jdbc3 driver
and everything worked but my postgres server version is 8.1.11
<!-- The JDBC Driver used by uPortal -->
<jdbc.groupId>postgresql</jdbc.groupId>
<jdbc.artifactId>postgresql</jdbc.artifactId>
<jdbc.version>8.2-507.jdbc3</jdbc.version>
<dependency>
<groupId>postgresql</groupId>
<artifactId>postgresql</artifactId>
<version>8.2-507.jdbc3</version>
</dependency>
Laura
On 11/30/11 2:25 AM, tomit wrote:
Could you please tell me, which version of uPortal are you using
with the
8.2-507.jdbc3 PostgreSQL driver?
--
View this message in context:
http://jasig.275507.n4.nabble.com/uPortal-4-0-2-PostgreSQL-and-MySQL-problems-tp4119513p4122201.html
Sent from the uPortal Developers mailing list archive at Nabble.com.
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
