Administer > System configuration parameters > Servlet parameters > Parameter: reportgroup

Parameter: reportgroup

Parameter

reportgroup

Description

This parameter displays the status of ports, processes, and threads in horizontal and vertical scaling servlet implementations.

Important: The reportgroup process requires every other process to send it a report. This means that every process must consume some amount of system memory to generate its report, which decreases the amount of memory available to run the system. While the reporting information may be valuable, you need to balance your data tracking requirements with the amount of memory being used. To reduce the performance impact of running this process, you may want to run it on a development or testing system, or choose a longer interval between running reports.

Note If you have opted to run this process continuously (for example, every minute non-stop), you have the option to shut down the process. To shut down a specific Service Manager process, specify the hostname of the Service Manager server and system process (PID) you want to shut down. On a command line, enter sm -shutdown -host:myhost.myserver.com -PID:1234.

Some examples of the information that is reported include:

  • Service Manager locks that are currently being held.
  • Service Manager threads waiting to acquire locks. This is useful for lock analysis.
  • Thread dumps of all Service Manager processes on all hosts. This is useful for detecting deadlocks, if any. Thread dumps repeat for each process and host.

The information is sent to a separate log file.

Settings

Server's operating system command prompt

Requires restart of the Service Manager server?

No

Default values

Run the report every 20 seconds.

Repeat the process 15 times.

Possible values

Number of seconds between reports and the number of times to run a report.

Example usage

Run the report every 20 seconds and repeat the process 15 times.

sm -reportgroup

sm -reportgroup:20,15

Recommended: Run the report every minute and repeat the process 20 times. This provides less load on the cluster.

sm -reportgroup:60,20

Log File Examples

The following sample is an example of the information that is displayed in a log file for a vertical scaling servlet implementation on one host.

Note  

  • This example report has been reformatted for printed display.
  • The output in this example has been truncated (this is not the full output from the command).
Load Balancer Status:Sat Jun 23 09:58:52 PDT 2012
HP Service Manager LoadBalancer Running on Host:myhost.myserver.com Port:34567
List of Hosts:

HostName: myhost.myserver.com
-------------------------------------------------------------------Server Instances
 ProcessID     ClusterAddress     HttpPort  HttpsPort  Sessions  DbgMode  QMode  LB         
    7872     15.178.177.72:33285    34568       0       (3/50)      N       N     N   
    7881     15.178.177.72:33283    34569       0       (1/50)      N       N     N      
    7837     15.178.177.72:33278    34567       0       (0/50)      N       N     Y       

-------------------------------------------------
State        LowMem     JAVA_USED/MAX/PERCENT
WR[6d22h39m] N       (4404408/238616576/1.8458097)
QR[9m]       N       (2983152/238616576/1.2501864)
RUN          N       (2601080/238616576/1.0900668)
----------------------------------------------------------Non Server Instances---
 ProcessID     ClusterAddress         State    LowMem     JAVA_USED/MAX/PERCENT    
    8510     15.178.177.72:33329       RUN        N         (0/89522176/0.0)         
    7931     15.178.177.72:33299       RUN        N   (1502256/59703296/2.5162027)   
    7880     15.178.177.72:33280       RST        N   (1539248/59703296/2.5781624)   
    7930     15.178.177.72:33291       SHT        N   (1514024/59703296/2.5359137)   

--------------------------------------

Command Line parameters
-reportgroup:1,1 
-sync -log:../logs/sm.sync.log 
system.start -log:../logs/sm.start.log 
-que:ir -log:../logs/sm.que.log

Locks from all nodes in the cluster.
Waiting locks
Thread Dumps from all nodes In the cluster
Thread Dump from process: Host: myhost.myserver.com PID: 7872 
ChannelAddress: 15.178.177.72:33285
   SM_LowMemoryHandler
            java.lang.Thread.sleep(Native Method)
            comp.hp.ov.sm.common.oom.LowMemoryHandler.run(LowMemoryHandler.java:181)
            java.lang.Thread.run(Thread.java:619

Related topics

Servlet implementation
System parameters
Startup parameter: shutdown
Connection parameters
Servlet parameters