jboss-ejb-client.properties bug in latest nightly?

[markus78]

I just upgraded my JBoss to the latest nightly and now only the first receiver in the list is used in jboss-ejb-client.properties?

That is i get javax.ejb.NoSuchEJBException for beans deployed on the second server in this example, "two" is never added as an receiver it seems...

remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false remote.connections=one, two remote.connection.one.host=localhost remote.connection.one.port=6999 remote.connection.one.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false remote.connection.two.host=localhost remote.connection.two.port=7999 remote.connection.two.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false

But if I specify two only those beans are found... is this a known problem?

BR

/Markus

[markus78]

Okej, I figured it out seems like the property jboss.host.name cannot be the same for 2 servers on the same machine .. so modifying jboss.host.name for server TWO above fixed the problem,

a bit strange that I have to modify the host.name property, there is also an jboss.node.name property would that not be a better property to use for this?

/Markus

[jaikiran]

markus78 wrote:

a bit strange that I have to modify the host.name property, there is also an jboss.node.name property would that not be a better property to use for this?

We don't use jboss.host.name. jboss.node.name is the right property to set when running two instances on the same machine.

[markus78]

Okey, are you sure? , when we used debug logging we could see that the ejb client code rejected the second ejb receiver with the node name set to our "jboss-host-name" property, the jboss-node-name is equal to the server-name set first in the standalone.xml right? our unittests did not work when changing server name ( verified that jboss.node.name changed accordingly via the jboss_cli )... but when changing "host-name" the tests passed and we could se in the debug printouts that the "node-name" changed...

[jaikiran]

markus78 wrote:

Okey, are you sure? , when we used debug logging we could see that the ejb client code rejected the second ejb receiver with the node name set to our "jboss-host-name" property, the jboss-node-name is equal to the server-name set first in the standalone.xml right?

Without knowing which property you are referring to, I can't be sure What's jboss-host-name property? Where do you set it? You don't have to change it at all. Just change -Djboss.node.name on the server side.

[markus78]

Thanks for your time & answers, I went back and did it over again, and -Djboss.node.name works fine, not sure what went wrong the first time around!

BR

/Markus