JWP triggers tracing without reason on AIX

Document ID : KB000117189
Last Modified Date : 14/10/2018
Show Technical Document Details
Issue:
The JWP produce traces  environment.
In WP logs, the following logs matching with trace time creation can be found:
20180410/111636.405 - U00045020 Got feedback for the runtime estimation of RunID '15330390': estimated '44' seconds, actual runtime was '297' seconds.
20180410/111636.431 - U00009907 Memory dump 'Failed to handle message' (Address='n/a', Length='000032')
00000000 46454544 4241434B 30310018 001A4B81 >FEEDBACK01....K.<
00000010 00E9EC56 001CDF2A 0000002C 00000129 >.éìV..ß*...,...)<
20180410/111636.432 - U00045014 Exception 'java.lang.IllegalAccessError: "invokeinterface of non-public method 'iterator ' in java/u "' at 'com.google.common.collect.Sets$SetFromMap.iterator():527'.
20180410/111636.432 - U00003620 Routine 'com.automic.kernel.impl.MQRecordReader' forces trace because of error.
20180410/111636.440 - U00003450 The TRACE file was opened with the switches '0000000000000000'.
20180410/111636.676 - U00003449 Output to the TRACE file is finished.
Environment:
AIX Agent with IBM Java
Resolution:

Solution:

Update to a fix version listed below or a newer version if available.

 

Fix version:

Component(s): Automation Engine 

 

  • Automation.Engine 12.1.3 - Available
  • Automation.Engine 12.0.6 - Available
  • Automation.Engine 11.2.9 - Available