Console error when using FMP Server

[John A]

Hi,

I have a ScriptMaster function that acts differently when running locally vs. running against our server.

Scenario: Same exact database, one local and one on the server (obviously, FMP 11 local client has the plugin).

When I run my script against the local database it works great, completing in 20 seconds or so.

When I run my script against the remote database it takes about 10 minutes and hangs until this error spits to console (same exact plugin, just one on a locally opened DB and the other test on the same DB opened from FMP Server Advanced)

11/8/11 12:33:49 PM FileMaker Pro[9492] *** __NSAutoreleaseNoPool(): Object 0x3acc24f0 of class NSCFArray autoreleased with no pool in place - just leaking

11/8/11 12:33:49 PM FileMaker Pro[9492] *** __NSAutoreleaseNoPool(): Object 0x3ac12f20 of class NSCFArray autoreleased with no pool in place - just leaking

11/8/11 12:33:49 PM FileMaker Pro[9492] *** __NSAutoreleaseNoPool(): Object 0x3aceaec0 of class FMDocWindowCocoa autoreleased with no pool in place - just leaking

Once this error pops the script completes properly.

I am going to do some line by line debugging and see specifically what line its hanging on before this explodes but the only other examples of this error in the forums resulted in a bugfix to scriptmaster so I wanted to parallel post and see if this made sense to anyone.

Tx

John-

[John A]

Ok more context after some more investigation

1) This memory issue happens on both LOCAL and REMOTE. I was misreading the console.

2) REMOTE is slow. Where local takes 15 seconds remote takes over 5 minutes

3) The slowness and the memory leak errors are in the same line of code

I have narrowed it down to these lines, specifically the executeSql command (added updateSql for reference purposes)

String updateSql = "update customer set billingcircleid = " + response.getResponseData();

fmpro.executeSql(updateSql);

That executeSql command with the sql above throws those memory errors.

response.getResponseData() is a string (but a string as a number). The sql updates properly.

Anyone have ideas? This is a bummer :(

[John A]

Slowness Solved. Memory error is still there but its more performant now.

Tip for everyone

DONT FORGET THE WHERE CLAUSE.

Yes, it turns out updating thousands of records remotely is slow.

Sigh. Anyhow, any tips on the memory issue would be great.