Community
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"rryda" <rryda@mgedata.cz>Of
wrote in message
href="news:f17004a.0@WebX.maYIadrTaRb">news:f17004a.0@WebX.maYIadrTaRb...
course my question is: What is right? "Health Restart Enabled" or
"HealthRestartEnabled"?
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"rryda" <rryda@mgedata.cz>Thank
wrote in message
href="news:f17004a.2@WebX.maYIadrTaRb">news:f17004a.2@WebX.maYIadrTaRb...
you, Marion. One more q: is this functionality implemented to version 5?
Richard
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Joakim Rylander" <
href="mailto:jockeryl@hotmail.com">jockeryl@hotmail.com> wrote in
message
href="news:1C925BB85C2D806ED920E2920E49B3BE@in.WebX.maYIadrTaRb">news:1C925BB85C2D806ED920E2920E4......
Hi,
Your question should be, is this bug fixed in the
latest MapGuide? 😉
I mean why have a function to restart a service,
fix the reason why the server has to be restarted in the first
place...
The issue is that only the affected OLEDB
connections to the Oracle should be dropped, not restarting the whole service
and disrupt the service for users accessing other MWFs with SDF files, not
having any problems...
How to promise 99.99% uptime to customers with
this inherited flaw?
Best regards,
Jocke
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"rryda" <rryda@mgedata.cz>Thank
wrote in message
href="news:f17004a.2@WebX.maYIadrTaRb">news:f17004a.2@WebX.maYIadrTaRb...
you, Marion. One more q: is this functionality implemented to version 5?
Richard
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Marion Pietsch" <
href="mailto:discussion.support@autodesk.com">discussion.support@autodesk.com>
wrote in message
href="news:A5DC2F7AF87F197AD7072D9940C2D5C2@in.WebX.maYIadrTaRb">news:A5DC2F7AF87F197AD7072D9940C......
Jocke,
you're talking about the Oracle
hanging issue, right? Yes, that one is fixed in MapGuide
6.3. However, the formerly added registry parameters are still
available and functional.
Marion Pietsch
Autodesk Professional
Services
Infrastructure Solutions
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Joakim Rylander" <
href="mailto:jockeryl@hotmail.com">jockeryl@hotmail.com> wrote in
message
href="news:1C925BB85C2D806ED920E2920E49B3BE@in.WebX.maYIadrTaRb">news:1C925BB85C2D806ED920E2920......
Hi,
Your question should be, is this bug fixed in
the latest MapGuide? 😉
I mean why have a function to restart a
service, fix the reason why the server has to be restarted in the first
place...
The issue is that only the affected OLEDB
connections to the Oracle should be dropped, not restarting the whole
service and disrupt the service for users accessing other MWFs with SDF
files, not having any problems...
How to promise 99.99% uptime to customers with
this inherited flaw?
Best regards,
Jocke
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"rryda" <Thank
href="mailto:rryda@mgedata.cz">rryda@mgedata.cz> wrote in message
href="news:f17004a.2@WebX.maYIadrTaRb">news:f17004a.2@WebX.maYIadrTaRb...
you, Marion. One more q: is this functionality implemented to version 5?
Richard