-
Bug
-
Resolution: Done
-
Major
-
EAP 5.0.0
-
JBoss EAP 5.x
-
Workaround Exists
-
-
-
Documented as Resolved Issue
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>
- relates to
-
JBTM-394 support JBossAS 5.0 service binding manager
- Closed