Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-996

Discrepancies between port schemes in sample-bindings.xml

XMLWordPrintable

    • Release Notes

      Discrepancies exist between the port schemes defined in sample-bindings.xml.

      1) The remoting connectors are inserted in different places in ports definition sections which makes comparing the sections more difficult than it needs to be.
      Defining everything in the same order would make it easier to compare the various ports definition sections.

      2) The "ports-03" section is missing the "EJB remoting connector" and the "remoting connector" sections completely (not just an ordering difference).

      3) "mq" is used in the name property of the HAJNDIJMSProvider instead of "jms." One example of this is:

      ===== "ports-default" section looks OK:

      <!-- ********************* hajndi-jms-ds.xml **************** -->

      <!-- The JMS provider loader -->
      <service-config name="jboss.jms:service=JMSProviderLoader,name=HAJNDIJMSProvider"
      delegateClass="org.jboss.services.binding.AttributeMappingDelegate">

      ===== "ports-01" section looks wrong ("mq" used):
      <!-- ********************* hajndi-jms-ds.xml **************** -->

      <!-- The JMS provider loader -->
      <service-config name="jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider"
      delegateClass="org.jboss.services.binding.AttributeMappingDelegate">

      4) The ports-01, ports-02, and ports-03 schemes define the "timeout" attribute twice in this section:

      <!-- ********************* jboss messaging ********************** -->

      <service-config name="jboss.messaging:service=Connector,transport=bisocket"
      delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
      <delegate-config>
      <attribute name="Configuration"><![CDATA[
      <config>
      <invoker transport="bisocket">
      <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="timeout" isParam="true">0</attribute>
      <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
      <attribute name="serverBindPort">4557</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>
      <attribute name="stopLeaseOnFailure" isParam="true">true</attribute>
      <attribute name="clientLeasePeriod" isParam="true">10000</attribute>
      <attribute name="timeout" isParam="true">0</attribute>
      <attribute name="numberOfRetries" isParam="true">10</attribute>
      <attribute name="JBM_clientMaxPoolSize" isParam="true">200</attribute>
      <attribute name="callbackTimeout">10000</attribute>
      </invoker>
      <handlers>
      <handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
      </handlers>
      </config>
      ]]></attribute>
      </delegate-config>
      <binding port="4557"/>
      </service-config>

            dandread1@redhat.com Dimitrios Andreadis
            rhn-support-jbertram Justin Bertram
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: