Re: What does this interbase.log entry mean?

Are you using any user define functions (UDFs)?

-- 

CLUSTER1 (Server) Wed Apr 25 17:56:55 2007
 
  Floating-point invalid operand.
  An indeterminate error occurred during a
  floating-point operation.
 This exception will cause the InterBase server
 to terminate abnormally.

This is IB2007  on a 4GB ram 2*Xeon dualcore machine with Windows 2003 
Enterprise Server.
Is there something i can do to avoid errors like this? Any hints why this 
happens?


Thanks, Michael





More of this interbase.log:

CLUSTER1 (Server) Wed Apr 25 17:42:37 2007
 INET/inet_error: read errno = 10054 client host = CLUSTER2 connection name 
= cluster1 user name = LABOR server port number = 0

CLUSTER1 (Server) Wed Apr 25 17:56:55 2007
 
  Floating-point invalid operand.
  An indeterminate error occurred during a
  floating-point operation.
 This exception will cause the InterBase server
 to terminate abnormally.

CLUSTER1 (Client) Wed Apr 25 17:56:55 2007
 C:\Programme\Borland\InterBase\bin\ibserver.exe: terminated abnormally (-1)


CLUSTER1 (Server) Wed Apr 25 17:56:57 2007
 SERVER/set_process_affinity: hyper-threading ProcessAffinityMask is 3

CLUSTER1 (Server) Wed Apr 25 17:56:57 2007
 SERVER/set_process_affinity: setting ProcessAffinityMask to 3

CLUSTER1 (Server) Wed Apr 25 17:56:57 2007
 Server: setting SWEEP_QUANTUM to 250, USER_QUANTUM to 1000,
      SWEEP_YIELD_TIME to 1 ms, and MAX_THREADS to 1000000
      SQL_COMPILER_RECURSION to 2000


CLUSTER1 (Client) Wed Apr 25 17:56:58 2007
 Guardian starting: C:\Programme\Borland\InterBase\bin\ibserver.exe

> Are you using any user define functions (UDFs)?

Yes, i am. But i am using them with ib 6020 since some years without any 
problems, so i did not think they could cause this one. Do they have to be 
defined different to work with IB2007?

Michael 

Michael Danninger wrote:

> Yes, i am. But i am using them with ib 6020 since some years without
> any problems, so i did not think they could cause this one.

	Sure they can. IB 7+ is *much* more aggressively multithreaded.
Particularly on a SMP or hyper-threading processor, you're practically
guaranteed to see any concurrency bugs your UDFs might have, whereas in
6.x and earlier you could often get away with it.

-- 
Craig Stuntz [TeamB] · Vertex Systems Corp. · Columbus, OH
  Delphi/InterBase Weblog : http://blogs.teamb.com/craigstuntz
Want to help make Delphi and InterBase better?  Use QC!

Michael Danninger wrote:

> Do they have to be defined different to work with IB2007?

IB 7 and later are multi-threaded and multi-threading will be used a
lot on multi-processor hardware. That means that you can expect any UDF
that is not thread safe to suddenly fail.

--