EAR scoping failed for JMSProviderLoader, BUG?

bartmann Aug 15, 2002 1:47 PM

In the mbean configuration of the JMSProviderLoader
you have to specify the ProviderAdapterClass.

I have a xxx.ear containing a xxx.sar which loads the
typical 3 mbeans (ProprietaryMessageService, ProviderLoader, ServerSessionPoolLoader)

The whole this *RUNS FINE* (deploys, undeploys) when
not using ear-scoping, but i need a few of these beasts
under ear-scoping for a long running system.

When using ear-scoping the deployment *FAILS* with a
ClassNotFoundException when trying to resolve the
ProviderAdapterClass from the ProviderLoader-mbean.

But everything so far is INSIDE one big ear!

What am I doing wrong here?
I will attach the jboss-service.xml of the xxx.sar
inside the xxx.ear.

Enjoy,

Michael

1. Re: EAR scoping failed for JMSProviderLoader, BUG?

bartmann Aug 15, 2002 1:51 PM (in response to bartmann)

oh, forgot to say:

this is under 3.2.0-RC1 (Branch_3_2)
Actions
2. Re: EAR scoping failed for JMSProviderLoader, BUG?

bartmann Aug 16, 2002 5:04 AM (in response to bartmann)

Ok, I fixed this one.

The fix is in cvs (Branch_3_0, Branch_3_2, HEAD) and
should show up with the 3.0.2 release.

It was a bug in JMSProviderLoader using
Class.forName() instead of
Thread.currentThread().getContextClassLoader.loadClass()

Enjoy,
Michael
Actions

Go to original post