[jboss-user] [JBoss Messaging] - Re: Create Queue Connection Error
b16d
do-not-reply at jboss.com
Fri Apr 3 08:27:08 EDT 2009
thanks for your help. My server is on my computeur. I am using the default server. i give all xml files who are containes in the folder "messaging" :
connection-factories-service.xml
<?xml version="1.0" encoding="UTF-8"?>
|
| <!--
| Messaging Destinations deployment descriptor.
|
| $Id: destinations-service.xml 81998 2008-12-03 06:46:29Z scott.stark at jboss.org $
| -->
|
| <server>
|
| I am using jbpm, jdpl
|
| <!--
| 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>
|
|
| <mbean code="org.jboss.jms.server.destination.QueueService"
| name="jboss.messaging.destination:service=Queue,name=toto"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| </mbean>
| </server>
destinations-service.xml
<?xml version="1.0" encoding="UTF-8"?>
|
| <!--
| Messaging Destinations deployment descriptor.
|
| $Id: destinations-service.xml 81998 2008-12-03 06:46:29Z scott.stark at 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>
|
|
| <mbean code="org.jboss.jms.server.destination.QueueService"
| name="jboss.messaging.destination:service=Queue,name=toto"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| </mbean>
| </server>
hsqldb-persistence-service.xml
<?xml version="1.0" encoding="UTF-8"?>
|
| <!--
| Hypersonic persistence deployment descriptor.
|
| DO NOT USE HYPERSONIC IN PRODUCTION or in a clustered environment- Hypersonic does not have transaction isolation
|
| $Id: hsqldb-persistence-service.xml 3339 2007-11-16 20:48:08Z clebert.suconic at jboss.com $
| -->
|
| <server>
|
| <!-- Persistence Manager MBean configuration
| ======================================= -->
|
| <mbean code="org.jboss.messaging.core.jmx.JDBCPersistenceManagerService"
| name="jboss.messaging:service=PersistenceManager"
| xmbean-dd="xmdesc/JDBCPersistenceManager-xmbean.xml">
|
| <depends>jboss.jca:service=DataSourceBinding,name=DefaultDS</depends>
|
| <depends optional-attribute-name="TransactionManager">jboss:service=TransactionManager</depends>
|
| <!-- The datasource to use for the persistence manager -->
|
| <attribute name="DataSource">java:/DefaultDS</attribute>
|
| <!-- If true will attempt to create tables and indexes on every start-up -->
|
| <attribute name="CreateTablesOnStartup">true</attribute>
|
| <!-- If true then will use JDBC batch updates -->
|
| <attribute name="UsingBatchUpdates">false</attribute>
|
| <!-- The maximum number of parameters to include in a prepared statement -->
|
| <attribute name="MaxParams">500</attribute>
| </mbean>
|
| <!-- Messaging Post Office MBean configuration
| ========================================= -->
|
| <mbean code="org.jboss.messaging.core.jmx.MessagingPostOfficeService"
| name="jboss.messaging:service=PostOffice"
| xmbean-dd="xmdesc/MessagingPostOffice-xmbean.xml">
|
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
|
| <depends>jboss.jca:service=DataSourceBinding,name=DefaultDS</depends>
|
| <depends optional-attribute-name="TransactionManager">jboss:service=TransactionManager</depends>
|
| <!-- The name of the post office -->
|
| <attribute name="PostOfficeName">JMS post office</attribute>
|
| <!-- The datasource used by the post office to access it's binding information -->
|
| <attribute name="DataSource">java:/DefaultDS</attribute>
|
| <!-- If true will attempt to create tables and indexes on every start-up -->
|
| <attribute name="CreateTablesOnStartup">true</attribute>
|
| <!-- This post office is NON CLUSTERED - do not use clustering with Hypersonic!! -->
|
| <attribute name="Clustered">false</attribute>
| </mbean>
|
| <!-- Messaging JMS User Manager MBean config
| ======================================= -->
|
| <mbean code="org.jboss.jms.server.plugin.JDBCJMSUserManagerService"
| name="jboss.messaging:service=JMSUserManager"
| xmbean-dd="xmdesc/JMSUserManager-xmbean.xml">
|
| <depends>jboss.jca:service=DataSourceBinding,name=DefaultDS</depends>
|
| <depends optional-attribute-name="TransactionManager">jboss:service=TransactionManager</depends>
|
| <attribute name="DataSource">java:/DefaultDS</attribute>
|
| <attribute name="CreateTablesOnStartup">true</attribute>
|
| <attribute name="SqlProperties"><![CDATA[
| POPULATE.TABLES.1 = INSERT INTO JBM_USER (USER_ID, PASSWD) VALUES ('guest', 'guest')
| POPULATE.TABLES.2 = INSERT INTO JBM_USER (USER_ID, PASSWD) VALUES ('j2ee', 'j2ee')
| POPULATE.TABLES.3 = INSERT INTO JBM_USER (USER_ID, PASSWD, CLIENTID) VALUES ('john', 'needle', 'DurableSubscriberExample')
| POPULATE.TABLES.4 = INSERT INTO JBM_USER (USER_ID, PASSWD) VALUES ('nobody', 'nobody')
| POPULATE.TABLES.5 = INSERT INTO JBM_USER (USER_ID, PASSWD) VALUES ('dynsub', 'dynsub')
| POPULATE.TABLES.6 = INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('guest','guest')
| POPULATE.TABLES.7 = INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('j2ee','guest')
| POPULATE.TABLES.8 = INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('john','guest')
| POPULATE.TABLES.9 = INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('subscriber','john')
| POPULATE.TABLES.10 = INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('publisher','john')
| POPULATE.TABLES.11 = INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('publisher','dynsub')
| POPULATE.TABLES.12 = INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('durpublisher','john')
| POPULATE.TABLES.13 = INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('durpublisher','dynsub')
| POPULATE.TABLES.14 = INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('noacc','nobody')
| ]]></attribute>
| </mbean>
|
| </server>
jms-ds.xml
<?xml version="1.0" encoding="UTF-8"?>
|
| <connection-factories>
|
| <!-- ==================================================================== -->
| <!-- JMS Stuff -->
| <!-- ==================================================================== -->
|
| <!--
| The JMS provider loader. Currently pointing to a non-clustered ConnectionFactory. Need to
| be replaced with a clustered non-load-balanced ConnectionFactory when it becomes available.
| See http://jira.jboss.org/jira/browse/JBMESSAGING-843.
| -->
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| name="jboss.messaging:service=JMSProviderLoader,name=JMSProvider">
| <attribute name="ProviderName">DefaultJMSProvider</attribute>
| <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
| <attribute name="FactoryRef">java:/XAConnectionFactory</attribute>
| <attribute name="QueueFactoryRef">java:/XAConnectionFactory</attribute>
| <attribute name="TopicFactoryRef">java:/XAConnectionFactory</attribute>
| </mbean>
|
| <!-- JMS XA Resource adapter, use this to get transacted JMS in beans -->
| <tx-connection-factory>
| <jndi-name>JmsXA</jndi-name>
| <xa-transaction/>
| <rar-name>jms-ra.rar</rar-name>
| <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
| <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
| <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/DefaultJMSProvider</config-property>
| <max-pool-size>20</max-pool-size>
| <security-domain-and-application>JmsXARealm</security-domain-and-application>
| <depends>jboss.messaging:service=ServerPeer</depends>
| </tx-connection-factory>
|
| </connection-factories>
|
legacy-service.xml
<?xml version="1.0" encoding="UTF-8"?>
| <!--
| Messaging Destinations deployment descriptor.
|
| $Id: destinations-service.xml 927 2006-05-03 01:51:14Z ovidiu $
| -->
|
| <server>
| <mbean code="org.jboss.mq.server.jmx.DummyDestMgr"
| name="jboss.mq:service=DestinationManager">
| <depends>jboss.messaging:service=ServerPeer</depends>
| </mbean>
| <mbean code="org.jboss.mq.server.jmx.DummySecurityMgr"
| name="jboss.mq:service=SecurityManager" />
|
| </server>
|
messaging-jboss-beans.xml
<?xml version="1.0" encoding="UTF-8"?>
|
| <!--
| Messaging beans
| $Id: messaging-beans.xml 68282 2007-12-14 13:43:52Z alex.loubyansky at jboss.com $
| -->
| <deployment xmlns="urn:jboss:bean-deployer:2.0">
|
| <!-- messaging application-policy definition -->
| <application-policy xmlns="urn:jboss:security-beans:1.0" name="messaging">
| <authentication>
| <login-module code="org.jboss.security.auth.spi.DatabaseServerLoginModule" flag="required">
| <module-option name="unauthenticatedIdentity">guest</module-option>
| <module-option name="dsJndiName">java:/DefaultDS</module-option>
| <module-option name="principalsQuery">SELECT PASSWD FROM JBM_USER WHERE USER_ID=?</module-option>
| <module-option name="rolesQuery">SELECT ROLE_ID, 'Roles' FROM JBM_ROLE WHERE USER_ID=?</module-option>
| </login-module>
| </authentication>
| </application-policy>
|
| <bean name="SecurityStore" class="org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore">
| <!-- default security configuration -->
| <property name="defaultSecurityConfig">
| <![CDATA[
| <security>
| <role name="guest" read="true" write="true" create="true"/>
| </security>
| ]]>
| </property>
| <property name="suckerPassword">CHANGE ME!!</property>
| <property name="securityDomain">messaging</property>
| <property name="securityManagement"><inject bean="JNDIBasedSecurityManagement"/></property>
| <!-- @JMX annotation to export the management view of this bean -->
| <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.messaging:service=SecurityStore",exposedInterface=org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStoreMBean.class)</annotation>
| </bean>
|
| <bean name="QueueTemplate" class="org.jboss.profileservice.management.templates.JmsDestinationTemplate">
| <property name="info"><inject bean="QueueTemplateInfo"/></property>
| </bean>
| <bean name="QueueTemplateInfo"
| class="org.jboss.profileservice.management.templates.JmsDestinationTemplateInfo">
| <constructor>
| <parameter>QueueTemplate</parameter>
| <parameter>A template for JMS queue *-service.xml deployments</parameter>
| <parameter>queue</parameter>
| </constructor>
| </bean>
|
| <bean name="TopicTemplate" class="org.jboss.profileservice.management.templates.JmsDestinationTemplate">
| <property name="info"><inject bean="TopicTemplateInfo"/></property>
| </bean>
| <bean name="TopicTemplateInfo"
| class="org.jboss.profileservice.management.templates.JmsDestinationTemplateInfo">
| <constructor>
| <parameter>TopicTemplate</parameter>
| <parameter>A template for JMS topic *-service.xml deployments</parameter>
| <parameter>topic</parameter>
| </constructor>
| </bean>
|
| <bean name="QueueMODefinition" class="org.jboss.jms.server.destination.QueueMODefinition">
| <constructor>
| <parameter><inject bean="ManagedObjectFactory" /></parameter>
| </constructor>
| </bean>
|
| <bean name="TopicMODefinition" class="org.jboss.jms.server.destination.TopicMODefinition">
| <constructor>
| <parameter><inject bean="ManagedObjectFactory" /></parameter>
| </constructor>
| </bean>
|
| </deployment>
|
messaging-service.xml
<?xml version="1.0" encoding="UTF-8"?>
|
| <!--
| The JBoss Messaging service deployment descriptor.
|
| $Id: messaging-service.xml 3880 2008-03-14 15:55:42Z timfox $
| -->
|
| <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>
|
remoting-bisocket-service.xml
<?xml version="1.0" encoding="UTF-8"?>
|
| <!--
| Standard bisocket-based Remoting service deployment descriptor.
|
| $Id: remoting-bisocket-service.xml 3981 2008-03-28 18:00:41Z timfox $
| -->
|
| <server>
|
| <!-- Standard bisocket connector - the bisocket transport only opens connection from client->server
| so can be used with firewalls where only outgoing connections are allowed.
| For examples of HTTP and SSL transports see docs/examples -->
| <mbean code="org.jboss.remoting.transport.Connector"
| name="jboss.messaging:service=Connector,transport=bisocket"
| display-name="Bisocket Transport Connector">
| <attribute name="Configuration">
| <config>
| <invoker transport="bisocket">
|
| <!-- There should be no reason to change these parameters - warning!
| Changing them may stop JBoss Messaging working correctly -->
| <attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
| <attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
| <attribute name="dataType" isParam="true">jms</attribute>
| <attribute name="socket.check_connection" isParam="true">false</attribute>
| <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
| <attribute name="serverBindPort">${jboss.messaging.connector.bisocket.port:4457}</attribute>
| <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>
| <attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>
|
| <attribute name="numberOfCallRetries" isParam="true">1</attribute>
| <attribute name="pingFrequency" isParam="true">214748364</attribute>
| <attribute name="pingWindowFactor" isParam="true">10</attribute>
| <attribute name="onewayThreadPool">org.jboss.jms.server.remoting.DirectThreadPool</attribute>
| <!-- End immutable parameters -->
|
| <attribute name="stopLeaseOnFailure" isParam="true">true</attribute>
|
| <!-- Periodicity of client pings. Server window by default is twice this figure -->
| <attribute name="clientLeasePeriod" isParam="true">10000</attribute>
| <attribute name="validatorPingPeriod" isParam="true">10000</attribute>
| <attribute name="validatorPingTimeout" isParam="true">5000</attribute>
| <attribute name="registerCallbackListener">false</attribute>
|
| <attribute name="timeout" isParam="true">0</attribute>
|
| <!-- Number of seconds to wait for a connection in the client pool to become free -->
| <attribute name="connectionWait" isParam="true">10</attribute>
|
| <!-- Max Number of connections in client pool. This should be significantly higher than
| the max number of sessions/consumers you expect -->
| <attribute name="JBM_clientMaxPoolSize" isParam="true">200</attribute>
|
| <!-- The maximum time to wait before timing out on trying to write a message to socket for delivery -->
| <attribute name="callbackTimeout">10000</attribute>
|
| <!-- Use these parameters to specify values for binding and connecting control connections to
| work with your firewall/NAT configuration
| <attribute name="secondaryBindPort">xyz</attribute>
| <attribute name="secondaryConnectPort">abc</attribute>
| -->
|
| </invoker>
| <handlers>
| <handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
| </handlers>
| </config>
| </attribute>
| </mbean>
|
| </server>
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223278#4223278
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223278
More information about the jboss-user
mailing list