« Return to Thread: Re: [cargo-dev] [jira] Created: (CARGO-849) Change to

Re: Re: [cargo-dev] [jira] Created: (CARGO-849) Change <cargo.rmi.port> to <cargo.naming.port>

by snicoll :: Rate this Message:

| View in Thread

Looking at that again, the code snippet is weird.

First, if one wants to change the RMI port it needs to go to server/conf/jboss-service.xml

Then, there is no possible confusion. Here's the content for this bean (4.2.3)

<mbean code="org.jboss.naming.NamingService"

name="jboss:service=Naming"

xmbean-dd="resource:xmdesc/NamingService-xmbean.xml">

<!-- The call by value mode. true if all lookups are unmarshalled using

the caller's TCL, false if in VM lookups return the value by reference.

-->

<attribute name="CallByValue">false</attribute>

<!-- The listening port for the bootstrap JNP service. Set this to -1

to run the NamingService without the JNP invoker listening port.

-->

<!-- The bootstrap JNP server bind address. This also sets the default

RMI service bind address. Empty == all addresses

-->

<attribute name="BindAddress">${jboss.bind.address}</attribute>

<!-- The RMI service bind address. Empty == all addresses

-->

<attribute name="RmiBindAddress">${jboss.bind.address}</attribute>

<depends optional-attribute-name="LookupPool"

proxy-type="attribute">jboss.system:service=ThreadPool</depends>

<!-- An example of using the unifed invoker as the transport.

<depends optional-attribute-name="InvokerProxyFactory"

proxy-type="attribute">jboss:service=proxyFactory,type=unified,target=Naming</depends>

-->

<depends optional-attribute-name="Naming"

proxy-type="attribute">jboss:service=NamingBeanImpl</depends>

</mbean>

To me it looks like the user got confused and took the wrong file. Type JBoss rmi port on google and you'll see

On Tue, Sep 28, 2010 at 11:15 PM, S. Ali Tokmen <nospam@...> wrote:

Hello Matt (and other CARGO users that use JBoss a lot)

Any comments on this JIRA ticket?

Cheers

S. Ali Tokmen
http://ali.tokmen.com/

GSM (fr): +33 66 43 00 555 [Orange]
GSM (tr): +90 555 266 52 73 [Avea]

My AIM, ICQ, MSN Messenger and Yahoo IM
contact details are on http://contact.ali.tokmen.com

On 22.09.2010 10:07, Griboval Philippe (JIRA) wrote:
> Change <cargo.rmi.port> to <cargo.naming.port>
> ----------------------------------------------
>
> Key: CARGO-849
> URL: http://jira.codehaus.org/browse/CARGO-849
> Project: Cargo
> Issue Type: Improvement
> Components: JBoss
> Affects Versions: 1.0.3
> Reporter: Griboval Philippe
> Priority: Minor
>
>
> 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...
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

« Return to Thread: Re: [cargo-dev] [jira] Created: (CARGO-849) Change to