What are the implications of restarting the Jazz server?

For the most part it shouldn't be a problem. If the UI was running
paginated queries or if you were uploading lots of content (doing a
large SCM share, for example) you may have see some hiccups but the
state of the system is maintained through transactions which should
either clearly succeed or fail. If not, that is a bug!

Why are you restarting the server so often?

JohnC
SCM Server

Aaron Cohen wrote:

I have restarted our server more than I would like and my eclipe client
was able to continue plugging away without any problems after the
restart. So my question is what components are affected by a server
being cycled? Beyond the time it takes for the server to restart, how
much time is lost? Is there any expected data loss? I believe the answer
to this question will be worthwhile for an Admin to know what the
implecations of restarting a Jazz Server are.

Thanks!

John Camelon wrote:

For the most part it shouldn't be a problem. If the UI was running
paginated queries or if you were uploading lots of content (doing a
large SCM share, for example) you may have see some hiccups but the
state of the system is maintained through transactions which should
either clearly succeed or fail. If not, that is a bug!

Why are you restarting the server so often?

JohnC
SCM Server

Aaron Cohen wrote:
I have restarted our server more than I would like and my eclipe
client was able to continue plugging away without any problems after
the restart. So my question is what components are affected by a
server being cycled? Beyond the time it takes for the server to
restart, how much time is lost? Is there any expected data loss? I
believe the answer to this question will be worthwhile for an Admin to
know what the implecations of restarting a Jazz Server are.

Thanks!
John,

Thanks for the information. The reason I was restarting the server was
more of a WAS issue than Jazz issue. If I am reading your response
correctly, As long as the users are not uploading content or running a
transaction, they should be fine.

Hi Aaron,

What I mean is that service requests that were running when you disabled
the app server likely failed the transaction, which is not big deal ...
the client should be able to recover the same way that they would if the
network connection was lost : when the server comes back online the
clients should be able to retry (if applicable) or refresh and retry
depending on the specific scenario.

The server caches will repopulate as requests get processed and within
an hour (by default if you did not change the setting in the admin web
ui) stray content will get cleaned up if an owner has not been found for
it. After this content garbage collection is done, the system is
completely healed.

HTH,
JohnC

Aaron Cohen wrote:

John Camelon wrote:
For the most part it shouldn't be a problem. If the UI was running
paginated queries or if you were uploading lots of content (doing a
large SCM share, for example) you may have see some hiccups but the
state of the system is maintained through transactions which should
either clearly succeed or fail. If not, that is a bug!

Why are you restarting the server so often?

JohnC
SCM Server

Aaron Cohen wrote:
I have restarted our server more than I would like and my eclipe
client was able to continue plugging away without any problems after
the restart. So my question is what components are affected by a
server being cycled? Beyond the time it takes for the server to
restart, how much time is lost? Is there any expected data loss? I
believe the answer to this question will be worthwhile for an Admin
to know what the implecations of restarting a Jazz Server are.

Thanks!
John,

Thanks for the information. The reason I was restarting the server was
more of a WAS issue than Jazz issue. If I am reading your response
correctly, As long as the users are not uploading content or running a
transaction, they should be fine.