6 Replies Latest reply on Oct 28, 2009 2:21 PM by Raja Gullapalli

    JBoss Messaging 1.4.2 Fails - JBoss AS 5.0.1 Startup

    Raja Gullapalli Newbie

      Hi,

      I've been for so long tryign to start the JBoss Messaging server on my JBoss 5.0.1 AS. I have been able to do this on a different context root. The error Ive come across is:

      6:46:16,281 ERROR [AbstractKernelController] Error installing to Real: name=vfsfile:/C:/JavaTools/jboss-5.0.1.GA/server/dispatch/deploy/messaging-service.xml state=PreReal mode=Manual requiredState=Real
      org.jboss.deployers.spi.DeploymentException: Error deploying: jboss.messaging:service=ServerPeer
       at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
       at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:118)
       at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
       at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
       at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
       at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
       at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
       at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
       at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
       at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
       at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
       at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
       at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
       at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698)
       at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304)
       at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
       at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
       at org.jboss.Main.boot(Main.java:209)
       at org.jboss.Main$1.run(Main.java:547)
       at java.lang.Thread.run(Thread.java:595)
      Caused by: java.lang.RuntimeException: No Attribute found with name: SecurityDomain for jboss.messaging:service=ServerPeer, attributes: [ProviderVersion, DefaultExpiryQueue, DefaultMaxDeliveryAttempts, ServerAopConfig, JMSProviderName, FailoverCompleteTimeout, JMSVersion, DefaultRedeliveryDelay, StrictTck, Destinations, FailoverStartTimeout, MessageStatistics, RecoverDeliveriesTimeout, DefaultPreserveOrdering, ClientAopConfig, DefaultMessageCounterHistoryDayLimit, DefaultDLQ, SuckerPassword, Instance, DefaultTopicJNDIContext, ServerPeerID, ClusterPullConnectionFactoryName, PostOffice, PersistenceManager, EnableMessageCounters, MessageCounters, ProviderMajorVersion, JMSMajorVersion, DefaultQueueJNDIContext, SecurityStore, JMSUserManager, JMSMinorVersion, SupportsFailover, MessageCounterSamplePeriod, ProviderMinorVersion]
       at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:142)
       at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:114)
       at org.jboss.system.microcontainer.ConfigureAction.installAction(ConfigureAction.java:58)
       at org.jboss.system.microcontainer.ConfigureAction.installAction(ConfigureAction.java:42)
       at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
       at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
       at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
       at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
       at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286)
       at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
       at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
       at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
       at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
       at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
       at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
       at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
       at org.jboss.system.ServiceController.install(ServiceController.java:274)
       at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:90)
       ... 23 more
      


      Also, I did try to comparing the two contexts, i.e the earlier good context with the the new one, the one trying to get things working.

      Thanks,
      Rama

        • 1. Re: JBoss Messaging 1.4.2 Fails - JBoss AS 5.0.1 Startup
          Yong Hao Gao Master

          which version of JBM are you using?

          • 3. Re: JBoss Messaging 1.4.2 Fails - JBoss AS 5.0.1 Startup
            Raja Gullapalli Newbie

            None of the Queues/Topics are deployed.

            DEPLOYMENTS IN ERROR:
             Deployment "vfsfile:/C:/JavaTools/jboss-5.0.1.GA/server/dispatch/deploy/messaging-service.xml" is in error due to the following reason(s): java.lang.RuntimeException: No Attribute found with name: SecurityDomain for jboss.messaging:service=ServerPeer, attributes: [ProviderVersion, DefaultExpiryQueue, DefaultMaxDeliveryAttempts, ServerAopConfig, JMSProviderName, FailoverCompleteTimeout, JMSVersion, DefaultRedeliveryDelay, StrictTck, Destinations, FailoverStartTimeout, MessageStatistics, RecoverDeliveriesTimeout, DefaultPreserveOrdering, ClientAopConfig, DefaultMessageCounterHistoryDayLimit, DefaultDLQ, SuckerPassword, Instance, DefaultTopicJNDIContext, ServerPeerID, ClusterPullConnectionFactoryName, PostOffice, PersistenceManager, EnableMessageCounters, MessageCounters, ProviderMajorVersion, JMSMajorVersion, DefaultQueueJNDIContext, SecurityStore, JMSUserManager, JMSMinorVersion, SupportsFailover, MessageCounterSamplePeriod, ProviderMinorVersion]
             Deployment "jboss.messaging:service=ServerPeer" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.messaging:service=ServerPeer' **
            


            The messaging-service.xml is the default service file:
            <server>
            
             <!-- ServerPeer MBean configuration
             ============================== -->
            
             <mbean code="org.jboss.jms.server.ServerPeer"
             name="jboss.messaging:service=ServerPeer"
             xmbean-dd="xmdesc/ServerPeer-xmbean.xml">
            
             <!-- The unique id of the server peer - in a cluster each node MUST have a unique value - must be an integer -->
            
             <attribute name="ServerPeerID">${jboss.messaging.ServerPeerID:0}</attribute>
            
             <!-- The default JNDI context to use for queues when they are deployed without specifying one -->
            
             <attribute name="DefaultQueueJNDIContext">/queue</attribute>
            
             <!-- The default JNDI context to use for topics when they are deployed without specifying one -->
            
             <attribute name="DefaultTopicJNDIContext">/topic</attribute>
            
             <attribute name="PostOffice">jboss.messaging:service=PostOffice</attribute>
            
             <!-- The JAAS security domain to use for JBoss Messaging -->
            
             <attribute name="SecurityDomain">java:/jaas/messaging</attribute>
            
             <!-- The default security configuration to apply to destinations - this can be overridden on a per destination basis -->
            
             <attribute name="DefaultSecurityConfig">
             <security>
             <role name="guest" read="true" write="true" create="true"/>
             </security>
             </attribute>
            
             <!-- The default Dead Letter Queue (DLQ) to use for destinations.
             This can be overridden on a per destinatin basis -->
            
             <attribute name="DefaultDLQ">jboss.messaging.destination:service=Queue,name=DLQ</attribute>
            
             <!-- The default maximum number of times to attempt delivery of a message before sending to the DLQ (if configured).
             This can be overridden on a per destinatin basis -->
            
             <attribute name="DefaultMaxDeliveryAttempts">10</attribute>
            
             <!-- The default Expiry Queue to use for destinations. This can be overridden on a per destination basis -->
            
             <attribute name="DefaultExpiryQueue">jboss.messaging.destination:service=Queue,name=ExpiryQueue</attribute>
            
             <!-- The default redelivery delay to impose. This can be overridden on a per destination basis -->
            
             <attribute name="DefaultRedeliveryDelay">0</attribute>
            
             <!-- The periodicity of the message counter manager enquiring on queues for statistics -->
            
             <attribute name="MessageCounterSamplePeriod">5000</attribute>
            
             <!-- The maximum amount of time for a client to wait for failover to start on the server side after
             it has detected failure -->
            
             <attribute name="FailoverStartTimeout">60000</attribute>
            
             <!-- The maximum amount of time for a client to wait for failover to complete on the server side after
             it has detected failure -->
            
             <attribute name="FailoverCompleteTimeout">300000</attribute>
            
             <!-- The maximum number of days results to maintain in the message counter history -->
            
             <attribute name="DefaultMessageCounterHistoryDayLimit">-1</attribute>
            
             <!-- The name of the connection factory to use for creating connections between nodes to pull messages -->
            
             <attribute name="ClusterPullConnectionFactoryName">jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory</attribute>
            
             <!-- When redistributing messages in the cluster. Do we need to preserve the order of messages received
             by a particular consumer from a particular producer? -->
            
             <attribute name="DefaultPreserveOrdering">false</attribute>
            
             <!-- Max. time to hold previously delivered messages back waiting for clients to reconnect after failover -->
            
             <attribute name="RecoverDeliveriesTimeout">300000</attribute>
            
             <!-- Set to true to enable message counters that can be viewed via JMX -->
            
             <attribute name="EnableMessageCounters">false</attribute>
            
             <!-- The password used by the message sucker connections to create connections.
             THIS SHOULD ALWAYS BE CHANGED AT INSTALL TIME TO SECURE SYSTEM
             <attribute name="SuckerPassword"></attribute>
             -->
            
             <depends optional-attribute-name="PersistenceManager">jboss.messaging:service=PersistenceManager</depends>
            
             <depends optional-attribute-name="JMSUserManager">jboss.messaging:service=JMSUserManager</depends>
            
             <depends>jboss.messaging:service=Connector,transport=bisocket</depends>
            
             </mbean>
            


            • 4. Re: JBoss Messaging 1.4.2 Fails - JBoss AS 5.0.1 Startup
              Yong Hao Gao Master

              1.4.2 is not for AS5. Pls try 1.4.3, or 1.4.6 (latest)

              Howard

              • 5. Re: JBoss Messaging 1.4.2 Fails - JBoss AS 5.0.1 Startup
                Raja Gullapalli Newbie

                i'll try that tomorrow. I do have a different context root, in which I was successfully able to run the JBM 1.4.2 on my AS 5.0.1.

                Thanks,
                Rama

                • 6. Re: JBoss Messaging 1.4.2 Fails - JBoss AS 5.0.1 Startup
                  Raja Gullapalli Newbie

                  I was able to start JBM 1.4.3 on JBoss AS 5.0.1 GA release qithout any issues.

                  Thanks Howard.

                  -Rama