1 Reply Latest reply on Jul 5, 2011 8:22 PM by Peter Johnson

    Whether License Required for JBoss EAP 5.1 JMS Messaging to be fully functional?

    Karunanidhi Murugaian Newbie

      Our product support JBOSS Server for Messaging and we want to claim support for JBOSS EAP 5.1. The scenario goes like this.

       

      Downloaded JBOSS 5.1 Enterprise Application Platform server and enabled the log level of management and binding to Trace. The default server profile was used and server was started using root privileges.

       

      The console show up with following message.

       

      15:55:40,160 INFO  [RARDeployment] Required license terms exist, view vfsfile:/usr/local/jboss-eap-5.1.0/jboss-eap-5.1/jboss-as/server/default/deploy/jms-ra.rar/META-INF/ra.xml

       

      The jms-ra.rar adapter description is specific to JMS. Does the above message means that licensing is required for complete funtional of JMS? Or the JMS is fully functional during Trail Period even without license?

      Our system failed to consume messages from jboss queues?

      The server came up with some exceptions in server.log and one such exception is mentioned below. we use default connection factory to get connections to JMS Queues.

       

      jboss.messaging.connectionfactory:service=ConnectionFactory

      javax.management.InstanceNotFoundException: jboss.messaging.connectionfactory:service=ConnectionFactory is not registered.

          at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:526)

          at org.jboss.mx.server.MBeanServerImpl.isInstanceOf(MBeanServerImpl.java:974)

          at org.jboss.management.j2ee.MBean.postCreation(MBean.java:151)

          at org.jboss.management.j2ee.J2EEManagedObject.postRegister(J2EEManagedObject.java:314)

          at org.jboss.mx.server.AbstractMBeanInvoker.invokePostRegister(AbstractMBeanInvoker.java:974)

          at org.jboss.mx.server.AbstractMBeanInvoker.postRegister(AbstractMBeanInvoker.java:681)

          at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:335)

          at sun.reflect.GeneratedMethodAccessor107.invoke(Unknown Source)

          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

          at java.lang.reflect.Method.invoke(Method.java:597)

          at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)

          at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)

          at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)

          at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)

          at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140)

          at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)

          at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)

          at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)

          at org.jboss.mx.server.MBeanServerImpl$3.run(MBeanServerImpl.java:1431)

          at java.security.AccessController.doPrivileged(Native Method)

          at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1426)

          at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:376)

          at org.jboss.management.j2ee.MBean.create(MBean.java:79)

          at org.jboss.management.j2ee.deployers.ServiceModuleJSR77Deployer.deployJsr77(ServiceModuleJSR77Deployer.java:62)

          at org.jboss.management.j2ee.deployers.ServiceModuleJSR77Deployer.deployJsr77(ServiceModuleJSR77Deployer.java:40)

          at org.jboss.management.j2ee.deployers.AbstractVFSJSR77Deployer.deployJsr77(AbstractVFSJSR77Deployer.java:46)

          at org.jboss.management.j2ee.deployers.AbstractJSR77Deployer.deploy(AbstractJSR77Deployer.java:173)

          at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)

          at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55)

          at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)

          at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)

          at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)

          at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)

          at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

          at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)

          at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)

          at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

          at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)

          at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)

          at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)

          at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)

          at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)

          at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)

          at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)

          at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)

          at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403)

          at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

          at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)

          at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)

          at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

          at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)

          at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778)

          at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543)

          at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308)

          at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256)

          at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)

          at org.jboss.Main.boot(Main.java:221)

          at org.jboss.Main$1.run(Main.java:556)

          at java.lang.Thread.run(Thread.java:619)

        • 1. Re: Whether License Required for JBoss EAP 5.1 JMS Messaging to be fully functional?
          Peter Johnson Master

          Karunanidhi, welcome to the JBoss Community!

           

          >>Does the above message means that licensing is required for complete funtional of JMS?

          No, it doesn't. That same message appears in the 5.1.0.GA version, and JBoss Messaging works just fine.

           

          Regarding the excp[etion stack trace, what configuration changes did you make to Messaging? The jboss.messaging.connectionfactory:service=ConnectionFactory MBean is declared in server/default/deploy/messaging/connection-factories-service.xml, so it should not be missing.

           

          Is this the first exception stack trace in the server log (with ERROR level)?