Ticket #387 (closed defect: fixed)

Opened 5 years ago

Last modified 4 years ago

Flukes does not return manifests properly, when manifest contains Java stack backtrace

Reported by: vjo Owned by: ibaldin
Priority: major Milestone:
Component: External: FLUKES Version: baseline
Keywords: Cc:


When I was diagnosing the issue with the OSF rack (wherein the OSCARS instance servicing OSF had crashed, and was returning a Java stack trace), attempts to query for a manifest via Flukes resulted in an error dialog.

It would appear that, when the manifest that is returned contains the text of an exception, Flukes interprets this as though an Exception had been returned.

This issue needs to be resolved, since Flukes never loads the manifest that contains the Exception text (after displaying the error dialog), and the request that resulted in the manifest containing the Exception can no longer be manipulated by Flukes; it has to be closed via pequod instead.

Change History

Changed 4 years ago by ibaldin

  • status changed from new to closed
  • resolution set to fixed

Fixed in r7071 - not a flukes, but a controller issue.

Note: See TracTickets for help on using tickets.