Mixing
Handle out of sync point issue via IBM JMS from Mule
I am connecting MQ-8.x from Mule via JMS and recently I had faced an issue that seems like MQ write operation is going out of sync point range and due to this and also the huge inbound load, MQ went in to deadlock state.
<spring:bean id="ConnectionFactory" class="com.ibm.mq.jms.MQConnectionFactory" name="ConnectionFactory">
<spring:property name="hostName" value="xxxx" />
<spring:property name="port" value="xxxx"/>
<spring:property name="queueManager" value="xxxx"/>
<spring:property name="transportType" value="1"/>
<spring:property name="channel" value="xxxx"/>
</spring:bean>
<jms:connector name="JmsConsumer" username="xxxx" password="xxxx" specification="1.1" connectionFactory-ref="ConnectionFactory" numberOfConsumers="1" validateConnections="true" persistentDelivery="true" doc:name="JMS"/>
<jms:outbound-endpoint queue="xxxx" connector-ref="JmsConsumer" doc:name="Audits"/>
My operation volume will be move but its just a PUT operation, so I am really not sure whether XA or other Transaction manager to be needed in this.
jms mule ibm-mq xa mule-esb
asked Aug 28 '18 at 17:16
NGBeginnerNGBeginner
10019
add a comment |
I am connecting MQ-8.x from Mule via JMS and recently I had faced an issue that seems like MQ write operation is going out of sync point range and due to this and also the huge inbound load, MQ went in to deadlock state.
<spring:bean id="ConnectionFactory" class="com.ibm.mq.jms.MQConnectionFactory" name="ConnectionFactory">
<spring:property name="hostName" value="xxxx" />
<spring:property name="port" value="xxxx"/>
<spring:property name="queueManager" value="xxxx"/>
<spring:property name="transportType" value="1"/>
<spring:property name="channel" value="xxxx"/>
</spring:bean>
<jms:connector name="JmsConsumer" username="xxxx" password="xxxx" specification="1.1" connectionFactory-ref="ConnectionFactory" numberOfConsumers="1" validateConnections="true" persistentDelivery="true" doc:name="JMS"/>
<jms:outbound-endpoint queue="xxxx" connector-ref="JmsConsumer" doc:name="Audits"/>
My operation volume will be move but its just a PUT operation, so I am really not sure whether XA or other Transaction manager to be needed in this.
jms mule ibm-mq xa mule-esb
asked Aug 28 '18 at 17:16
NGBeginnerNGBeginner
10019
Sounds like your jms:connector isn't committing the transactions ? Maybe you should try transactionalAction="ALWAYS_JOIN" ?
– Axel Podehl
Sep 6 '18 at 17:00
add a comment |
I am connecting MQ-8.x from Mule via JMS and recently I had faced an issue that seems like MQ write operation is going out of sync point range and due to this and also the huge inbound load, MQ went in to deadlock state.
<spring:bean id="ConnectionFactory" class="com.ibm.mq.jms.MQConnectionFactory" name="ConnectionFactory">
<spring:property name="hostName" value="xxxx" />
<spring:property name="port" value="xxxx"/>
<spring:property name="queueManager" value="xxxx"/>
<spring:property name="transportType" value="1"/>
<spring:property name="channel" value="xxxx"/>
</spring:bean>
<jms:connector name="JmsConsumer" username="xxxx" password="xxxx" specification="1.1" connectionFactory-ref="ConnectionFactory" numberOfConsumers="1" validateConnections="true" persistentDelivery="true" doc:name="JMS"/>
<jms:outbound-endpoint queue="xxxx" connector-ref="JmsConsumer" doc:name="Audits"/>
My operation volume will be move but its just a PUT operation, so I am really not sure whether XA or other Transaction manager to be needed in this.
jms mule ibm-mq xa mule-esb
asked Aug 28 '18 at 17:16
NGBeginnerNGBeginner
10019
I am connecting MQ-8.x from Mule via JMS and recently I had faced an issue that seems like MQ write operation is going out of sync point range and due to this and also the huge inbound load, MQ went in to deadlock state.
<spring:bean id="ConnectionFactory" class="com.ibm.mq.jms.MQConnectionFactory" name="ConnectionFactory">
<spring:property name="hostName" value="xxxx" />
<spring:property name="port" value="xxxx"/>
<spring:property name="queueManager" value="xxxx"/>
<spring:property name="transportType" value="1"/>
<spring:property name="channel" value="xxxx"/>
</spring:bean>
<jms:connector name="JmsConsumer" username="xxxx" password="xxxx" specification="1.1" connectionFactory-ref="ConnectionFactory" numberOfConsumers="1" validateConnections="true" persistentDelivery="true" doc:name="JMS"/>
<jms:outbound-endpoint queue="xxxx" connector-ref="JmsConsumer" doc:name="Audits"/>
My operation volume will be move but its just a PUT operation, so I am really not sure whether XA or other Transaction manager to be needed in this.
jms mule ibm-mq xa mule-esb
jms mule ibm-mq xa mule-esb
asked Aug 28 '18 at 17:16
NGBeginnerNGBeginner
10019
asked Aug 28 '18 at 17:16
NGBeginnerNGBeginner
10019
asked Aug 28 '18 at 17:16
NGBeginnerNGBeginner
10019
asked Aug 28 '18 at 17:16
NGBeginnerNGBeginner
10019
asked Aug 28 '18 at 17:16
NGBeginnerNGBeginner
10019
10019
Sounds like your jms:connector isn't committing the transactions ? Maybe you should try transactionalAction="ALWAYS_JOIN" ?
– Axel Podehl
Sep 6 '18 at 17:00
add a comment |
Sounds like your jms:connector isn't committing the transactions ? Maybe you should try transactionalAction="ALWAYS_JOIN" ?
– Axel Podehl
Sep 6 '18 at 17:00
Sounds like your jms:connector isn't committing the transactions ? Maybe you should try transactionalAction="ALWAYS_JOIN" ?
– Axel Podehl
Sep 6 '18 at 17:00
Sounds like your jms:connector isn't committing the transactions ? Maybe you should try transactionalAction="ALWAYS_JOIN" ?
– Axel Podehl
Sep 6 '18 at 17:00
add a comment |
2 Answers
2
active
oldest
votes
This has been handled in MQ-9.x version that MQ itself will manage the out of sync point implicitly. MQ-9.x upgrade will be the solution for this kind of issue.
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.dev.doc/q026865_.html
answered Nov 20 '18 at 18:00
NGBeginnerNGBeginner
10019
You should accept your own answer, note this change was added in MQ 9.0.5 CDS release and is present in the new MQ v9.1 release.
– JoshMc
Nov 20 '18 at 18:32
add a comment |
This message is produced because persistent messages are being produced out side of a transaction. MQ is highly optimized to process transactional persistent messages and this warning is informing us that the queue isn't being processed as efficiently as possible. The system will receive a significant performance improvement if you make the actions inside a transaction/syncpoint or if non persistent is good enough turn the persistent flag off.
answered Nov 20 '18 at 17:36
newbienewbie
18928
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52063260%2fhandle-out-of-sync-point-issue-via-ibm-jms-from-mule%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
This has been handled in MQ-9.x version that MQ itself will manage the out of sync point implicitly. MQ-9.x upgrade will be the solution for this kind of issue.
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.dev.doc/q026865_.html
answered Nov 20 '18 at 18:00
NGBeginnerNGBeginner
10019
You should accept your own answer, note this change was added in MQ 9.0.5 CDS release and is present in the new MQ v9.1 release.
– JoshMc
Nov 20 '18 at 18:32
add a comment |
This has been handled in MQ-9.x version that MQ itself will manage the out of sync point implicitly. MQ-9.x upgrade will be the solution for this kind of issue.
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.dev.doc/q026865_.html
answered Nov 20 '18 at 18:00
NGBeginnerNGBeginner
10019
You should accept your own answer, note this change was added in MQ 9.0.5 CDS release and is present in the new MQ v9.1 release.
– JoshMc
Nov 20 '18 at 18:32
add a comment |
This has been handled in MQ-9.x version that MQ itself will manage the out of sync point implicitly. MQ-9.x upgrade will be the solution for this kind of issue.
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.dev.doc/q026865_.html
answered Nov 20 '18 at 18:00
NGBeginnerNGBeginner
10019
This has been handled in MQ-9.x version that MQ itself will manage the out of sync point implicitly. MQ-9.x upgrade will be the solution for this kind of issue.
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.dev.doc/q026865_.html
answered Nov 20 '18 at 18:00
NGBeginnerNGBeginner
10019
answered Nov 20 '18 at 18:00
NGBeginnerNGBeginner
10019
answered Nov 20 '18 at 18:00
NGBeginnerNGBeginner
10019
answered Nov 20 '18 at 18:00
NGBeginnerNGBeginner
10019
10019
You should accept your own answer, note this change was added in MQ 9.0.5 CDS release and is present in the new MQ v9.1 release.
– JoshMc
Nov 20 '18 at 18:32
add a comment |
You should accept your own answer, note this change was added in MQ 9.0.5 CDS release and is present in the new MQ v9.1 release.
– JoshMc
Nov 20 '18 at 18:32
You should accept your own answer, note this change was added in MQ 9.0.5 CDS release and is present in the new MQ v9.1 release.
– JoshMc
Nov 20 '18 at 18:32
You should accept your own answer, note this change was added in MQ 9.0.5 CDS release and is present in the new MQ v9.1 release.
– JoshMc
Nov 20 '18 at 18:32
add a comment |
This message is produced because persistent messages are being produced out side of a transaction. MQ is highly optimized to process transactional persistent messages and this warning is informing us that the queue isn't being processed as efficiently as possible. The system will receive a significant performance improvement if you make the actions inside a transaction/syncpoint or if non persistent is good enough turn the persistent flag off.
answered Nov 20 '18 at 17:36
newbienewbie
18928
add a comment |
This message is produced because persistent messages are being produced out side of a transaction. MQ is highly optimized to process transactional persistent messages and this warning is informing us that the queue isn't being processed as efficiently as possible. The system will receive a significant performance improvement if you make the actions inside a transaction/syncpoint or if non persistent is good enough turn the persistent flag off.
answered Nov 20 '18 at 17:36
newbienewbie
18928
add a comment |
This message is produced because persistent messages are being produced out side of a transaction. MQ is highly optimized to process transactional persistent messages and this warning is informing us that the queue isn't being processed as efficiently as possible. The system will receive a significant performance improvement if you make the actions inside a transaction/syncpoint or if non persistent is good enough turn the persistent flag off.
answered Nov 20 '18 at 17:36
newbienewbie
18928
This message is produced because persistent messages are being produced out side of a transaction. MQ is highly optimized to process transactional persistent messages and this warning is informing us that the queue isn't being processed as efficiently as possible. The system will receive a significant performance improvement if you make the actions inside a transaction/syncpoint or if non persistent is good enough turn the persistent flag off.
answered Nov 20 '18 at 17:36
newbienewbie
18928
answered Nov 20 '18 at 17:36
newbienewbie
18928
answered Nov 20 '18 at 17:36
newbienewbie
18928
answered Nov 20 '18 at 17:36
newbienewbie
18928
18928
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52063260%2fhandle-out-of-sync-point-issue-via-ibm-jms-from-mule%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Sounds like your jms:connector isn't committing the transactions ? Maybe you should try transactionalAction="ALWAYS_JOIN" ?
– Axel Podehl
Sep 6 '18 at 17:00