Machine: jtgb4u2b (SunOS jtgb4u2b 5.6 Generic_105181-20 sun4u sparc SUNW,Ultra-2)
flag: -server -Xcomp
VolanoTest failed after 0 days: 20 hours 16 minutes
Error message:
Unexpected Signal: 11
An error has just occurred, do you want to debug the problem?
There is no core file available

Machine: jtgb4u2d1 (SunOS jtgb4u2d1 5.8 Generic_108528-01 sun4u sparc SUNW,Ultra-60)
flag: -server
VolanoTest failed after 0 days: 4 hours 30 minutes
Error message:
Unexpected Signal: 10
An error has just occurred, do you want to debug the problem?
There is no core file available

june.zhong@eng 2001-01-26

I accidentally removed log files on jtgb4u2b and jtgb4u2d1.
The log files do not contain much helpful informantion anyway.
The only error message from the log file is "An error has just occurred, do you want to debug the problem?"

I reproduced the failure on jtg-s119.
This time it only took 2 hours for the problem to show up.
log files under /local/bigapps/VolanoTestrun.753
server pid: 779
client pid: 1428

It seems the faster the CPU speed, the sooner the failure happens.

jtg-s119 is Ultra60, 360MPZ, the failure happened in about 2 hours. ( flag: -server -Xcomp)
jtgb4u2b is 200MHZ, the failure happened after 20 hours. ( flag: -server -Xcomp)
jtgb4u2d1 is 296MHZ, the failure happened after 4 hours 30 minutes. ( flag: -server)
My own desktop, mooncake is 200MHZ, the failure happened after about 24 hours.
(flag: -server)



june.zhong@eng 2001-01-29