For some reason, even though this is happening immediately when the call
occurs, changing the timeout fixes it.
Crazy!
On 1/10/18, 5:05 PM, "Ken Anderson" wrote:
All,
We’re running into an issue where our connection to SQL Server is being
lost at the moment we try to execute a stored
All,
We’re running into an issue where our connection to SQL Server is being lost at
the moment we try to execute a stored procedure. We’re unfortunately still
using 4.0M3 if that matters… Any ideas?
Ken
java.sql.SQLException: I/O Error: Read timed out
at
net.sourceforge.jtd
> Le 10 janv. 2018 à 11:16, John Huss a écrit :
>
> Hard to say.
>
> Is the shared cache enabled?
I’m using the default settings.
> Is it sized big enough?
To hold everything? I don’t think so (+470 000 rows from FileMaker).
>
> Is the app under memory pressure when this is happening, o
Hard to say.
Is the shared cache enabled? Is it sized big enough?
Is the app under memory pressure when this is happening, or is it happening
all the time?
On Wed, Jan 10, 2018 at 6:35 AM Pascal Robert wrote:
> Hi,
>
> I’m trying to find out why it takes between 200 and 500 ms to convert an
>
Hi,
I’m trying to find out why it takes between 200 and 500 ms to convert an entity
coming from FileMaker and commit the « new » entity to MySQL. Found out that
every time I access a property of the fetched object, Cayenne does a SELECT
query. Example:
try(ResultBatchIterator batch =
Objec