getMemoryUsage in Tibco Hawk rulebase

Tags

business works, ems, hawk, monitor memory, solaris, tibco, unresolved, unresolved for weeks

Operating Systems Solaris getMemoryUsage in Tibco Hawk rulebase

02-18-2009

Registered User

8, 0

Join Date: Feb 2008

Last Activity: 15 May 2009, 5:55 AM EDT

Posts: 8

Thanks Given: 0

Thanked 0 Times in 0 Posts

getMemoryUsage in Tibco Hawk rulebase

We have a Hawk rulebase monitoring memory usage on a Tibco BW process. We have it set to alert if memory usage goes above 96%.

It is now telling us that usage has reached 96% but we don't know why this is as there is no discernible increase in the number of ems messages that the process is dealing with.

Any ideas about why this would happen or how we can control it. Do we need to take some remedial action with this process to reduce this usage from 96%??

Any help appreciated...

billy_mega

View Public Profile for billy_mega

Find all posts by billy_mega

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. Red Hat

Rsyslog implementation using rulebase

Hi All, Can anyone guide me how to setup rsyslog using rule base, Templates , Modules and mmnormalize.. I have gone through rsyslog site ..But not able to get idea how to set the rsyslog.conf using rulebase particularly.. Thanks in advance ..

2. HP-UX

how to log into a tibco server?

how to log into a tibco server from unix ?

LEARN ABOUT OSX

ucblinks

ucblinks(1B)					     SunOS/BSD Compatibility Package Commands					      ucblinks(1B)

NAME

       ucblinks - adds /dev entries to give SunOS 4.x compatible names to SunOS 5.x devices

SYNOPSIS

       /usr/ucb/ucblinks [-e rulebase] [-r rootdir]

DESCRIPTION

       ucblinks  creates symbolic links under the /dev directory for devices whose SunOS 5.x names differ from their SunOS 4.x names. Where possi-
       ble, these symbolic links point to the device's SunOS 5.x name rather than to the actual /devices entry.

       ucblinks does not remove unneeded compatibility links; these must be removed by hand.

       ucblinks should be called each time the system is reconfiguration-booted, after any new SunOS 5.x links that are needed have been  created,
       since the reconfiguration may have resulted in more compatibility names being needed.

       In  releases prior to SunOS 5.4, ucblinks used a  nawk rule-base to construct the SunOS 4.x compatible names. ucblinks no longer uses  nawk
       for the default operation, although  nawk rule-bases can still be specifed with the -e option.  The  nawk rule-base equivalent to the SunOS
       5.4 default operation can be found in /usr/ucblib/ucblinks.awk.

OPTIONS

       -e rulebase     Specify rulebase as the file containing nawk(1) pattern-action statements.

       -r rootdir      Specify rootdir as the directory under which dev and devices will be found, rather than the standard root directory /.

FILES

       /usr/ucblib/ucblinks.awk        sample rule-base for compatibility links

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWscpu			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       devlinks(1M), disks(1M), ports(1M), tapes(1M), attributes(5)

SunOS 5.10							    13 Apr 1994 						      ucblinks(1B)

Solaris