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

Unable to configure the JBoss Transactions (Arjuna) socketProcessIdPort port in the Service Binding Manager

    Details

    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      Manually do the change mentioned in the description.

      Show
      Manually do the change mentioned in the description.
    • Release Notes Text:
      Hide
      In earlier versions of EAP 5 it was found that although the <filename>binding-jboss-beans.xml</filename> file specified the SocketProcessId, this was not honored by the <filename>transaction-jboss-beans.xml</filename> file.

      This issue has been resolved in this release by using the Service Binding Manager value-factory instead.
      Show
      In earlier versions of EAP 5 it was found that although the <filename>binding-jboss-beans.xml</filename> file specified the SocketProcessId, this was not honored by the <filename>transaction-jboss-beans.xml</filename> file. This issue has been resolved in this release by using the Service Binding Manager value-factory instead.
    • Release Notes Docs Status:
      Documented as Resolved Issue
    • Target Release:

      Description

      The $JBOSS_HOME/server/$PROFILE/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml specifies the SocketProcessId, however it is not used in the $JBOSS_HOME/server/$PROFILE/deploy/transaction-jboss-beans.xml

      <!-- JBossTS SocketProcessId. The address part is ignored,
      it will always use localhost/127.0.0.1. -->
      <bean class="org.jboss.services.binding.ServiceBindingMetadata">
      <property name="serviceName">TransactionManager</property>
      <property name="bindingName">socketProcessId</property>
      <property name="port">4714</property>
      <property name="description">Socket used to provide unique process id for JBossTS. The address configuration is ignored; will always use localhost/127.0.0.1</property>
      </bean>

      To fix it, the $JBOSS_HOME/server/$PROFILE/deploy/transaction-jboss-beans.xml should be changed to use the Service Binding Manager value-factory such as:

      Edit $JBOSS_HOME/server/$PROFILE/deploy/transaction-jboss-beans.xml

      Change the socketProcessIdPort property from:

      <property name="socketProcessIdPort">0</property>

      To:

      <property name="socketProcessIdPort">
      <value-factory bean="ServiceBindingManager"
      method="getIntBinding">
      <parameter>TransactionManager</parameter>
      <parameter>socketProcessId</parameter>
      </value-factory>
      </property>

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  istudens Ivo Studensky
                  Reporter:
                  bmaxwell Brad Maxwell
                  Writer:
                  Eva Kopalova
                • Votes:
                  2 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: