Sponsored Content
Special Forums UNIX and Linux Applications JBoss: Difference Standard / proprietary deployment discriptor Post 302632443 by htshshrm2 on Monday 30th of April 2012 06:52:01 AM
Old 04-30-2012
thanks for replying on this...yes, this is with regards to jboss,actually i am kind of new to jboss...just wondering if you can tell me something in detail about it...
 

4 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Proprietary vs. open Unix

Howdy all, I've used various applications in the past that ran in unix and windoze and unfortunately several of those programs are migrating to a windoze only environment so management is bagging the proprietary unix boxes in the process. AArrgggghh So here's my question for all you serious... (3 Replies)
Discussion started by: bulletbob
3 Replies

2. Shell Programming and Scripting

standard error to standard out question

Hi there how can i get the result of a command to not give me its error. For example, on certain systems the 'zfs' command below is not available, but this is fine becaues I am testing against $? so i dont want to see the message " command not found" Ive tried outputting to /dev/null 2>&1 to no... (5 Replies)
Discussion started by: hcclnoodles
5 Replies

3. UNIX for Dummies Questions & Answers

Redirect Standard output and standard error into spreadsheet

Hey, I'm completely new at this and I was wondering if there is a way that I would be able to redirect the log files in a directories standard output and standard error into and excel spreadsheet in anyway? Please remember don't use too advanced of terminology as I just started using shell... (6 Replies)
Discussion started by: killaram
6 Replies

4. Shell Programming and Scripting

Transfer output of a proprietary command to a file

Hi Guys, My problem looks simple. I have a software-proprietary command (not linux) that provides an output, let's say 200 lines. Unfortunately the dumb coders of the software did not include the option ">" or ">>" which allows to transfer output to a file, so I need a way to do that using some... (5 Replies)
Discussion started by: liviusbr
5 Replies
OCF_HEARTBEAT_JBOSS(7)						OCF resource agents					    OCF_HEARTBEAT_JBOSS(7)

NAME
ocf_heartbeat_jboss - Manages a JBoss application server instance SYNOPSIS
jboss [start | stop | status | monitor | meta-data | validate-all] DESCRIPTION
Resource script for Jboss. It manages a Jboss instance as an HA resource. SUPPORTED PARAMETERS
resource_name The name of the resource. Defaults to the name of the resource instance. (unique, optional, string, default default) console A destination of the log of jboss run and shutdown script. (unique, optional, string, no default) shutdown_timeout Timeout for jboss bin/shutdown.sh. We wait for this timeout to expire, then send the TERM and QUIT signals. Finally, the KILL signal is used to terminate the jboss process. You should set the timeout for the stop operation to a value bigger than the sum of the timeout parameters. See also kill_timeout. (optional, integer, default 5) kill_timeout If bin/shutdown.sh doesn't stop the jboss process, then we send it TERM and QUIT signals, intermittently and once a second. After this timeout expires, if the process is still live, we use the KILL signal. See also shutdown_timeout. (optional, integer, default 10) user A user name to start a JBoss. (optional, string, default root) statusurl URL to test in the monitor operation. (optional, string, default http://127.0.0.1:8080) java_home Home directory of Java. Defaults to the environment variable JAVA_HOME. If it is not set, then define this parameter. (optional, string, no default) jboss_home Home directory of Jboss. (unique, required, string, no default) pstring With this string heartbeat matches for the right process to kill. (optional, string, default java -Dprogram.name=run.sh) run_opts Start options to start Jboss with, defaults are from the Jboss-Doku. (optional, string, default -c default -l lpg4j) shutdown_opts Stop options to stop Jboss with. (optional, string, default -s 127.0.0.1:1099) SUPPORTED ACTIONS
This resource agent supports the following actions (operations): start Starts the resource. Suggested minimum timeout: 60s. stop Stops the resource. Suggested minimum timeout: 120s. status Performs a status check. Suggested minimum timeout: 30s. monitor Performs a detailed status check. Suggested minimum timeout: 30s. Suggested interval: 10s. meta-data Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5s. validate-all Performs a validation of the resource configuration. Suggested minimum timeout: 5. EXAMPLE
The following is an example configuration for a jboss resource using the crm(8) shell: primitive p_jboss ocf:heartbeat:jboss params jboss_home=string op monitor depth="0" timeout="30s" interval="10s" SEE ALSO
http://www.linux-ha.org/wiki/jboss_(resource_agent) AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors) resource-agents UNKNOWN 03/09/2014 OCF_HEARTBEAT_JBOSS(7)
All times are GMT -4. The time now is 06:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy