Thanks, Fred. Turns out to have been a red herring. The
manage/unmanage logic actually had a bug in it that was tripped by an
obscure database condition seen only on that box. When I made that
database available to one of my other boxes we replicated it right away.
>>>>> "F" == FredK <
fred.l.kl...@gmail.com> writes:
F> On Tuesday, October 30, 2012 9:33:44 AM UTC-7, Jake Colman wrote:
>> We have an application that manages/unmanages a widget depending on certain
>> logic. It works fine on almost every box we run. We set up a new standalone
>> Solaris 11 machine for QA and the widget is always managed, it won't
>> unmanage. Has anyone seen something like this before? Where a widget
>> refuses to unmanage? I know the code is good because its been working in
>> the field for a long time. The only issue is on this new box that we just
>> created. Everything but this one widget on this one screen seems
>> fine. Thanks. ...Jake -- Jake Colman | Director, Software Development
>> PRINCIPIA | 101 West Elm Street | Suite 620 | Conshohocken | PA 19428 t: +1
>>
(610) 755 9786 | f:
+1 (201) 221 8929 e:
col...@ppllc.com | w:
>>
www.principiaSFP.com Know your investments
F> Probably too much water from Sandy...
F> What kind of widget is it? Or is it a gadget? Is it the direct child of a
F> Shell?