ansaurus

Question

Concurrency problem using spring, dbcp and postgres

Answer 1

A:

timestamp out of range: "20120100-09-26 00:00:00.000000 -04:00:00"

You're working in the year 20120100 ? (twenty million) Are you sure? The maximum year for a timestamp is 294276, but I'm pretty sure your input isn't correct.

This has nothing to do with concurrency either, just out of range input.

Frank Heikens 2010-09-08 03:50:49

that's the weird thing. I have a jmeter test that that queries some data using the timestamp. If the number of user are less than 20, then there are no problem. I start increasing the number of user and the problem appears from time to time.

Dani Cricco 2010-09-08 14:00:23

Then the problem might be in JMeter: it's using invalid data, the database has no other option than to reject the query and throw an error.

Frank Heikens 2010-09-08 14:19:41

Answer 2

A:

In your java code do you have non-threadsafe usage of a DateFormat object anywhere? Weird and wonderful date errors often stem from this sort of issue?

private static final DateFormat fmt = new SimpleDateFormat("yyyy-MM-dd HH:mm:ss.SSS");

becomes

private static final ThreadLocal<DateFormat> fmt = new ThreadLocal<DateFormat>() {
    @Override
    protected DateFormat initialValue() {
        return new SimpleDateFormat("yyyy-MM-dd HH:mm:ss.SSS");
    }
}

See DateFormat, ThreadLocal

Jon Freedman 2010-09-08 08:18:19

tks for the answer. The code runs inside inside a method and it only use variables declared in the method.

Dani Cricco 2010-09-08 14:25:14

Take a look at p7spy - http://www.p6spy.com/ - you can set it up as a proxy JDBC driver to log all statements running against the db - should help you pinpoint the exact query that's causing the problem, and potentially find where the statements called from.

Jon Freedman 2010-09-08 17:51:16

ansaurus

tags:

views:

answers:

Concurrency problem using spring, dbcp and postgres

related questions