![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: Exceeded retry limit Topic Summary: Created On: 19-Feb-2004 02:46 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: This is one possibility. We have the same once in a while: - Sometimes the jetty server just hangs and everything is fine after the user tries again to log-in. - Sometimes the jetty server 'crashes' because the corresponding database is protected and the csuser sessions can't be established: Then the server can be set to 'disabled' in the configuration file (you can see that in the Admin section of CS)... We ran into that because of the changed behaviour of the ccm backup command in 6.2 leaving the databases protected after the backup (if you did a ccm protect or ccm shutdown at the beginning of your backup...). We usually did a backup without shutting down the jetty servers and restarting them after the backup procedure. We first backup our databases and then shut down and restarted the jetties (to reload the configuration data automatically every night). For every cs instance the first user to log-in after the restart got your error message! Then he had to wait 10 seconds, retry to log-in and everything was fine again... The second user to log-in on the same instance didn't get any errors! We learned that the first user reanimated the csuser processes... Strange... Now the stopping and starting of the jetty servers is part of our backup script (shutting down in the beginning, starting over after the backup) and no more errors of that kind! Regards, Thomas | |
![]() |
|
One of my users was using Change Synergy and of the sudden it gave the following error:
Failed to get a session: Exceeded retry limit Any ideas why? |
|
![]() |
|
![]() |
|
This indicates that you have exceeded your users/sessions limit. You must increase this value on the Admin interface of Change Synergy: Admin -> Server -> Select the database that the user uses -> Increase "Max. sessions" if you have free change synergy licenses not used yet or try to increase "Users/session". Hope help you by that. Lyes GUERROUI |
|
![]() |
|
![]() |
|
This is one possibility.
We have the same once in a while: - Sometimes the jetty server just hangs and everything is fine after the user tries again to log-in. - Sometimes the jetty server 'crashes' because the corresponding database is protected and the csuser sessions can't be established: Then the server can be set to 'disabled' in the configuration file (you can see that in the Admin section of CS)... We ran into that because of the changed behaviour of the ccm backup command in 6.2 leaving the databases protected after the backup (if you did a ccm protect or ccm shutdown at the beginning of your backup...). We usually did a backup without shutting down the jetty servers and restarting them after the backup procedure. We first backup our databases and then shut down and restarted the jetties (to reload the configuration data automatically every night). For every cs instance the first user to log-in after the restart got your error message! Then he had to wait 10 seconds, retry to log-in and everything was fine again... The second user to log-in on the same instance didn't get any errors! We learned that the first user reanimated the csuser processes... Strange... Now the stopping and starting of the jetty servers is part of our backup script (shutting down in the beginning, starting over after the backup) and no more errors of that kind! Regards, Thomas |
|
![]() |
Telelogic SYNERGY
» SYNERGY/Change
»
Exceeded retry limit
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.