This is now fixed, annotation proxies are no longer used, they were
being leaked anyway.
Jason T. Greene wrote:
This is coming from the profile service mbean discovery code which
has
to generate annotations. I was going to work around it today since are
components are frozen.
It's also a lie, AnnocationCreator uses the passed in annotations
classloader anyway.
Brian Stansberry wrote:
> I figure the last one is related to the
>
org.jboss.test.cluster.defaultcfg.test.ClusterPartitionManagedObjectsTestCase(Default-udp).testHAPartition
> failure that appeared about a week ago. I'll be looking into that today.
>
> Dimitris Andreadis wrote:
>> Have you seen the warnings after logging in to the admin-console?
>>
>> ...
>> 17:43:39,093 WARN [AnnotationCreator] No ClassLoader provided, using
>> TCCL: org.jboss.managed.api.annotation.ManagementComponent
>> 17:43:39,093 WARN [AnnotationCreator] No ClassLoader provided, using
>> TCCL: org.jboss.managed.api.annotation.ManagementObject
>> 17:43:39,093 WARN [AnnotationCreator] No ClassLoader provided, using
>> TCCL: org.jboss.managed.api.annotation.ManagementComponent
>> 17:43:39,125 WARN [ManagementViewImpl] Failed to merged the
>> following runtime ManagedObjects:
>> {DefaultPartition/HAPartition=ManagedObject{DefaultPartition}}
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jboss-development
>
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development