Problem reporting is critical to allow TIBCO to continue to improve the TIBCO StreamBase® Runtime product.
Providing the following information in all issues reported to TIBCO will help us resolve problems in a timely fashion.
a concise description of what caused the problem, including these details:
Production or development environment.
Is the problem reproducible? If not how often does it occur?
Deployment tool crash or hang?
Node crash or hang?
Is the node running on a virtual machine?
a simple program, or administrative commands, that recreates the problem.
any screen shots that contain error information.
a snapshot of the node.
If the application is being deployed from a client machine that is different than the server machine please include:
Client operating system and version.
Java version.
Snapshots of node log, configuration, and other information,
are taken using the create snapshot command. A snapshot
of a node can be taken whether a node is running or not. There are also
cases where a node automatically creates a snapshot if an internal error
is detected. These snapshot files should be provided when reporting the
failure.
To take a snapshot of a running node the
servicename or hostname/adminport
parameters are used. If a node is not running, the
installpath
Example 1.1. Node snapshot command
#
# Snapshot of a running node with a service name of A
#
epadmin --servicename=A create snapshot
Created snapshot archive '/opt/RUN/./A/../snapshots/A/A.2015-04-10-09-42-33.zip'
#
# Snapshot of a down node installed into a directory named A
#
epadmin create snapshot --installpath=A
Created snapshot archive '/opt/RUN/A/../snapshots/A/A.2015-04-10-09-43-26.zip'The created snapshot archive should be attached to the support issue.