You may encounter these problems when using TeamForge EventQ.

Certain activities appear grayed-out and I cannot get an activity’s detail information

TeamForge EventQ sometimes learns about certain activities through an association reference before the details of the activity are officially reported by the source. Such activities are termed Phantom Activities and appear grayed-out temporarily. Once TeamForge EventQ receives information on this activity it creates a regular Details page and everything goes back to normal. Traceability graphs include these activities, but you cannot click on the commit nodes to get commit details.

Activities may be perpetually grayed-out when TeamForge EventQ is unable to retrieve activity information such as:

  • Activity details of events that occurred before TeamForge EventQ was started — TeamForge EventQ begins to gather data from configured sources as soon as those connections are established, but cannot retrieve historical activity data.
  • Activities that occurred during system down-time — In unusual circumstances such as power outage or network failure, TeamForge EventQ may never receive information about activities that occurred during such events.

Activities in the Activity stream appear out of chronological sequence

Solve this problem by synchronizing the clocks on servers that report data to TeamForge EventQ. The Activity stream shows activities in reverse chronological sequence. EventQ obtains the time stamp for activities from the originating server. Failure to synchronize the clocks of the various servers reporting data to TeamForge EventQ may result in activities that appear out of sequence. On Unix systems, use NTP or similar services to synchronize server clocks.

My custom event handler is not working! What is wrong?

If you get a message in server.log (or events.log) that your event handler could not be parsed, these are some points you might check.

  • Did you change the package of your class containing handler code? - This is not supported.

  • Did you move event.xml to another directory? - This is not supported.

  • Did you compile your java code with a Java version that is not supported by the JVM running on the TeamForge server? Did you use a very long file name for your JAR file? - Only 31 characters are supported.

  • Did you include libraries in your JAR file that have already been part of the default TeamForge class path? - In this case, your libraries will not be picked up.

  • Did you try to reference internal TF classes from packages other than the SOAP namespace? - In this case, the TeamForge security classloader will reject your JAR file.

  • Did you change the DTD location referenced in events.xml? - This will not work.

  • Did you try to trigger a follow up action in a synchronous event handler? - This will most likely result in a time out exception, since your code is already running in a transaction that locks the resources you are trying to obtain a lock for.

  • Did you trigger a TeamForge SOAP call with the session ID passed to your handler which threw an exception? - **See [Using an Asynchronous Event Handler: Trigger Follow-up Events][extend_teamforge.html#asynceventhandler] for an explanation why this does not work.

Tags for this page: faq eventq