The secondaryBindPort is not specified in $JBOSS_HOME$/server/$PROFILE/deploy/messaging/remoting-bisocket-service.xml, it is commented out. And it cannot be configured from the Service Binding Manager

The SBM bindings-jboss-beans.xml and remoting-bisocket-service.xml should be changed such as below to allow the port to be configured from the SBM.

Add these to <JBOSS_HOME>/server/<profile>/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml:
In the "org.jboss.services.binding.ServiceBindingMetadata" elementClass for the StandardBindings"StandardBindings" bean:

<bean class="org.jboss.services.binding.ServiceBindingMetadata">
<property name="serviceName">jboss.messaging:service=Connector,transport=bisocket</property>
<property name="bindingName">secondaryBindPort</property>
<property name="port">4458</property>
<property name="description">Secondary Socket for JBoss Messaging 1.x</property>
</bean>

In the "SystemPropertyBinder" bean:

<bean class="org.jboss.services.binding.SystemPropertyBinding">
<constructor>
<parameter>jboss.messaging.connector.bisocket.secondaryport</parameter>
<parameter class="int">
<value-factory bean="ServiceBindingManager" method="getIntBinding">
<parameter>jboss.messaging:service=Connector,transport=bisocket</parameter>
<parameter>secondaryBindPort</parameter>
</value-factory>
</parameter>
</constructor>
</bean>

Specify this in <JBOSS_HOME>/server/<profile>/deploy/messaging/remoting-bisocket-service.xml:

<attribute name="secondaryBindPort">${jboss.messaging.connector.bisocket.secondaryport}</attribute>

Of course, "4458" can be any valid port.