Queue and topic not bound in jboss 5 GA
naveenkumarnl Jul 8, 2014 2:18 AMHi folks,
Please help me to resolve the issue.
Summary: I get queue not bound error when I start my jboss server.
Below is the server log:
/opt/jboss/bin/run.conf: line 84: rem: command not found
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/jboss
JAVA: java
JAVA_OPTS: -Dprogram.name=run.sh -Xms2048m -Xmx2048m -XX:MaxPermSize=512m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -Djboss.messaging.ServerPeerID=112 -Djboss.messaging.datachanneltcpport=7910 -Djboss.messaging.datachanneludpport=45720 -Djboss.partition.udpGroup=230.11.11.11 -Djboss.jgroups.udp.mcast_port=45691 -Djboss.jgroups.diagnostics_addr=226.0.75.75 -Djboss.jgroups.diagnostics_port=7510 -Dcom.sun.management.jmxremote.port=6789 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.rmi.server.hostname=10.10.75.14 -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -Djboss.messaging.ServerPeerID=98 -Djavax.net.ssl.trustStore=/opt/jboss/server/all/conf/truststore -Djavax.net.ssl.trustStorePassword=password -Djava.net.preferIPv4Stack=true
CLASSPATH: /opt/jboss/bin/run.jar
=========================================================================
00:44:53,976 INFO [ServerImpl] Starting JBoss (Microcontainer)...
00:44:53,979 INFO [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)
00:44:53,979 INFO [ServerImpl] Bootstrap URL: null
00:44:53,979 INFO [ServerImpl] Home Dir: /opt/jboss-5.1.0.GA
00:44:53,979 INFO [ServerImpl] Home URL: file:/opt/jboss-5.1.0.GA/
00:44:53,980 INFO [ServerImpl] Library URL: file:/opt/jboss-5.1.0.GA/lib/
00:44:53,981 INFO [ServerImpl] Patch URL: null
00:44:53,981 INFO [ServerImpl] Common Base URL: file:/opt/jboss-5.1.0.GA/common/
00:44:53,981 INFO [ServerImpl] Common Library URL: file:/opt/jboss-5.1.0.GA/common/lib/
00:44:53,981 INFO [ServerImpl] Server Name: all
00:44:53,981 INFO [ServerImpl] Server Base Dir: /opt/jboss-5.1.0.GA/server
00:44:53,982 INFO [ServerImpl] Server Base URL: file:/opt/jboss-5.1.0.GA/server/
00:44:53,982 INFO [ServerImpl] Server Config URL: file:/opt/jboss-5.1.0.GA/server/all/conf/
00:44:53,982 INFO [ServerImpl] Server Home Dir: /opt/jboss-5.1.0.GA/server/all
00:44:53,982 INFO [ServerImpl] Server Home URL: file:/opt/jboss-5.1.0.GA/server/all/
00:44:53,982 INFO [ServerImpl] Server Data Dir: /opt/jboss-5.1.0.GA/server/all/data
00:44:53,983 INFO [ServerImpl] Server Library URL: file:/opt/jboss-5.1.0.GA/server/all/lib/
00:44:53,983 INFO [ServerImpl] Server Log Dir: /opt/jboss-5.1.0.GA/server/all/log
00:44:53,983 INFO [ServerImpl] Server Native Dir: /opt/jboss-5.1.0.GA/server/all/tmp/native
00:44:53,983 INFO [ServerImpl] Server Temp Dir: /opt/jboss-5.1.0.GA/server/all/tmp
00:44:53,983 INFO [ServerImpl] Server Temp Deploy Dir: /opt/jboss-5.1.0.GA/server/all/tmp/deploy
00:44:54,697 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/opt/jboss-5.1.0.GA/server/all/conf/bootstrap.xml
00:44:55,476 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]
00:44:55,478 INFO [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]
00:44:56,045 INFO [CopyMechanism] VFS temp dir: /opt/jboss-5.1.0.GA/server/all/tmp
00:44:56,046 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
00:44:57,819 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc.
00:44:57,819 INFO [ServerInfo] Java Runtime: OpenJDK Runtime Environment (build 1.6.0_17-b17)
00:44:57,819 INFO [ServerInfo] Java VM: OpenJDK Server VM 14.0-b16,Sun Microsystems Inc.
00:44:57,819 INFO [ServerInfo] OS-System: Linux 2.6.18-194.32.1.el5,i386
00:44:57,820 INFO [ServerInfo] VM arguments: -Dprogram.name=run.sh -Xms2048m -Xmx2048m -XX:MaxPermSize=512m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -Djboss.messaging.ServerPeerID=112 -Djboss.messaging.datachanneltcpport=7910 -Djboss.messaging.datachanneludpport=45720 -Djboss.partition.udpGroup=230.11.11.11 -Djboss.jgroups.udp.mcast_port=45691 -Djboss.jgroups.diagnostics_addr=226.0.75.75 -Djboss.jgroups.diagnostics_port=7510 -Dcom.sun.management.jmxremote.port=6789 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.rmi.server.hostname=10.10.75.14 -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -Djboss.messaging.ServerPeerID=98 -Djavax.net.ssl.trustStore=/opt/jboss/server/all/conf/truststore -Djavax.net.ssl.trustStorePassword=password -Djava.net.preferIPv4Stack=true -Djava.endorsed.dirs=/opt/jboss/lib/endorsed
00:44:57,855 INFO [JMXKernel] Legacy JMX core initialized
00:45:00,983 INFO [ProfileServiceBootstrap] Loading profile: ProfileKey@1117681[domain=default, server=default, name=all]
00:45:03,932 INFO [WebService] Using RMI server codebase: http://10.10.75.14:8083/
00:45:11,977 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
00:45:11,977 INFO [NativeServerConfig] 3.1.2.GA
00:45:13,203 INFO [AttributeCallbackItem] Owner callback not implemented.
00:45:14,625 INFO [LogNotificationListener] Adding notification listener for logging mbean "jboss.system:service=Logging,type=Log4jService" to server org.jboss.mx.server.MBeanServerImpl@15b011c[ defaultDomain='jboss' ]
00:45:26,406 INFO [ContainerDependencyMetaData] addJndiDependency, JndiDependencyMetaData@3540ce{topic/demoTopic}
00:45:32,586 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@2553775{vfszip:/opt/jboss-5.1.0.GA/server/all/deploy/NotificationMailMDB-1.1.jar/}
00:45:32,588 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@2553775{vfszip:/opt/jboss-5.1.0.GA/server/all/deploy/NotificationMailMDB-1.1.jar/}
00:45:32,588 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@2553775{vfszip:/opt/jboss-5.1.0.GA/server/all/deploy/NotificationMailMDB-1.1.jar/}
00:45:32,588 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@2553775{vfszip:/opt/jboss-5.1.0.GA/server/all/deploy/NotificationMailMDB-1.1.jar/}
00:45:32,589 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@23357928{vfsfile:/opt/jboss-5.1.0.GA/server/all/deploy/profileservice-secured.jar/}
00:45:32,589 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@23357928{vfsfile:/opt/jboss-5.1.0.GA/server/all/deploy/profileservice-secured.jar/}
00:45:32,589 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@23357928{vfsfile:/opt/jboss-5.1.0.GA/server/all/deploy/profileservice-secured.jar/}
00:45:32,590 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@23357928{vfsfile:/opt/jboss-5.1.0.GA/server/all/deploy/profileservice-secured.jar/}
00:45:32,592 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@2573405{vfszip:/opt/jboss-5.1.0.GA/server/all/deploy/dgws-ear.ear/dgws-serviceejb-1.3-SNAPSHOT.jar/}
00:45:32,592 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@2573405{vfszip:/opt/jboss-5.1.0.GA/server/all/deploy/dgws-ear.ear/dgws-serviceejb-1.3-SNAPSHOT.jar/}
00:45:32,592 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@2573405{vfszip:/opt/jboss-5.1.0.GA/server/all/deploy/dgws-ear.ear/dgws-serviceejb-1.3-SNAPSHOT.jar/}
00:45:32,593 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@2573405{vfszip:/opt/jboss-5.1.0.GA/server/all/deploy/dgws-ear.ear/dgws-serviceejb-1.3-SNAPSHOT.jar/}
00:45:32,593 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@33111802{vfszip:/opt/jboss-5.1.0.GA/server/all/deploy/dgws-ear.ear/dgws-statefulserviceejb-1.3-SNAPSHOT.jar/}
00:45:32,593 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@33111802{vfszip:/opt/jboss-5.1.0.GA/server/all/deploy/dgws-ear.ear/dgws-statefulserviceejb-1.3-SNAPSHOT.jar/}
00:45:34,688 INFO [CorbaNamingService] CORBA Naming Started
00:45:37,353 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://10.10.75.14/jndi/rmi://10.10.75.14:1090/jmxconnector
00:45:37,636 INFO [MailService] Mail Service bound to java:/Mail
00:45:38,533 INFO [SnmpAgentService] SNMP agent going active
00:45:41,214 INFO [DG3QACluster] Initializing partition DG3QACluster
00:45:41,287 INFO [STDOUT]
---------------------------------------------------------
GMS: address is 10.10.75.14:40110 (cluster=DG3QACluster)
---------------------------------------------------------
00:45:41,468 INFO [PlatformMBeanServerRegistration] JBossCache MBeans were successfully registered to the platform mbean server.
00:45:41,515 INFO [STDOUT]
---------------------------------------------------------
GMS: address is 10.10.75.14:40110 (cluster=DG3QACluster-HAPartitionCache)
---------------------------------------------------------
00:45:43,419 INFO [DG3QACluster] Number of cluster members: 1
00:45:43,421 INFO [DG3QACluster] Other members: 0
00:45:43,580 INFO [RPCManagerImpl] Received new cluster view: [10.10.75.14:40110|0] [10.10.75.14:40110]
00:45:43,582 INFO [RPCManagerImpl] Cache local address is 10.10.75.14:40110
00:45:43,585 INFO [RPCManagerImpl] state was retrieved successfully (in 2.07 seconds)
00:45:43,602 INFO [ComponentRegistry] JBoss Cache version: JBossCache 'Cascabel' 3.1.0.GA
00:45:43,602 INFO [DG3QACluster] Fetching serviceState (will wait for 30000 milliseconds):
00:45:43,604 INFO [DG3QACluster] State could not be retrieved (we are the first member in group)
00:45:43,823 INFO [HANamingService] Started HAJNDI bootstrap; jnpPort=1100, backlog=50, bindAddress=dg3qasrv1.symyx.com/10.10.75.14
00:45:43,828 INFO [DetachedHANamingService$AutomaticDiscovery] Listening on /10.10.75.14:1102, group=230.11.11.11, HA-JNDI address=10.10.75.14:1100
00:45:45,504 INFO [UnifiedInvokerHA] Service name is jboss:service=invoker,type=unifiedha
00:45:46,417 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
00:45:46,441 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
00:45:46,596 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
00:45:46,649 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version - tag:JBOSSTS_4_6_1_GA) - JBoss Inc.
00:45:46,649 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
00:45:46,834 INFO [TransactionManagerService] Initializing recovery manager
00:45:46,979 INFO [TransactionManagerService] Recovery manager configured
00:45:46,979 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
00:45:47,025 INFO [TransactionManagerService] Starting transaction recovery manager
00:45:47,740 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/lib/i386/server:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/lib/i386:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib
00:45:47,973 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-dg3qasrv1.symyx.com%2F10.10.75.14-8080
00:45:47,974 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-dg3qasrv1.symyx.com%2F10.10.75.14-12502
00:45:48,008 INFO [StandardService] Starting service jboss.web
00:45:48,010 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.3.GA
00:45:48,069 INFO [Catalina] Server startup in 94 ms
00:45:48,093 INFO [TomcatDeployment] deploy, ctxPath=/invoker
00:45:48,926 INFO [TomcatDeployment] deploy, ctxPath=/web-console
00:45:49,270 INFO [TomcatDeployment] deploy, ctxPath=/jbossws
00:45:49,294 INFO [TomcatDeployment] deploy, ctxPath=/juddi
00:45:49,326 INFO [RegistryServlet] Loading jUDDI configuration.
00:45:49,327 INFO [RegistryServlet] Resources loaded from: /WEB-INF/juddi.properties
00:45:49,327 INFO [RegistryServlet] Initializing jUDDI components.
00:45:49,623 INFO [RARDeployment] Required license terms exist, view vfszip:/opt/jboss-5.1.0.GA/server/all/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
00:45:49,641 INFO [RARDeployment] Required license terms exist, view vfszip:/opt/jboss-5.1.0.GA/server/all/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
00:45:49,680 INFO [RARDeployment] Required license terms exist, view vfszip:/opt/jboss-5.1.0.GA/server/all/deploy/jms-ra.rar/META-INF/ra.xml
00:45:49,708 INFO [RARDeployment] Required license terms exist, view vfszip:/opt/jboss-5.1.0.GA/server/all/deploy/mail-ra.rar/META-INF/ra.xml
00:45:49,772 INFO [RARDeployment] Required license terms exist, view vfszip:/opt/jboss-5.1.0.GA/server/all/deploy/quartz-ra.rar/META-INF/ra.xml
00:45:49,884 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
00:45:49,939 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
00:45:49,942 INFO [RAMJobStore] RAMJobStore initialized.
00:45:49,942 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
00:45:49,942 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
00:45:49,943 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
00:45:50,132 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=XADGDevDS' to JNDI name 'java:XADGDevDS'
00:45:50,821 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
00:45:51,409 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=XARefDataDevDS' to JNDI name 'java:XARefDataDevDS'
00:45:51,797 INFO [JBossASKernel] Created KernelDeployment for: NotificationMailMDB-1.1.jar
00:45:51,803 INFO [JBossASKernel] installing bean: jboss.j2ee:jar=NotificationMailMDB-1.1.jar,name=MessageDispatcherBean,service=EJB3
00:45:51,803 INFO [JBossASKernel] with dependencies:
00:45:51,803 INFO [JBossASKernel] and demands:
00:45:51,803 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
00:45:51,803 INFO [JBossASKernel] and supplies:
00:45:51,803 INFO [JBossASKernel] jndi:null
00:45:51,803 INFO [JBossASKernel] Class:javax.jms.MessageListener
00:45:51,803 INFO [JBossASKernel] Added bean(jboss.j2ee:jar=NotificationMailMDB-1.1.jar,name=MessageDispatcherBean,service=EJB3) to KernelDeployment of: NotificationMailMDB-1.1.jar
00:45:51,907 INFO [EJBContainer] STARTED EJB: com.symyx.dg3.ui.server.notification.MessageDispatcherBean ejbName: MessageDispatcherBean
00:45:52,008 WARN [JmsActivation] Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@1f0f176(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@1d5d4e5 destination=/queue/NotificationMailQueue destinationType=javax.jms.Queue tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
javax.naming.NameNotFoundException: queue not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
at org.jnp.server.NamingServer.getObject(NamingServer.java:785)
at org.jnp.server.NamingServer.lookup(NamingServer.java:396)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:726)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
at javax.naming.InitialContext.lookup(InitialContext.java:409)
at org.jboss.util.naming.Util.lookup(Util.java:222)
at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQDestination(AbstractDLQHandler.java:106)
at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:82)
at org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:413)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:351)
at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:729)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
Below is my destinations-service.xml located at server/all/deploy/messaging
<?xml version="1.0" encoding="UTF-8"?>
<!--
Messaging Destinations deployment descriptor.
$Id: destinations-service.xml 85945 2009-03-16 19:45:12Z dimitris@jboss.org $
-->
<server>
<!--
The Default Dead Letter Queue. This destination is a dependency of an EJB MDB container.
-->
<mbean code="org.jboss.jms.server.destination.QueueService"
name="jboss.messaging.destination:service=Queue,name=DLQ"
xmbean-dd="xmdesc/Queue-xmbean.xml">
<depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
<depends>jboss.messaging:service=PostOffice</depends>
</mbean>
<!--
The Default Expiry Queue.
-->
<mbean code="org.jboss.jms.server.destination.QueueService"
name="jboss.messaging.destination:service=Queue,name=ExpiryQueue"
xmbean-dd="xmdesc/Queue-xmbean.xml">
<depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
<depends>jboss.messaging:service=PostOffice</depends>
</mbean>
</server>
below is my messaging-service.xml
<?xml version="1.0" encoding="UTF-8"?>
<!--
The JBoss Messaging service deployment descriptor.
$Id: messaging-service.xml 85945 2009-03-16 19:45:12Z dimitris@jboss.org $
-->
<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 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 destinatin 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>
<attribute name="StrictTck">false</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>
-->
<!-- The name of the server aspects configuration resource
<attribute name="ServerAopConfig">aop/jboss-aop-messaging-server.xml</attribute>
-->
<!-- The name of the client aspects configuration resource
<attribute name="ClientAopConfig">aop/jboss-aop-messaging-client.xml</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>
<depends optional-attribute-name="SecurityStore"
proxy-type="org.jboss.jms.server.SecurityStore">jboss.messaging:service=SecurityStore</depends>
</mbean>
</server>
What am I missing?
Appreciate your help.
Regards
Naveen