Tom Mueller wrote:
> Ken,
> The problem shows up if you have this situation:
>
> Within cluster c1, within instance i1, you want to look up a port for
> instance i2.
>
> Currently, i1's domain.xml will not have any data about instance i2
> (until 12397 is fixed).
> Tom
If the information is not even AVAILABLE in i1's domain.xml, then 12397
is a P1/P2 blocking
all work on IIOP FOLB until it is fixed. IIOP FOLB is highly dependent
on having an accurate
view of the cluster's configuration at each instance.
By the way, how does code running on an instance determine which cluster
it's in?
Thanks,
Ken.
>
>
> On 7/6/2010 5:14 PM, Ken wrote:
>> Joseph Fialli wrote:
>>> Ken,
>>>
>>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=12397
>>>
>>> I would recommend that you push for this to be fixed for M3.
>>>
>>> -Joe
>>>
>> Is there really a problem here? What I need to do is resolved the
>> values of the port
>> in the config element in the context of the appropriate server object
>> (using something
>> like PropertyResolver), so that the SystemProperty instances in the
>> server are applied
>> to the port value (see the attached email).
>>
>> From the bug, it looks like GF 3.1 will support multiple clusters in
>> domain.xml.
>> So how do I determine which cluster my instance is running in? I
>> think I've got
>> a lot of this figured out, but I'm still waiting to here from the
>> admin team about
>> the first email message.
>>
>> Thanks,
>>
>> Ken.
>>