Nitesh Mehta [https://community.jboss.org/people/niteshmehta] created the discussion "Re: Problem upgrading to JBoss Messaging from 1.4.3 to 1.4.5 in JBoss 5.1" To view the discussion, visit: https://community.jboss.org/message/777523#777523 -------------------------------------------------------------- OK, I thing I got it. Although Code of org.jboss.jms.server.ServerPeer class look almost similar But when I compared  /xmdesc/ServerPeer-xmbean.xml file I found that   <attribute access="read-write" getMethod="getSecurityStore" setMethod="setSecurityStore">       <description>The SecurityStore implementation for the server.</description>       <name>SecurityStore</name> <type>org.jboss.jms.server.SecurityStore</type>    </attribute> Does not exist in JBM 1.4.5 Whereas two new attributes    <attribute access="read-write" getMethod="getSecurityDomain" setMethod="setSecurityDomain"> <description>The Security Domain to be used by the Server Peer</description> <name>SecurityDomain</name> <type>java.lang.String</type>    </attribute>    <attribute access="read-write" getMethod="getDefaultSecurityConfig" setMethod="setDefaultSecurityConfig"> <description>The Security config to use when the destination does not supply any</description> <name>DefaultSecurityConfig</name> <type>org.w3c.dom.Element</type>    </attribute> has been added. These two attributes (DefaultSecurityConfig, SecurityDomain ) was part of SecurityStore bean @see SecurityStore bean above. I copied these two entries directly into ServerPeer mbean Now myServerPeer mbean  looks something like <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">10000</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>       <attribute name="SuckerPassword">${queues.database.password}</attribute>             <attribute name="SecurityDomain">messaging</attribute>             <attribute name="DefaultSecurityConfig">                      <![CDATA[             <security>                <role name="guest" read="true" write="true" create="true"/>             </security>          ]]>             </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>jboss.messaging:service=SecurityStore</depends>    </mbean> -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/777523#777523] Start a new discussion in JBoss Messaging at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]