> Chris, > This sounds like some major progress! Meh. It was some work for me, mainly making the vm crash at will and getting JOTM to enlist/recover the resource managers. Things worked out of the box from the side of neo.
> IMHO you should start a branch > in the SVN so others can look at the code. That would be the ideal way, yes. Would you set up a laboratory space for me? > Having the compatibility > tests is great - there are other breaking test that Mattias and Johan > are using to purposely break recovery on both the normal server and HA > setups. They are run on a number of amazon instances and it would be > great if your tests could be integrated and run there, too, so we can > find failing recovery scenarios. I assume you are referring to qa/recovery-robustness. I haven't studied its mechanics yet but I could put it there, I suppose. From a cursory look I understood that it runs from a script so my tests could fit there. > any suggestions on making the use of external TX managers easier or > document the setup process somewhere? For my part I could post an article on my blag(TM) on how I have setup JOTM as a Neo service and how to enable it. I would prefer to do that however after the code has been seen from eyeballs other than mine and actually certified not to be a big, fat, slobbering mess. This way the API will be standardized and people will have something concrete to read about. cheers, CG _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
