Coldfusion 5.0 - Fatal error codes requested!

[f.nijenhuis]

Since some time we have serious problems with our virtual hosting environment
and coldfusion. Some of our customers are going away due to the problems. It
seems that 'out of the blue' problems started with our cf5.0/debian linux
server, which ran in the past without problems. We are now reinstalling a new
server, to migrate some of the customers to see where the problems are coming
from. As I understand the errors
''Fatal','11275','08/24/04','09:46:41',,'Caught a fatal signal (11) -
Aborting'' mostly are related to out-of-date external odbc drivers,
programming problems (cflock, variables) or the jre engine (version 1.3). The
second part of the log shows some kind of ID, and I'm trying to find out what
it tells us. It looks to me that Macromedia should be able to tell us some
more about that second field which might help us to pinpoint the different
types of problems. Till now we were not able to pinpoint the time of the fatal
signals to specific templates. Our log since 24th of april shows us: 171
'8200' 144 '9225' 82 '10250' 71 '11275' 38 '12300' 21
'7175' 2 '6150' 1 '4100' 1 '1024' Where the first field is
the number of occurences, the second the 'id' field of the log line. Is there
someone out there who could tell us something about the first 5 id's so we can
try to solve them??? thx Frank

[Tom Jordahl]

These are thread IDs and are only used to correlate messages from the same
thread.

They are not error codes.

--
Tom Jordahl
Macromedia Server Development

[f.nijenhuis]

mmm,ok, but why are the same thread codes always used, and why are some thread
id's mentioned more often than others.
Is it possible to trace running thread id's to coldfusion
application/templates?

It's quit impossible to track down the problem on a virtual hosting
environmnet. We tried over and over to match the timing of the fatal signal
with the accesslogs with no result.

Frank