J2EEApplication=null when EJB redeployed using JMX

hsaha Jun 16, 2006 11:18 AM

Hi,
I have written a EJB monitoring MBean service for handling Database failover scenarios. Basically this would redeploy the failed beans after the DB is up.

I am trying to redeploy a failed EJB using the jboss.system:service=MainDeployer MBean by the redeploy(String url) method invocation. The deployment works fine, but after that the EJB MBean shows as
jboss.management.local:
EJBModule=,J2EEApplication=null,J2EEServer=Local,
j2eeType=EntityBean,name=

Pls note the MBean object key J2EEApplication=null. It should actually be J2EEApplication=

Could somebody let me know if there's something else also that needs to be done to inform the JMX Microkernel aware of the EAR associated with the EJB Jar

Regards
Himadri

1. Re: J2EEApplication=null when EJB redeployed using JMX

dimitris Jun 16, 2006 3:42 PM (in response to hsaha)

No, as far as I remember from the JSR-77 spec, it must be the 'null' string.

Can you point otherwise in the spec?
Actions
2. Re: J2EEApplication=null when EJB redeployed using JMX

hsaha Jun 16, 2006 4:24 PM (in response to hsaha)

Hi Dimitris,
Thanks for ur reply.
The failed EJB is a part of an EAR. That is why i am expecting J2EEApplication=xxxearnamexxx

In fact before the EJB is redeployed, the Object name reads:
jboss.management.local:
EJBModule=,J2EEApplication=xx.ear,J2EEServer=Local,
j2eeType=EntityBean,name=abcEJB

and after redeployment it reads :
jboss.management.local:
EJBModule=,J2EEApplication=null,J2EEServer=Local,
j2eeType=EntityBean,name=abcEJB

Is this ok?

Regards
Himadri
Actions
3. Re: J2EEApplication=null when EJB redeployed using JMX

dimitris Jun 20, 2006 5:48 AM (in response to hsaha)

I guess this is related to the embedded ejb jar redeployed independently of the .ear. Can you try redeploy the whole ear?
Actions
4. Re: J2EEApplication=null when EJB redeployed using JMX

hsaha Jun 21, 2006 12:16 PM (in response to hsaha)

Yes, this is related to an embedded EJB in an EAR.

Redeploying my EAR solves the problem, but that is not the intention at all. Since the EAR consists of tens of EJBs, we dont want to loose the other EJB services for that period.

Is there any workaround for this?

Regards
Himadri
Actions

Go to original post