JMS MDB Listener getting paused and Messages are not being removed from the queue
We have set up a point to point, JMS MDB listener and we are able to read the messages. However, the listener read few messages and then gets paused. When we resume it, it reads the same message and gets paused. We do not see any error in the logs. The processing activity only contains a log message which we are able to see for the message being read. We see same message in the queue as it is not being removed after processing. We do not have to send any response back to the provider.
Kindly suggest
***Edited by Moderator Marissa to change General to Product; update Platform Capability tags****
Accepted Solution
Updated: 6 Jun 2022 16:23 EDT
Hitachi Digital Services
US
We found the below errors in the log:
“[5/13/20 18:54:51:180 EDT] 0000009d RegisteredRes E WTRN0063E: An illegal attempt to commit a one phase capable resource with existing two phase capable resources has occurred.” in the error log (sysout.log).
As per the articles in https://community.pega.com/support/support-articles/xaexception-encountered-during-prepare-phase-transaction and https://www.ibm.com/support/pages/trace-analysis-wtrn0063e-illegal-attempt-commit-one-phase-capable-resource-existing-two-phase-capable-resources-has-occurred below change is suggested to resolve the issue.
Please use the following steps to enable the property via the administrative console for WebSphere Application Server version 8.0 or higher:
We found the below errors in the log:
“[5/13/20 18:54:51:180 EDT] 0000009d RegisteredRes E WTRN0063E: An illegal attempt to commit a one phase capable resource with existing two phase capable resources has occurred.” in the error log (sysout.log).
As per the articles in https://community.pega.com/support/support-articles/xaexception-encountered-during-prepare-phase-transaction and https://www.ibm.com/support/pages/trace-analysis-wtrn0063e-illegal-attempt-commit-one-phase-capable-resource-existing-two-phase-capable-resources-has-occurred below change is suggested to resolve the issue.
Please use the following steps to enable the property via the administrative console for WebSphere Application Server version 8.0 or higher:
- In the administrative console, click Servers > Server Types > WebSphere application servers > server_name. The properties of the application server, server_name, are displayed in the content pane.
- Click [Container Settings] Container Services > Transaction Service. The Transaction Service settings page is displayed.
- Ensure that the Configuration tab is displayed.
- Check the box next to "Accept heuristic hazard"
- Restart the application server.
This seemed to have resolved the issue.
Pegasystems Inc.
US
The triggering of the messages is controlled by container. What is your app server? Use the debugging tool there would be the first course of action. From Pega side, the entry point is in class:
com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRJMSListener
You can turn on the logging level to INFO, look for onMessage. If you are not seeing this, focus on the container level debugging (which is outside pega side). Otherwise, provide more details from the Pega side.
Labb Ltd
GB
The messages should be removed automatically once it's received by the container. If it's not happening, please check the queue configurations,
Is it configured to not remove messages unless it receives acknowledgement?
In that case check if listener is configured to send acknowledgement?
Regards,
Murali
Accepted Solution
Updated: 6 Jun 2022 16:23 EDT
Hitachi Digital Services
US
We found the below errors in the log:
“[5/13/20 18:54:51:180 EDT] 0000009d RegisteredRes E WTRN0063E: An illegal attempt to commit a one phase capable resource with existing two phase capable resources has occurred.” in the error log (sysout.log).
As per the articles in https://community.pega.com/support/support-articles/xaexception-encountered-during-prepare-phase-transaction and https://www.ibm.com/support/pages/trace-analysis-wtrn0063e-illegal-attempt-commit-one-phase-capable-resource-existing-two-phase-capable-resources-has-occurred below change is suggested to resolve the issue.
Please use the following steps to enable the property via the administrative console for WebSphere Application Server version 8.0 or higher:
We found the below errors in the log:
“[5/13/20 18:54:51:180 EDT] 0000009d RegisteredRes E WTRN0063E: An illegal attempt to commit a one phase capable resource with existing two phase capable resources has occurred.” in the error log (sysout.log).
As per the articles in https://community.pega.com/support/support-articles/xaexception-encountered-during-prepare-phase-transaction and https://www.ibm.com/support/pages/trace-analysis-wtrn0063e-illegal-attempt-commit-one-phase-capable-resource-existing-two-phase-capable-resources-has-occurred below change is suggested to resolve the issue.
Please use the following steps to enable the property via the administrative console for WebSphere Application Server version 8.0 or higher:
- In the administrative console, click Servers > Server Types > WebSphere application servers > server_name. The properties of the application server, server_name, are displayed in the content pane.
- Click [Container Settings] Container Services > Transaction Service. The Transaction Service settings page is displayed.
- Ensure that the Configuration tab is displayed.
- Check the box next to "Accept heuristic hazard"
- Restart the application server.
This seemed to have resolved the issue.