Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
November 17, 2009, 03:58 PM
Pascal Bellerose
Already read this and it's no use because the configuration tools crashes the http listener. (about to open a case on this)
I need to understand traces components in order to know which traces I can start without to much impact on the system.
For example, If it's possible, I'd like to start a trace that will monitor incoming requests only.
The main reason for this is we have a setup made of Reporting servers connecting to Full Function Servers. We may get an email stating that a Full Function Server's agent crashed. Since edaprint does not show the incoming request, we can't figure out which reporting server sent it.
Sometimes we don't even get an ibisnap. And when we have one, the call stack is useless without the context.
Thanks
WFS/FFS/DM 7.6.4 / WFS/FFS/DM 7.6.8 / WFS/FFS/DM 7.6.9 / AS400 V5R4M0 / HTML / iSM 5.5sp2
November 20, 2009, 10:53 AM
Kerry
Hi Pascal,
For installation and configuration issues, the best channel for assistance would be to open a case with Information Builders' Customer Support Services. The phone number is 1-800-736-6130, or access online at InfoResponse.
Cheers,
Kerry
Kerry Zhan Focal Point Moderator Information Builders, Inc.