Hi Jacques,
thanks for your hints. I suggest the order creation is done by a service? I
saw in the duplicate order data record is the the intital id mentioned. But
I have the postgres also under suspicion. Currently we can´t change to
Postgres 8.1 because the database is maintained by an other supplier. We
uses the postgresql-8.0-311.jdbc3.jar with PostgreSQL 7.4.13.
best Regards
Sebastian
--On Montag, 30. Oktober 2006 20:59 +0100 Jacques Le Roux
<[EMAIL PROTECTED]> wrote:
Sebastian
You can set the transaction timeout in different places:
- as an attribute of screen definition : this sets the timeout of the
screen's transaction - as an attribute of a service definition : this
sets the timeout of the service
First of all I'd try with the latter...
Also BTW I read that there was some problems with pre PostGres 8.0 JDBC
drivers. I'd try to move to PostGres 8.1
Jacques
--On Montag, 30. Oktober 2006 19:09 +0100 Jacques Le Roux
<[EMAIL PROTECTED]> wrote:
> Not a problem of time out too short for transactions ?
Hi,
where to adjust? The system is working on a postges 7.4.3
best regards
Sebastian
/**
* Sebastian Schirmer
* ZYRES digital media systems GmbH
* Eschersheimer Landstr. 5-7
* 60322 Frankfurt am Main
*
* Phone +49 (0)69 98 55 99 - 0 | Fax +49 (0)69 98 55 99 - 11
* http://www.zyres.com/
*
*/
/**
* Sebastian Schirmer
* ZYRES digital media systems GmbH
* Eschersheimer Landstr. 5-7
* 60322 Frankfurt am Main
*
* Phone +49 (0)69 98 55 99 - 0 | Fax +49 (0)69 98 55 99 - 11
* http://www.zyres.com/
*
*/
