0 Replies Latest reply on Jun 18, 2007 7:05 AM by Sean Radford

    Binding Manager

    Sean Radford Novice

      Hi,

      In the sample binding manager config file: docs/examples/binding-manager/sample-bindings.xml the sections for the JMSProviderLoader don't change the jnp.discoveryPort (it is always 1102). Is this correct?

      Thanks,

      Sean

       <service-config name="jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider"
       delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
       <!--
       MAKE SURE java.naming.provider.url
       PORT IS SAME AS HA-JNDI ABOVE !!!
       -->
       <delegate-config>
       <attribute name="Properties"><![CDATA[
       java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
       java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
       java.naming.provider.url=${jboss.bind.address:localhost}:1100
       jnp.disableDiscovery=false
       jnp.partitionName=${jboss.partition.name:DefaultPartition}
       jnp.discoveryGroup=${jboss.partition.udpGroup:230.0.0.4}
       jnp.discoveryPort=1102
       jnp.discoveryTTL=16
       jnp.discoveryTimeout=5000
       jnp.maxRetries=1
       ]]>
       </attribute>
       </delegate-config>
       <!-- NOTE: YOU MUST ADD THIS ELEMENT, BUT THE VALUE DOESN'T MATTER
       BE SURE THE CORRECT VALUE IS IN java.naming.provider.url ABOVE -->
       <binding port="1100"/>
       </service-config>