We use jBase 3.4.10 on Windows Server 2003.
We seem to suffer reasonably regular (one every couple of months) file
corruptions in a file which is heavily used.
The symptom is that the process (which is invisible in background and
runs in a web service) drops to debugger. This causes partial data
updates and a complete headache to fix. I know that using transactions
will alleviate the problem - but currently we don't use these.
My question is; Is there someway that I can trap the error - rather than
have the process drop to debugger - so that I can take automated action
(shut down the web service!)? Or is there some other way that I can
monitor that the problem has occurred ?
Regards
Simon
=======================================
Simon Verona
Director
Dealer Management Services Ltd
T: 0845 686 2300
========================================
On 02/04/2012 15:40, Robert Beaudry wrote:
Hello,
We have been using Jbase 3 with SAN for a while and an AIX specialist
put the segment size for LUN at 16K because this is the good value for
Oracle or DB2, so he think it must be the good value for Jbase as well.
We didn't realy had performance problem since then but can somebody
confirm that this is also the best size for jBase as well?
And is it the same thing with jBase 5?
Thank's in advance
Robert
--
IMPORTANT: T24/Globus posts are no longer accepted on this forum.
To post, send email to [email protected]
To unsubscribe, send email to [email protected]
For more options, visit this group at
http://groups.google.com/group/jBASE?hl=en
--
IMPORTANT: T24/Globus posts are no longer accepted on this forum.
To post, send email to [email protected]
To unsubscribe, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
