There is an easy workaround. Write a new class with the only methods
annotated as probes (Note that these are empty methods) and then
instantiate in your current class and call it from the right place (This
is done by all other modules).
Bobby Bissett wrote:
>>>
>>> Can such errors be sorted out before the integration of a new version?
>> I'm not sure what you mean by "sorted out". One of two things has to
>> happen in order to get rid of these errors:
>>
>> * 9536 needs to be fixed
>> * The ORB needs to be modified to introduce two new classes just
>> for the @Probe annotations
>>
>> The monitoring team is unwilling to commit to fixing 9536. The ORB
>> fix requires a new ORB integration.
>
> Is there an obvious next step? This is partially blocking upgrade
> since an upgrade process can *never* return successfully.
>
> Thanks,
> Bobby
>