On Jul 16, 2007, at 1:11 PM, Mike Wynholds wrote:
I am running a cluster of Resin servers on 3.1.1. I have two
servers in my app-tier cluster, app-a and app-b. When I access the
following JMX object:
resin:type=Cluster,name=app-tier
using jconsole, the “Servers” attribute has an array of ObjectNames
of length 1. It only contains app-b.
However, both of the following objects are directly available in JMX:
resin:type=ServerConnector,name=app-a
resin:type=ServerConnector,name=app-b
and when I hit /caucho-status they are both up.
so why does the app-tier cluster report only a single server? I am
connected to the JMX server on app-a. does it not include itself
in the Servers attribute, or is this a bug, or am I doing something
wrong? I assume it’s not an order of operations thing, ie: I bring
app-a up, then app-b. when I then access app-a via JMX, that
cluster mxbean should be updated, right?
It may just be that we tried to be a little too clever on the
ServerConnector.
The idea was that ServerConnector is a connection to a peer server.
Since Resin doesn't connect to itself, there's no administration
information on the app-a to app-a connection, so it doesn't make
sense returning itself.
We might want to revisit that, so the Servers also returns a bogus
ServerConnector to itself.
-- Scott
..mike..
_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
