Re: [Fwd: Re: [Fwd: Re: Transaction related error in log when the]]

2007-12-12 Thread Jacques Le Roux
o pass it along) is that > >> they should wrap their minilang find in a transaction and not use a > >> transaction for the get inventory service. This service doesn't > >> actually store data and wrapping a transaction uses resources > >> unnecessarily and c

Re: [Fwd: Re: [Fwd: Re: Transaction related error in log when the]]

2007-12-12 Thread David E Jones
lly need to communicate with Si thru you? That is funny. Jacopo Walter Vaughan wrote: Original Message Subject: Re: [Fwd: Re: Transaction related error in log when the] Date: Wed, 12 Dec 2007 08:03:42 -0800 From: Si Chen <[EMAIL PROTECTED]> Reply-To:

Re: [Fwd: Re: [Fwd: Re: Transaction related error in log when the]]

2007-12-12 Thread Jacopo Cappellato
Walter, thanks very much for the communication effort but... do we really need to communicate with Si thru you? That is funny. Jacopo Walter Vaughan wrote: Original Message Subject: Re: [Fwd: Re: Transaction related error in log when the] Date: Wed, 12 Dec 2007 08

[Fwd: Re: [Fwd: Re: Transaction related error in log when the]]

2007-12-12 Thread Walter Vaughan
Original Message Subject:Re: [Fwd: Re: Transaction related error in log when the] Date: Wed, 12 Dec 2007 08:03:42 -0800 From: Si Chen <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] Organization: Open Source Strategies, Inc. To: Walter Vaughan &

Re: Transaction related error in log when the

2007-12-11 Thread Jonathon -- Improov
Hi Jacopo, Just chiming in. David is absolutely right. Transactions are always needed. For database reads, transactions are needed to prevent dirty reads, for example. It should be obvious why update, delete, insert need transactions. The use-transaction=false should only be off when the ser

Re: Transaction related error in log when the

2007-12-11 Thread Jacopo Cappellato
Of course, I'd love too to get Si's opinion... but I have the feeling he doesn't like to participate in ML discussions. In the last months I don't remember a message from Si, apart from the comments on Jira and the commit logs. Hopefully he will find a moment to jump in this discussion, if not

Re: Transaction related error in log when the

2007-12-11 Thread David E Jones
It would be good to hear Si's comment on that, but my vote is definitely for removing it. A service should only really have use-transaction set to false if it is doing it's own transaction management internally, like manually or in sub-services only. -David On Dec 11, 2007, at 11:00 A

Re: Transaction related error in log when the

2007-12-11 Thread Jacopo Cappellato
David, thanks for the explanation. So I guess that it is ok to remove the use-transaction="false" for these services, right? Jacopo David E Jones wrote: This is an important error message. The problem is that the Entity Engine can't just create a transaction for these because it can't com

Re: Transaction related error in log when the

2007-12-11 Thread David E Jones
This is an important error message. The problem is that the Entity Engine can't just create a transaction for these because it can't commit or rollback the transaction because the connection and ResultSet stay open until the EntityListIterator is closed, which is done by the code calling

Transaction related error in log when the

2007-12-11 Thread Jacopo Cappellato
The following error is logged (even if the service works as expected) when the service "getInventoryAvailableByFacility" is called: == 2007-12-11 15:54:57,906 (default-invoker-Thread-6) [ GenericDelegator.java:2031:ERROR]