The auto port-assignment and token resolution features have been in for
a month.
The Replication code did NOT take advantage of it so you were forced to
pass in the ports explicitly.
I modified the Replication code -- so it now works correctly.
You don't need to send in those annoying port assignment
system-property's anymore.
here is a comment from the code I changed:
//TODO : The following piece of code is kludge - pending config API changes for tokens in MS2
On 7/19/2010 6:10 AM, Hong Zhang wrote:
> Hi, Byron
> I don't know the details about this. I was just told that I should
> continue passing in the port information to the create instance
> command so the command replication framework can get the port
> information and replicate properly.
> I will let Vijay share more details on this. Probably something
> related to what you have fixed for this issue:
>
> https://glassfish.dev.java.net/issues/show_bug.cgi?id=12675
>
>
> Thanks,
>
> - Hong
>
> On 7/18/2010 2:02 AM, Byron Nevins wrote:
>> What is the issue number for the bug in token resolution? I didn't
>> deliver that feature but I use it and can help you use it properly if
>> need be.
>>
>> Note that it is impossible to get Tokens resolved for a server
>> instance from inside DAS without doing something special. See below
>> for a sample.
>>
>> The server instance itself will get its tokens resolved
>> automatically. So, for instance, the ports will all be resolved as
>> expected and automatically.
>>
>> Sample code (thanks to Jennifer Chou) for resolving on behalf of an
>> instance while running in DAS:
>>
>> PropertyResolver resolver = new PropertyResolver(domain,
>> server.getName());
>> return resolver.getPropertyValue(portString);
>>
>>
>> On 7/17/2010 10:51 PM, Byron Nevins wrote:
>>> Hi Hong,
>>>
>>> The port replication works just fine. There have been zero bugs
>>> reported against it in the month since it was introduced in MS2.
>>> The feature is used and exercised a LOT by the clustering
>>> infrastructure team -- with no reported problems.
>>>
>>> Here is an example of what it does:
>>>
>>> <server node="vaio" node-agent-ref="vaio" name="i2"
>>> config-ref="c1-config">
>>> <property name="rendezvousOccurred" value="true" />
>>> <system-property name="JMX_SYSTEM_CONNECTOR_PORT" value="28687" />
>>> <system-property name="JMS_PROVIDER_PORT" value="27677" />
>>> <system-property name="ASADMIN_LISTENER_PORT" value="24849" />
>>> <system-property name="HTTP_LISTENER_PORT" value="28081" />
>>> <system-property name="IIOP_LISTENER_PORT" value="23701" />
>>> <system-property name="IIOP_SSL_LISTENER_PORT" value="23821" />
>>> <system-property name="HTTP_SSL_LISTENER_PORT" value="28182" />
>>> <system-property name="IIOP_SSL_MUTUALAUTH_PORT" value="23921" />
>>> </server>
>>> </servers>
>>>
>>> Thanks,
>>>
>>> Byron
>>>
>>> n 7/17/2010 9:02 PM, Hong Zhang wrote:
>>>> Hi, Byron
>>>> Even though this feature (automatic port determination) was in,
>>>> from recent conversation with Vijay and recent experiments (a
>>>> couple days ago), my understanding is we still need to pass in the
>>>> port information explicitly when creating instances so the command
>>>> replication will work as expected (due to a bug in token resolution)?
>>>> Thanks,
>>>>
>>>> - Hong
>>>>
>>>> On 7/17/2010 2:25 PM, Byron Nevins wrote:
>>>>> By request I'm announcing a feature that was released with MS2
>>>>> (3-4 weeks ago).
>>>>>
>>>>> You don't need to specify any ports as system properties when you
>>>>> create instances. We will do that for you automatically.
>>>>>
>>>>> You still are allowed to specify them if you want specific ports,
>>>>> but you don't have to. THis is especially handy if you are a
>>>>> developer and create instances frequently and don't care what the
>>>>> port values are.
>>>>>
>>>>> OLD:
>>>>> asadmin create-local-instance --cluster c1 --systemproperties
>>>>> HTTP_LISTENER_PORT=18080:HTTP_SSL_LISTENER_PORT=18181:
>>>>> IIOP_SSL_LISTENER_PORT=13800:
>>>>> IIOP_LISTENER_PORT=13700:JMX_SYSTEM_CONNECTOR_PORT=17676:
>>>>> IIOP_SSL_MUTUALAUTH_PORT=13801:JMS_PROVIDER_PORT=18686:ASADMIN_LISTENER_PORT=14848
>>>>> in1
>>>>>
>>>>> New:
>>>>> asadmin create-local-instance --cluster c1 in1
>>>>>
>>>>> ========================
>>>>>
>>>>> While I'm announcing things -- restart-instance is now supported:
>>>>>
>>>>> asadmin restart-instance
>>>>>
>>>>> And you can turn on (or off) JPDA debugging like so with a restart:
>>>>>
>>>>> asadmin restart-instance --debug
>>>>> asadmin restart-domain --debug=false
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
--
Byron Nevins - Oracle Corporation
Home: 650-359-1290
Cell: 650-784-4123
Sierra: 209-295-2188