Hello Stefan.
I think your jboss RA should have an OCF parameter to configure options
for the shutdown.sh of JBoss. Otherwise, the RA will be caught in a trouble
when multiple jboss instances run in a same node.
In this case, each java process of JBoss must use different ports,
so the shutdown.sh script of JBoss requires additional options to
identify its target process.
For instance, if the target process uses 1101(default is 1099),
shutdown.sh must be executed like this:
# /path_to_jboss_home_dir/bin/shutdown.sh -s 127.0.0.1:1101
The reason I suggest a new OCF parameter is to take care of this case.
Without this parameter, a stop action for a jboss process whose port
isn't the default causes an unintended stop of the process whose port
is the default.
My suggestions are:
* Rename OCF_RESKEY_jboss_sh into OCF_RESKEY_jboss_run_opts
* Create OCF_RESKEY_jboss_shutdown_opts and pass its value to shutdown.sh
How do you think about this problem?
Takenaka Kazuhiro wrote:
Hello Stefan.
I am planning to test your jboss RA on the following enviroment.
Redhat 5.2(i386)
heartbeat 2.1.4
jdk-1_5_0_17
jboss-eap-4.3.0.GA_CP03
If anything turns out, I will post it.
Wait my report without haste.
Stefan Schluppeck:
Hi,
I have written a jboss ocf script, to run jboss as active/passive
resource.
It is based on the tomcat script. It is tested well under Novell
SLES10 SP2
64bit with jboss-4.2.3.GA, and jdk1.6.0_11
Please take a look.
------------------------------------------------------------------------
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
--
Takenaka Kazuhiro <[email protected]>
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
