Hi Thorsten,
Thanks for your notes and guidelines. For now, I am incorporating all your
suggestions and updating my design doc accordingly. I am also going to
upload a ha-jboss user guide which would help users and community install
ha-jboss and use it.
I am also working on reformatting the code into the appropriate GDS template
in order to make integration of ha-jboss possible with OHAC but it might
take some time.
I would send a note to this alias once I have updated the above mentioned
document and your advice on that would be very helpful! :)
Regards,
Abhishek
On Thu, Feb 5, 2009 at 5:25 AM, Thorsten Frueauf
<Thorsten.Frueauf at sun.com>wrote:
> Hi Abhishek et al,
>
> first of all, thanks a lot for taking the time to go through the process
> setting up the HA JBOSS project page and coming up with a design document
> and a webrev with your agent code. This is really excellent!
>
> To finish the process I did click on the "endorse project" functionality of
> the HA Clusters community main page to mark the project accordingly, as such
> it is now fully endorsed by the HA Clusters community :)
>
> You already got some good feedback. I would like to add the following
> comments:
>
> - I saw you will consider to use the GDS template - and I support that idea
> :) But just for the record - it would also be totally OK to stay scdsbuilder
> based and provide the agent from the project page. So it depends on the
> level of integration into the OHAC gate that you seek.
>
> - If you would stay on an scdsbuilder based implementation, I would
> recommend to document the steps how you created the agent by using the
> scdsbuilder, and which parts you added to the script(s) afterwards.
>
> - The key implementation details seem to be
>
> START_CMD="${JBOSS_HOME}/bin/run.sh \
> -b ${HOSTNAME} \
> -Djboss.server.base.dir=${JBOSS_SERVER_BASEDIR} \
> -Djboss.server.base.url=file://${JBOSS_SERVER_BASEDIR} \
> -c ${JBOSS_SERVER_NAME}"
>
> STOP_CMD="${JBOSS_HOME}/bin/shutdown.sh -s ${HOSTNAME} -S"
>
> PROBE_CMD="/usr/sfw/bin/wget -nc -q -O /dev/null
> http://${HOSTNAME}:${JBOSS_SERVER_PORT}
> ${PROBE_CMD_OPT} -t 3"
>
>
> It would be nice if you could describe the JBOSS application behavior a
> bit more in detail in the document:
>
> a) What are the processes and components started by "run.sh".
>
> b) What is the behavior of those components upon application crash
> (be it through node panic or unexpected termination of part or
> all of the JBOSS processes/components)?
>
> c) Will run.sh take care of any cleanup and/or crash recovery after
> a scenario of b)?
>
> d) The probe as implemented has two aspects
> 1) it inherits the process monitoring through PMF,
> which means JBOSS processes are tracked within a PMF tag
> 2) it checks if something is listening on the configured
> JBOSS_SERVER_PORT
>
> Within the design document you mention JBOSS clustering support,
> being designed for high availability.
> Could you describe which mechanism JBOSS uses in order to achieve
> this? I guess this is additional functionality on top of what the
> agent provides, and it would be good to understand how those
> mechanisms work together.
>
> Greets
> Thorsten
>
>
> Kumar Abhishek wrote:
>
>> Hi,
>>
>> I have done some coding on HA-JBoss and have done some initial testing. I
>> would request you to kindly review the code which you can find at
>> http://cr.opensolaris.org/~krabhi/ha-jboss/
>>
>> You can find the design document for this project at
>> http://opensolaris.org/os/project/ha-jboss/files/HA-JBoss_Design_Doc.pdf
>>
>> Summary
>> =========
>>
>> The script startjboss in /util folder attempts to register a resource
>> group for ha-jboss by executing the run.sh file in JBOSS_HOME/bin directory.
>> It passes a custom configuration directory path and custom configuration
>> name as a parameter to the start script. The values of these variables are
>> provided in the jboss_config file inside the same directory.
>>
>> Before registering the resource group, the script tries to validate the
>> parameters provided by checking is the path provided in the jboss_config
>> file are valid and have appropriate permissions.
>>
>> The probe command probes the JBoss server by using wget and it also probes
>> all the custom URLs which are included in a text file, path of which is set
>> in PROBE_URL_LIST variable in jboss_config file.
>> =========
>>
>>
>> Please suggest me the changes I should incorporate in what I have done so
>> far.
>>
>> Thank you for your time.
>>
>> Regards,
>> Abhishek
>>
>
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Sitz der Gesellschaft:
> Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
> Amtsgericht Muenchen: HRB 161028
> Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Dr. Roland Boemer
> Vorsitzender des Aufsichtsrates: Martin Haering
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/ha-clusters-discuss/attachments/20090211/5b02e500/attachment.html>
