If I open manualy this image execute the configureMyImage.st code from a playground, then save the image, I don't have a Voyage time error at start up. Are there non friendly interaction between voyage/socket and st command handler? Hilaire Le 22/03/2017 à 20:35, Hilaire a écrit :
Hi,
When I configure a production image with command st handler as following:
pharo myImage st --save --quit configureMyImage.st
I notice at image start up, a Socket timeout error.
In the configureMyImage.st script, among other things, I open a singleton Voyage repository. I added a 5s delay at the end of this script, just wondering if image was shutdown before Voyage establishes connection with the Mongo DB, but no.
Any incompatibility issues to be aware of between st command handler (particularly the --save part) and Voyage repository?
Thanks, Hilaire
-- Dr. Geo http://drgeo.eu