Application Server 7
  1. Application Server 7
  2. AS7-887

Support legacy ServiceMBeans in SAR deployments

    Details

    • Similar Issues:
      Show 10 results 

      Description

      It looks like the current SAR deployment code (jboss-as-sar) will deploy simple MBeans just fine. However, users may expect to be able to deploy older ServiceMBeans from previous Jboss AS versions. Currently, attempting to do this results in a ClassNotFoundException, since the org.jboss.system.ServiceMBean interface doesn't exist anymore.

      Ideally this would also involve supporting ServiceMBeans that extend org.jboss.system.ServiceMBeanSupport, which also doesn't exist anymore.

        Issue Links

          Activity

          Show
          Brandon Atkinson
          added a comment - https://community.jboss.org/message/632823
          Hide
          Eduardo Martins
          added a comment - - edited

          The attached pull enables deployments of MBeans implementing ServiceMBean, but wrt ServiceMBeanSupport the situation is quite complicated:

          • there is an old JBoss Logger exposed (as field and through method), converting to the new Logger will automatically render any MBean that uses it incompatible
          • requires org.jboss.mx.util.JBossNotificationBroadcasterSupport, which implementation must be updated too, since it requires missing features
          • has pojoX() and AS5 controllers exposed
          • has a public method to get missing DeploymentInfo (which in turn needs SARDeployerMBean)
          • support of even older ServiceMBeanSupport depends on AS5 ServiceController

          Obviously it's not impossible to reimplement any of the missing features, but the class refactor should turn incompatible quite a few of the usages, and if it's not compatible then why not promote the usage of AS7 Services instead...

          Show
          Eduardo Martins
          added a comment - - edited The attached pull enables deployments of MBeans implementing ServiceMBean, but wrt ServiceMBeanSupport the situation is quite complicated: there is an old JBoss Logger exposed (as field and through method), converting to the new Logger will automatically render any MBean that uses it incompatible requires org.jboss.mx.util.JBossNotificationBroadcasterSupport, which implementation must be updated too, since it requires missing features has pojoX() and AS5 controllers exposed has a public method to get missing DeploymentInfo (which in turn needs SARDeployerMBean) support of even older ServiceMBeanSupport depends on AS5 ServiceController Obviously it's not impossible to reimplement any of the missing features, but the class refactor should turn incompatible quite a few of the usages, and if it's not compatible then why not promote the usage of AS7 Services instead...
          Hide
          Eduardo Martins
          added a comment -

          The now merged PR adds full support for ServiceMBean, and partial support for ServiceMBeanSupport:

          • AS5 controller methods are gone, thus overwrites will fail
          • logger was migrated, thus usage of the old one will fail
          • no DeploymentInfo
          • no JBossNotificationBroadcasterSupport

          Support for this feature comes from the new module system-jmx, which is an optional dependency applied to war deployments

          Show
          Eduardo Martins
          added a comment - The now merged PR adds full support for ServiceMBean, and partial support for ServiceMBeanSupport: AS5 controller methods are gone, thus overwrites will fail logger was migrated, thus usage of the old one will fail no DeploymentInfo no JBossNotificationBroadcasterSupport Support for this feature comes from the new module system-jmx, which is an optional dependency applied to war deployments
          Hide
          RH Bugzilla Integration
          added a comment -

          John Mazzitelli <mazz@redhat.com> made a comment on bug 851268

          I've got some notes on this port work found here on the wiki:

          https://docs.jboss.org/author/display/RHQ/Hosting+RHQ+Server+in+AS7

          Show
          RH Bugzilla Integration
          added a comment - John Mazzitelli <mazz@redhat.com> made a comment on bug 851268 I've got some notes on this port work found here on the wiki: https://docs.jboss.org/author/display/RHQ/Hosting+RHQ+Server+in+AS7
          Hide
          RH Bugzilla Integration
          added a comment -

          John Mazzitelli <mazz@redhat.com> made a comment on bug 851268

          removing all the external bug tracking links - the bugzilla integration to jira is not good:

          I will add "see also" links from this BZ to these:

          https://issues.jboss.org/browse/AS7-5342
          https://issues.jboss.org/browse/AS7-5336
          https://issues.jboss.org/browse/AS7-5321
          https://issues.jboss.org/browse/AS7-5177
          https://issues.jboss.org/browse/AS7-887
          https://issues.jboss.org/browse/AS7-3199

          Show
          RH Bugzilla Integration
          added a comment - John Mazzitelli <mazz@redhat.com> made a comment on bug 851268 removing all the external bug tracking links - the bugzilla integration to jira is not good: I will add "see also" links from this BZ to these: https://issues.jboss.org/browse/AS7-5342 https://issues.jboss.org/browse/AS7-5336 https://issues.jboss.org/browse/AS7-5321 https://issues.jboss.org/browse/AS7-5177 https://issues.jboss.org/browse/AS7-887 https://issues.jboss.org/browse/AS7-3199
          Hide
          Guy Kaisin
          added a comment -

          Hi all, sorry but for me the solution is not usable.
          see my response on conversation: https://community.jboss.org/message/760195
          regards

          Show
          Guy Kaisin
          added a comment - Hi all, sorry but for me the solution is not usable. see my response on conversation: https://community.jboss.org/message/760195 regards
          Hide
          rajesh k
          added a comment -

          We are using Jboss EAP6.0.1 and used foo-commonj workmanager.sar that implemented on ServiceMBean and ServiceMBeanSupport. It received same exception as reported here and included previous version supported jars.
          Can I use your fix that is 6.1.0 jars to resolve this issue.
          Please help me in this.

          -Rajesh

          Show
          rajesh k
          added a comment - We are using Jboss EAP6.0.1 and used foo-commonj workmanager.sar that implemented on ServiceMBean and ServiceMBeanSupport. It received same exception as reported here and included previous version supported jars. Can I use your fix that is 6.1.0 jars to resolve this issue. Please help me in this. -Rajesh
          Hide
          Guy Kaisin
          added a comment - - edited

          Hi
          The jboss version you are using does NOT contain the sar deployment correction.
          The correction has been integrated and tested in jboss 7.2.0 alpha1 build 1372.

          Please use the last jboss artifact (nightly build for instance).

          regards,
          Guy

          Show
          Guy Kaisin
          added a comment - - edited Hi The jboss version you are using does NOT contain the sar deployment correction. The correction has been integrated and tested in jboss 7.2.0 alpha1 build 1372. Please use the last jboss artifact (nightly build for instance). regards, Guy
          Hide
          rajesh k
          added a comment -

          Pl kindly tell me which corrected jars i can use for Jboss EAP 6.0.1.
          Can you pl send any nightly build link if you have.

          Thanks
          Rajesh

          Show
          rajesh k
          added a comment - Pl kindly tell me which corrected jars i can use for Jboss EAP 6.0.1. Can you pl send any nightly build link if you have. Thanks Rajesh
          Hide
          Guy Kaisin
          added a comment -

          Hi,

          this link should be useful:
          https://ci.jboss.org/hudson/job/WildFly-latest-master/

          Regards,

          Guy

          Show
          Guy Kaisin
          added a comment - Hi, this link should be useful: https://ci.jboss.org/hudson/job/WildFly-latest-master/ Regards, Guy
          Hide
          rajesh k
          added a comment -

          Thank you, I downloaded last successful build (wildfly-8.x.zip) from wildFly-latest-master. Pl kindly share required jars i can apply to EAP 6.0.1 to fix this issue.

          Regards,
          Rajesh.

          Show
          rajesh k
          added a comment - Thank you, I downloaded last successful build (wildfly-8.x.zip) from wildFly-latest-master. Pl kindly share required jars i can apply to EAP 6.0.1 to fix this issue. Regards, Rajesh.
          Hide
          Eduardo Martins
          added a comment -

          Rajesh, if you have eap support please use it, this is a community site, no SLAs here. If you don't have EAP support please start a topic on the community forums.

          Anyway, if you don't have support and want to stick with EAP I would move to the latest release instead, since EAP 6.1 includes all of this. An alternative is Wildfly, which includes latest features/fixes, such as https://issues.jboss.org/browse/WFLY-222

          Show
          Eduardo Martins
          added a comment - Rajesh, if you have eap support please use it, this is a community site, no SLAs here. If you don't have EAP support please start a topic on the community forums. Anyway, if you don't have support and want to stick with EAP I would move to the latest release instead, since EAP 6.1 includes all of this. An alternative is Wildfly, which includes latest features/fixes, such as https://issues.jboss.org/browse/WFLY-222
          Hide
          rajesh k
          added a comment -

          Sorry I am bothing you as I dont have support and I have to stick to EAP 6.0.1. I need your help on couple of thing we came across during migration. I went through many jboss community forums as well on below issue.

          We are migrating app from Websphere to Jboss 6.0.1 EAP. We have websphere's workmanager feature which needs to be migrate using commonj. I tried to foo-commonj.sar to make use of workmanager features from ejb in Jboss 6.0.1 EAP. I used previous versions support jars to register commonj jndi in Jboss 6.0.1 EAP.

          will we able to use Commonj within EJB in JBoss 6.0.1 EAP as EJB spec prohibits to create threads within EJB due to vendor licencing issues.

          Pl help me in this.

          Regards,
          Rajesh.

          Show
          rajesh k
          added a comment - Sorry I am bothing you as I dont have support and I have to stick to EAP 6.0.1. I need your help on couple of thing we came across during migration. I went through many jboss community forums as well on below issue. We are migrating app from Websphere to Jboss 6.0.1 EAP. We have websphere's workmanager feature which needs to be migrate using commonj. I tried to foo-commonj.sar to make use of workmanager features from ejb in Jboss 6.0.1 EAP. I used previous versions support jars to register commonj jndi in Jboss 6.0.1 EAP. will we able to use Commonj within EJB in JBoss 6.0.1 EAP as EJB spec prohibits to create threads within EJB due to vendor licencing issues. Pl help me in this. Regards, Rajesh.
          Hide
          jaikiran pai
          added a comment -

          >> Sorry I am bothing you as I dont have support and I have to stick to EAP 6.0.1.

          EAP 6.0.1 binary is a paid product and you are entitled to support. Where did you get it from? You might want to check with your team to see who has access to the customer service portal.

          >> We are migrating app from Websphere to Jboss 6.0.1 EAP. We have websphere's workmanager feature which needs to be migrate using commonj. I tried to foo-commonj.sar to make use of workmanager features from ejb in Jboss 6.0.1 EAP. I used previous versions support jars to register commonj jndi in Jboss 6.0.1 EAP.

          You already created 2 other JIRAs to ask that question. Please do use the JIRAs for such questions. The user forums are the place where this should be discussed.

          Show
          jaikiran pai
          added a comment - >> Sorry I am bothing you as I dont have support and I have to stick to EAP 6.0.1. EAP 6.0.1 binary is a paid product and you are entitled to support. Where did you get it from? You might want to check with your team to see who has access to the customer service portal. >> We are migrating app from Websphere to Jboss 6.0.1 EAP. We have websphere's workmanager feature which needs to be migrate using commonj. I tried to foo-commonj.sar to make use of workmanager features from ejb in Jboss 6.0.1 EAP. I used previous versions support jars to register commonj jndi in Jboss 6.0.1 EAP. You already created 2 other JIRAs to ask that question. Please do use the JIRAs for such questions. The user forums are the place where this should be discussed.

            People

            • Assignee:
              Eduardo Martins
              Reporter:
              Matt Drees
            • Votes:
              10 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: