• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Jeanne Boyarsky
  • Ron McLeod
Sheriffs:
  • Paul Clapham
  • Liutauras Vilda
  • Devaka Cooray
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
Bartenders:

Dealing with MQ WF

 
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have part of my application using MQ Workflow to call Java components; several activities executing one after the other based on the "ResultCode".
I feel this acts like a "Black box" and i am not familiar with the WF call / working mechanism ( i am not working on WF) the only way the application is debugged is from the log files (log4j used in java code).
this is the only way i can get to know any problem in the application.
even if there is really problem in the WF model or FDL definition its only the logs we need to analyze to find the problem is really with java code or WF definition.

is there any way to log "calls" within the WF and log it separately so it will be helpful to navigate the WF logs to find the problem ?
is there any way to do this ?
please help, since this becomes a huge problem when debugging with a larger application.
 
roses are red, violets are blue. Some poems rhyme and some are a tiny ad:
New web page for Paul's Rocket Mass Heaters movies
https://coderanch.com/t/785239/web-page-Paul-Rocket-Mass
reply
    Bookmark Topic Watch Topic
  • New Topic