We currently have a few sites load balanced via Distributed Calling. One particular site uses Contour Code First. When both Distributed Calling and the Contour Code First HttpModule are enabled, the site refuses to start and hangs. When one is disabled and the other enabled, the site starts.
Has anyone experienced the same issue and does anyone know if the two are compatible with each other? Our Umbraco version is 4.11.8 and the Contour version is 3.0.13.
Within the Umbraco log table, the last log message we find is "Submitting calls to distributed servers". The last log message we see in the log files is "Completed resolution of types of umbraco.interfaces.ICacheRefresher, found 6 (took 11ms)".
We've checked to make sure our load balanced servers can talk to each other and they can do. Any help would be greatly appreciated.
Yeah. I've removed the Http Module from web.config and enabled Distributed Calling. It works in that instance. When I add the Http Module back and disable Distributed Calling, it still works. As soon as both the Http Module and Distributed Calling are enabled/present, it hangs.
Does Contour Code First work alongside Distributed Calling?
We currently have a few sites load balanced via Distributed Calling. One particular site uses Contour Code First. When both Distributed Calling and the Contour Code First HttpModule are enabled, the site refuses to start and hangs. When one is disabled and the other enabled, the site starts.
Has anyone experienced the same issue and does anyone know if the two are compatible with each other? Our Umbraco version is 4.11.8 and the Contour version is 3.0.13.
Within the Umbraco log table, the last log message we find is "Submitting calls to distributed servers". The last log message we see in the log files is "Completed resolution of types of umbraco.interfaces.ICacheRefresher, found 6 (took 11ms)".
We've checked to make sure our load balanced servers can talk to each other and they can do. Any help would be greatly appreciated.
Comment author was deleted
Hmm could you try to see what happens when you remove the http module from the web.config
Yeah. I've removed the Http Module from web.config and enabled Distributed Calling. It works in that instance. When I add the Http Module back and disable Distributed Calling, it still works. As soon as both the Http Module and Distributed Calling are enabled/present, it hangs.
Comment author was deleted
Well the module is just used to sync new forms / and update forms (if they changed in code) so should be ok to remove that from all slave sites
is working on a reply...