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>
|
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262478#4262478
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262478
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
