Skip to main content

Diagnostic information for Process flow is missing

Comments

7 comments

  • David Paras

    Could you double check that the process flow was saved after changing the Logging Level to Debug? The details information and diagnostic information are stored in different logging tables, so there maybe a problem with the diagnostic table.

    0
  • Tomasz Gruszewski

    I have checked that the process flow was saved successfully after changing the Logging Level to Debug - no problem here. However I have noticed warning message in Java console during loading of Process Designer for my process. Process designer loads ok, but in Java console window message is:

    "log4j:WARN No appenders could be found for logger (org.apache.commons.jelly.parser.XMLParser).

    log4j:WARN Please initialize the log4j system properly.

    Exception in thread "AWT-EventQueue-0" java.lang.ClassCastException  at javax.swing.LayoutComparator.compare(Unknown Source)

    at java.util.Arrays.mergeSort(Unknown Source)

    ... "

    Is this due to wrong configuration in log4j.properties file ?

    0
  • David Paras

    Is this issue occurring for all process flows or only certain ones? If only certain ones, could you describe the use case of these flows?

    0
  • Tomasz Gruszewski

    The warning message "log4j:WARN No appenders could be found for logger (org.apache.commons.jelly.parser.XMLParser)" shows up in Java console for every Process flow on Dev and UAT.

    The same with Diagnostic information - missing for other Processes on UAT.

    However on Dev environment Diagnostic information is available. Log4j.properties files are the same on DEV and UAT.

    There is one difference between environments in Administer > Setup > Application Settings > Update System Properties  > Systems > Logging > NteventLogging: paramter log4j.appender.ntevent.layout.ConversionPattern

    Value on DEV: %d{ISO8601} %-4r [%t] (%F:%L)%c %x - %m%n

    Value on UAT: %d                  %-4r [%t] (%F:%L)%c %x - %m%n

     

    0
  • David Paras

    When there's an issue that is occurring on one environment and not the other, a good tip is to compare the server-config.properties files from each system and look for possible differences that could cause the issue.

     

    This file can be found in the \AdeptiaSuite\AdeptiaSuite-5.1\AdeptiaServer\ServerKernel\etc directory

    0
  • Tomasz Gruszewski

    I've compared server-config.properties (UAT vs. Dev) line by line, but did not find significat difference, only URL differences and still Diagnostic information is not visible on UAT

    0
  • David Paras

    At this point, we would recommend an upgrade to our latest version or to submit a support request here: http://support.adeptia.com/anonymous_requests/new.

    0

Post is closed for comments.