Details
-
Type:
Improvement
-
Status: Closed (View workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.0.3
-
Fix Version/s: 1.0.4
-
Component/s: Documentation, JBoss
-
Labels:None
Description
In the cargo maven plugin you have to set <cargo.rmi.port> in case of not using the default jboss port.
To know the port I have opened my jboss_home/server/default/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml and look for the rmi port.
I found this :
<bean class="org.jboss.services.binding.ServiceBindingMetadata">
<property name="serviceName">jboss:service=Naming</property>
<property name="bindingName">Port</property>
<property name="port">1299</property>
<property name="description">The listening socket for the Naming service</property>
</bean>
<bean class="org.jboss.services.binding.ServiceBindingMetadata">
<property name="serviceName">jboss:service=Naming</property>
<property name="bindingName">RmiPort</property>
<property name="port">1098</property>
<property name="description">Socket Naming service uses to receive RMI requests from client proxies</property>
</bean>
So I put 1098 for the <cargo.rmi.port> instead of the 1299...
I think cargo.rmi.port might be badly named...