Timeline for Transaction (Process ID 126) was deadlocked on lock resources with another process
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 20, 2017 at 16:17 | answer | added | Manas.p | timeline score: 0 | |
| Oct 20, 2017 at 3:14 | history | tweeted | twitter.com/StackTridion/status/921213100111605760 | ||
| Oct 19, 2017 at 8:10 | comment | added | Bart Koopman | A deadlock is a database issue, so that is the system you should focus on. What could be important here is the exact setup of the deployer (or multiple deployers) and also if the database is properly maintained. I suggest you edit your question and supply a few more relevant details around all this. | |
| Oct 19, 2017 at 4:26 | answer | added | Hiren Kaku | timeline score: 2 | |
| Oct 19, 2017 at 2:22 | history | edited | Manas.p | CC BY-SA 3.0 |
edited body
|
| Oct 19, 2017 at 2:22 | comment | added | Manas.p | @Hiren : It is the same. Except the live discovery service is configured with 2 deployers using mirror strategy. | |
| Oct 18, 2017 at 22:47 | comment | added | Hiren Kaku | Are you using same configuration for live? Are you performing bulk publish or phased publish? | |
| Oct 18, 2017 at 18:42 | history | asked | Manas.p | CC BY-SA 3.0 |