Bugzilla – Bug 6394
erroneous error messages after a failed create
Last modified: 2008-10-15 09:32:40
You need to
before you can comment on or make changes to this bug.
"no vm?" is logged after a failed create. This is coming from the new (as of
tp2.0) object cache + expiration system. It's ultimately a cosmetic error
since it does not impede any functionality, but obviously the service should
not be producing log statements that are annoying/unhelpful.
Fix for Bug #6392
Fix for Bug #6394
Fix for Bug #6416
Erroneous errors involving destruction coupled with status queries. All the
same cause, missing removal step in the workspace service object cache manager.