Re: [jboss-as7-dev] UserTransaction used by remote clients
On Thursday 08 March 2012 12:24 AM, Wolf-Dieter Fink wrote:
===== Regarding node-name. =====
In standalone I supposed it is the name of jboss-ejb-client.properties
remote.connection.*default*.host=localhost
But I have to set it by -Djboss.node.name=<>.
Note that the "default" remote.connection.default is _not_ the
jboss.node.name of the server. It's just some random name you use for
identifying connections within the properties file. The way you use it is:
remote.connections=foo
which will indicate that you have a connection configuration for a
connection named foo. Later in the properties file you'll have:
remote.connection.foo.host=bar
So here you are configuring a connection named foo and setting its host
property to bar. So the "foo" is any random name of your choice. It will
play no other role than identifying the connection configuration for
that connection. It has no relation with jboss.node.name system property
from the server side.
The section for remote invoking EJB's note that a node name must be
set unique, but I did not see any problem if I start two instances
(same machine) without jboss.node.name?
Is here a default created?
The problem is "hidden". If you have 2 or more
instances on the same
machine and you don't use a unique jboss.node.name for each of these
instances and if your EJB client program lists both these servers within
the jboss-ejb-client.properties, then only one of them will be
registered within the EJB client context. The other registration will be
skipped because a EJB client context can't have more than 1 EJB receiver
with the same node name. So depending on your application deployments on
those instances, things may or may not work.
-Jaikiran