https://connect.hyland.com/t5/alfresco-archive/replication-problem-auto-node-generation-on-client-boot/m-p/161293#M115227 <HTML><HEAD></HEAD><BODY><SPAN>Immediate problem resolved:</SPAN><BR /><BR /><A href="http://issues.alfresco.com/browse/AR-2017" rel="nofollow noopener noreferrer">http://issues.alfresco.com/browse/AR-2017</A><SPAN> details the bug involving workflow happening even in a read-only system. I've made the same modification to WorkflowInterpreter.onBootstrap() that exists in the HEAD to only do the operation if read-only is set to false, and also to comment out the line "interpretCommand("var bpm<img id="smileytongue" class="emoticon emoticon-smileytongue" src="https://connect.hyland.com/i/smilies/16x16_smiley-tongue.png" alt="Smiley Tongue" title="Smiley Tongue" />ackage package 1");"</SPAN><BR /><BR /><SPAN>Those changes have stopped the automatic creation of nodes on system startup.</SPAN><BR /><BR /><BR /><SPAN>A larger problem with Alfresco replication remains and is detailed here: </SPAN><A href="http://forums.alfresco.com/viewtopic.php?t=11262" rel="nofollow noopener noreferrer">http://forums.alfresco.com/viewtopic.php?t=11262</A><BR /><BR /><SPAN>John</SPAN></BODY></HTML> Tue, 26 Feb 2008 16:23:45 GMT johnwalsh 2008-02-26T16:23:45Z https://connect.hyland.com/t5/alfresco-archive/replication-problem-auto-node-generation-on-client-boot/m-p/161292#M115226 Greetings,I've got replication working between two systems. When the slave system starts up, it creates new entries in the alf_node table as well as a new bin file in the data/live/contentstore/date directory. That slave-created entry in the alf_node table causes MySQL errors when the next node is c Fri, 22 Feb 2008 13:22:53 GMT https://connect.hyland.com/t5/alfresco-archive/replication-problem-auto-node-generation-on-client-boot/m-p/161292#M115226 johnwalsh 2008-02-22T13:22:53Z https://connect.hyland.com/t5/alfresco-archive/replication-problem-auto-node-generation-on-client-boot/m-p/161293#M115227 <HTML><HEAD></HEAD><BODY><SPAN>Immediate problem resolved:</SPAN><BR /><BR /><A href="http://issues.alfresco.com/browse/AR-2017" rel="nofollow noopener noreferrer">http://issues.alfresco.com/browse/AR-2017</A><SPAN> details the bug involving workflow happening even in a read-only system. I've made the same modification to WorkflowInterpreter.onBootstrap() that exists in the HEAD to only do the operation if read-only is set to false, and also to comment out the line "interpretCommand("var bpm<img id="smileytongue" class="emoticon emoticon-smileytongue" src="https://connect.hyland.com/i/smilies/16x16_smiley-tongue.png" alt="Smiley Tongue" title="Smiley Tongue" />ackage package 1");"</SPAN><BR /><BR /><SPAN>Those changes have stopped the automatic creation of nodes on system startup.</SPAN><BR /><BR /><BR /><SPAN>A larger problem with Alfresco replication remains and is detailed here: </SPAN><A href="http://forums.alfresco.com/viewtopic.php?t=11262" rel="nofollow noopener noreferrer">http://forums.alfresco.com/viewtopic.php?t=11262</A><BR /><BR /><SPAN>John</SPAN></BODY></HTML> Tue, 26 Feb 2008 16:23:45 GMT https://connect.hyland.com/t5/alfresco-archive/replication-problem-auto-node-generation-on-client-boot/m-p/161293#M115227 johnwalsh 2008-02-26T16:23:45Z