D
dbeavon
Guest
I sorted this out with Progress tech support. Apparently there should not normally be a message stating either way whether the appserver started successfully or failed to start. The error you should be looking for is simply: Starting as12345. Check status. (8296) However, in our case we were seeing the "unable to start" message when attempting to start the appserver broker. Per tech support, the first thing to try is starting the default app server that is defined in ubroker.properties. It is called asbroker1. We issued the start command and everything worked as expected: Starting asbroker1. Check status. Then we eliminated the differences between the configuration of that broker and the one that says "unable to start" (a bogus message given that it actually starts). By the process of elimination (removing things like logging preferences, autostart preferences, etc) we finally commented out the setting of the PROPATH and that finally gave us the right startup message (vs "unable to start"). So for anyone else getting the bogus "unable to start" message, you should first check the behavior when starting asbroker1 and then try to isolate the difference between your broker and asbroker1. Hope this helps.
Continue reading...
Continue reading...