Change 1
[2/20/17 7:53:19:800 CST] 00000262 PartnerLogDat E WTRN0000E: An internal error occurred in method logData in class com.ibm.ws.Transaction.JTA.PartnerLogData; the exception stack trace follows: com.ibm.ws.recoverylog.spi.InternalLogException
Line 114616: [2/20/17 7:53:19:803 CST] 000002e0 PartnerLogDat E WTRN0000E: An internal error occurred in method logData in class com.ibm.ws.Transaction.JTA.PartnerLogData; the exception stack trace follows: com.ibm.ws.recoverylog.spi.InternalLogException
Line 114641: [2/20/17 7:53:19:807 CST] 000002e8 PartnerLogDat E WTRN0000E: An internal error occurred in method logData in class com.ibm.ws.Transaction.JTA.PartnerLogData; the exception stack trace follows: com.ibm.ws.recoverylog.spi.InternalLogException
This may cause because our transaction/partner log is getting full. For temporary fix we can increase the size of partner log size. Please find below link for reference.
http://www-01.ibm.com/support/docview.wss?uid=swg1PM11632
https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014787263
Change 2
We have around 40 ActivationSpec and each ActivationSpec has maximum server session 2. So ideally WMQJCAResourceAdapter thread pool max size should be 80(40*2).But in our case it is 75.
We should do this change when we migrated few new modules.
We have to do change adaptor thread pool settings to 90 .Lets do this change next time before doing JVM restart.
http://www-01.ibm.com/support/docview.wss?uid=swg21383363
https://www.ibm.com/developerworks/community/blogs/aimsupport/entry/why_are_messages_piling_up_in_process_server_queues_and_not_getting_processed?lang=en
http://www-01.ibm.com/support/docview.wss?uid=swg21115785
