|Changes on .restart that may affect you in this week 3.1M [message #482980]
||Fri, 28 August 2009 19:46
| Angel Vera
Registered: July 2009
With this new driver we fixed a restart issue that affects:|
- Callers of IServer.restart, (ie: Run On Server, ...)
- Server adopters that don't provide a .restart mechanism (ie: Tomcat
Before bug# 255561 , if you try to schedule a job immediately after
calling restart, the job will be scheduled after the server stop job but
before the server start job. If you were relaying in this behaviour,
this was not the intended behaviour for Server.restart. For a concrete
example on the consequence on this behaviour when a 'Run on Server'
action was launched using 'Tomcat' it would cause a publish job, and the
browser launch job to be scheduled before the server was fully
restarted. Now with the new changes, we have fix the scheduling of the
jobs in restart, and now the stop and start jobs will be scheduled
before giving back control to the caller, which will then scheduled the
browser to be launched at the correct time.
But....!! As a consequence of this changes, we have found that the 'Run
On Server' has a bug that will be fix for 3.1M RC2. The new found bug
will trigger the intended publish after a restart, when it should be
done before to ensure that all the resources are sync.
For more information and a the discussion on this issue refer to bug#
255561. Comment #34, on that bug is probably the most interesting one,
but be sure to read comment #29 to see the effect of the changes.
Thanks to Larry for all his help on the testing on this bug.
Mr. Angel Vera
Those who think that something is impossible,
should not interfere with those who are willing to do it. - Angel Vera
WTP Server Tools Developer
Powered by FUDForum
. Page generated in 0.01591 seconds