tibco based application slowness report

Application slowness report #001

User Report/Research and Analysis:

Slowness across the board on a Citrix XenApp hosted application
Application: commodities trading
Category: trading
Server: name removed
(analysis #1) After thorough research from an application perspective on the XenApp server side, we search through our perform and predict application website to see if we could find any anomalies. So as it stands, any of the reliant Tibco, and oracle servers are not available. I've requested to add them so we can investigate the application footprint further. More hopefully to come.
(analysis #2) After further research, our oracle database server is actually part of a cluster and we are getting server metrics. Still no reference to tibco or messaging servers. From a Citrix perspective, we can only see the TCP and UDP endpoints rather than application calls to a "clustered name" which can be annoying when you are apptempting to troubleshoot an application performance issue.

Issues Concerns:

As a citrix administrator researching application performance issues, how do you troubleshoot TIBCO messaging based applications? Are there any command line applications availible to help in the process or is there a 100% reliancy on your Linux/Solaris administrators.
How well does your market data group work? In many cases, I have experienced market data groups are very reluctant to add additional monitorong to their processes and servers where others will have the ability to further drive analysis and troubleshooting. Also, like Canadians are scared of the dark - market data admins are scared of citrix.
Citrix, in general always takes the first hit when applications are not performing as expected. This is of couse without even looking at anything else (network/endpoints/etc...)

Application Dependencies:

Network Statistics:

@ first glance look good, or shall we say... Nominal. A bytes total spike of roughly 2.5% for under 3 seconds is generally nothing to worry about, as there is plenty of network left on a 100Mbps Interface card.
(red) = bytes sent, network adapter history
(yellow) bytes received, network adapter history
(green) bytes total, network adapter history

Performance:

CPU Usage and PF Usage look nominal as well on the server and appear to yield no noticeable spikes or concerns at fist glance.
Running Processes: 126, CPU Usage <1%
Resource manager has status codes of OK for ever monitored Object.

Event Log (24 hr check):

Application Log results
1. (error) The agent was unable to send data to the MOM Server at *****. The error code is 10054, An existing connection was forcibly closed by the remote host. (every 10 seconds) followed by
2. The agent has restored communication to *****.
3. (warning) The agent was unable to read data from the MOM Server at *****. The error code is 10054, An existing connection was forcibly closed by the remote host..
4. (error) Windows cannot obtain the domain controller name for your computer network. (An unexpected network error occurred. ). Group Policy processing aborted.
5. (warning | no concern) An error occurred while retrieving client printer properties. Default printer properties will be used instead. Client name:
System Log results (no serious concerns here or obvious errors/warnings)
1. The Security System has received an authentication request that could not be decoded. The request has failed.

Server Stats:

code examples | documentation