Collecting data for problems when using JViews products.

Article ID: 2462
Last updated: 09 Dec, 2014
Article ID: 2462
Last updated: 09 Dec, 2014
Revision: 1
Views: 972
Posted: 18 Oct, 2010
by Dean J.
Updated: 09 Dec, 2014
by Lefévère-Laoide F.

Problem(Abstract)

MustGather documents will aid in problem determination and save time resolving Problem Management Records (PMRs). These documents contain a list of documents you should gather so ILOG Visualization Support can diagnose your specific problem.

Resolving the problem

Collecting general information :

For all Rogue Wave Visualization products:

  • Product used
  • The context (development, production, migration) information with the business impact (precise your project deadline if any)
  • A detail problem description
  • Step by step reproduction sequence
  • Screen shots if relevant
  • Sample code, code fragment or sample from the distribution that reproduces the reported behavior
  • Exceptions, full stack traces in text format
  • Server logs if relevant
  • Name of the Rogue Wave API classes involved (starting with Ilv...)
  • If this is a heavy or a thin client related problem (JSF, ICEfaces, applet, Swing...)

Collecting JViews specific information:

  • Java Development Kit (JDK) version being used (either Sun or IBM JDK) : output of the 'java -version' command
  • Which product (either JViews Gantt, Chart, Diagrammer, Maps, JTGO, GL for Eclipse) including its version and patch level (double-click on the jviews-framework-all.jar file)
  • OS and its version
  • Browser and its version (for JSF/thin client related issues)
  • Application server (for JSF/thin client related issues)

What to do next

This article was:   Helpful | Not helpful
Report an issue
Article ID: 2462
Last updated: 09 Dec, 2014
Revision: 1
Views: 972
Posted: 18 Oct, 2010 by Dean J.
Updated: 09 Dec, 2014 by Lefévère-Laoide F.
Also listed in


Others in this category