Running UDS 5.2 on Windows, SQL Server.
We have found that occassionally we have Forte/UDS replicants that are failing (often due to a database deadlock) and the replcants are not auto-restarting.
We are unable to determine why these replicants do not automatically restart and we are hoping someone could shed some light on this.
All help appreciated.
Hi, Chris --
I know this is grasping at straws, but your thing might be related somehow...
Fixed in UDS 5.1.3:
Bug 4638138 - Replicated partitions don't start reliably
Fixed in UDS 5.2.0:
Bug 4987133 - Security scan can disable load balanced partitions
Bug 4990180 - Security scan can disable UDS web acess partition port
KenG.
Hi,
We are having the same problem with UDS 5.0.9 where we had a component partition that intermittently crashed for a still unknown reason. One of the solutions Sun Support give us was to turn on the auto restart option for the partition so using the following escript commands:
escript > findsubag lr_agreementtransactionmanager_cl0
escript > shutdown
escript > uninstall
escript > loaddistrib lr_agreementtransactionmanager cl0
escript > lockenv
escript > enableappcomp LiberatorServer1 LR_AgreementTransactionManager_cl0_Part7
escript > commit
escript > startup
The partition however did NOT restart when it crashed again. Is this the way you guys enabled the auto restart for your components (ie is there something I have missed?) or is this as KenG suggests a UDS issue/bug?
Thanks for your help,
Stephen.
