IBM Integration Community Come for answers. Stay for best practices. All we’re missing is you. Join / Log in Ask a question
mqtrcfrmt.jar file with debugging option to aid a user in looking into an issue
mqtrcfrmt.jar
Java JSSE Debug Trace This blog post will look at how the Java JSSE (Java Secure Socket Extension) trace can be used to help with debugging TLS issues that involve IBM MQ Java (which would include JMS) client applications
3 Comments - However, and I would give this nearly equal importance, in the very start up of the debug trace you can see which keystore and truststore are being loaded
See matching posts in thread - How debug Java Compute node?...Hel...
DeepDive-Debug&Test-520.mp4
The mustgather details from IBM support may encapsulate all the data needed for debugging issues. kubectl logs -f (apiconnect pod e.g. apiconnect-apim-v2-86b464c4f5-4cx6r) Tail the APIM pod
The communication between the debugger and the runtime is not secured. Care must therefore be taken when debugging a remote runtime
App Connect Enterprise’s flow debugger is widely used in flow development as it enables rapid problem resolution using local servers: the solution can be deployed, tested, and debugged from the toolkit. Moving flows to ACE-as-a-Service (ACEaaS) in AWS appears to break this approach, in that the servers are not visible on the same network as the toolkit and so the debugger will not be able to connect directly, but debugging is still possible using the “private network connection” capability of the ACE service