IBM FHIR Server – Debugging Tips

Checking a Postgres Function Definition

I needed to verify my postgres function.

  1. Shows the contents of the functions in the schema.
SELECT pg_get_functiondef(f.oid)
FROM pg_catalog.pg_proc f
INNER JOIN pg_catalog.pg_namespace n ON (f.pronamespace = n.oid)
WHERE n.nspname = 'fhirdata';
  1. Show all the details of the functions in the schema.
SELECT *
FROM pg_catalog.pg_proc f
INNER JOIN pg_catalog.pg_namespace n ON (f.pronamespace = n.oid)
WHERE n.nspname = 'fhirdata';

Tracing Bulk Data with Cloud Object Storage

I wanted to figure out why my code was failing to connect to the backend S3 bucket.

I used the environment variable in my docker image called TRACE_SPEC. TRACE_SPEC is loaded into the logging as the traceSpecification.

I set this to *=info:com.ibm.cloud.*=FINEST which spits out great detail to S3 using the IBM COS SDK.

The output looks like:

With this level of trace, you can really dive into the connection, and determine what is going on.

Note, if you want the whole picture of what is happening with COS and JavaBatch and BulkData, use the following:

*=info:com.ibm.fhir.*=finer:RRA=all:WAS.j2c=all:com.ibm.ws.jdbc.*=all:Transaction=all:ConnLeakLogic=all:Transaction=all:com.ibm.ws.transaction.services.WebAppTransactionCollaboratorImpl=all:RRA=all:com.ibm.cloud.*=FINEST

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.