Detector Utility
The detector utility is an application to monitor detections on a network. It will print to the console the identity and locators of the servers associated with detection messages as they occur (in the case of a new server being discovered or a server going down). The list of servers that the detector knows about will also be printed upon detection events. An example of the output that might be given:
New server detected:
Identity: JBOSS Identity [address:roxanne/192.168.1.2,instanceid:1073635896461,JMX id:192.168.1.2/1073635896602/f0ed2a6d7fb07688x87816dxf9f9afad1axX800023/1,domain:FOO]
InvokerLocator [socket://192.168.1.2:5000/]
Current list of known servers:
Identity: JBOSS Identity [address:GINGER/192.168.1.104,instanceid:1073634265724,JMX id:192.168.1.104/1073634265774/56d35d2f221c8d0ex15b7986xf9f996caaexX800062/1,domain:JBOSS]
InvokerLocator [socket://192.168.1.104:5001/]
Identity: JBOSS Identity [address:roxanne/192.168.1.2,instanceid:1073635896461,JMX id:192.168.1.2/1073635896602/f0ed2a6d7fb07688x87816dxf9f9afad1axX800023/1,domain:FOO]
InvokerLocator [socket://192.168.1.2:5000/]
- Added 1073635907928 to registry.
Server lost:
Identity: JBOSS Identity [address:roxanne/192.168.1.2,instanceid:1073635896461,JMX id:192.168.1.2/1073635896602/f0ed2a6d7fb07688x87816dxf9f9afad1axX800023/1,domain:FOO]
InvokerLocator [socket://192.168.1.2:5000/]
Current list of known servers:
Identity: JBOSS Identity [address:GINGER/192.168.1.104,instanceid:1073634265724,JMX id:192.168.1.104/1073634265774/56d35d2f221c8d0ex15b7986xf9f996caaexX800062/1,domain:JBOSS]
InvokerLocator [socket://192.168.1.104:5001/]
To build the detector utility, run the ant task ‘util’ within the ‘remoting’ directory. This will produce a all the jar files needed to run the application, a script file to run the application (only a Windows bat file now, called ‘runDetectorUtil.bat’), and a zip file (called detectorUtil.zip) which contains all the jars and the script file, within the output/util/ directory of the remoting directory.
To run the detector utility, you can either run the runDetectorUtil.bat file from the build output directory or unzip the detectorUtil.zip into a new directory and run it from there (everything that is needed is in the zip file).
The detector utility can accept the following arguments (in this order):
domain – the domain(s) the detector should accept. If this parameter is not provided, the default will be ‘JBOSS’. If passing multiple domains as a parameter use a comma as a separator and put the entire string of domains within quotes. For example, if want to use domains JBOSS, PROD, and QA would use the following command:
runDetectorUtil “JBOSS,PROD,QA”
type – the type of detection service to use. Valid values are ‘multicast’ or ‘jndi’. The default is multicast. If use jndi, will need to also include port and host.
port – port to use for the detection service. The default is 2410.
host – host name (or ip) to use for the detection service. The default is localhost.
The parameters are sequential, so for each parameter, the one before is required. Some examples are:
runDetectorUtil QA jndi 4910 qa.jboss.org - only detects QA domain using jndi server located at qa.jboss.org, port 4910.
runDetectorUtil “QA,PROD”- detects the QA and PROD domain using multicast on port 2410 (defaults)
Note: The detector utility’s local domain will default to ‘JBOSS’.
------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
