Author |
Message
|
shashivarungupta |
Posted: Fri Oct 11, 2013 5:42 am Post subject: SHARECNV to 0 from 10. What's the Impact on MQ and Appl ? |
|
|
 Grand Master
Joined: 24 Feb 2009 Posts: 1343 Location: Floating in space on a round rock.
|
Hi,
As per the InfoCenter... for SHARECNV ...
"The number of shared conversations over a TCP/IP socket.
The filter value is the integer number of shared conversations."
but if that value ( SHARECNV ) is being decreased from 10 to 0, what could be the impact on MQ and Application Transactions ?
Would that cause any delay in messages / transactions ?
Cause at present the channel status has two instances and each has CURSHCNV on it with value 5 and 1, that means, multiple conversations running on that instance of channel.
If I have to change the value of SHARECNV .. do I have to clear the buffer or space occupied ?
MQv7.0.1.6, Linux 64 bit. _________________ *Life will beat you down, you need to decide to fight back or leave it. |
|
Back to top |
|
 |
bruce2359 |
Posted: Fri Oct 11, 2013 5:59 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9470 Location: US: west coast, almost. Otherwise, enroute.
|
Do any of your applications multi-thread? Most user-written apps do not. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
shashivarungupta |
Posted: Fri Oct 11, 2013 9:08 am Post subject: |
|
|
 Grand Master
Joined: 24 Feb 2009 Posts: 1343 Location: Floating in space on a round rock.
|
bruce2359 wrote: |
Do any of your applications multi-thread? Most user-written apps do not. |
Application team shared some of the logs that they've faced... and cause of that they suggested to change its value to 0.
Quote: |
Failed at message handling with error JMSWMQ2002: Failed to get a message from destination '<QUEUETEST>'. errorCode JMSWMQ2002
com.ibm.msg.client.jms.DetailedMessageFormatException: JMSWMQ2002: Failed to get a message from destination '<QUEUE1>'. WebSphere MQ classes for JMS attempted to perform an MQGET; however WebSphere MQ reported an error. Use the linked exception to determine the cause of this error.
at com.ibm.msg.client.wmq.common.internal.Reason.reasonToException(Reason.java:570)
at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:236)
at com.ibm.msg.client.wmq.internal.WMQMessageConsumer.checkJmqiCallSuccess(WMQMessageConsumer.java:128)
at com.ibm.msg.client.wmq.internal.WMQConsumerShadow.getMsg(WMQConsumerShadow.java:1289)
at com.ibm.msg.client.wmq.internal.WMQSyncConsumerShadow.receiveInternal(WMQSyncConsumerShadow.java:233)
at com.ibm.msg.client.wmq.internal.WMQConsumerShadow.receive(WMQConsumerShadow.java:1013)
at com.ibm.msg.client.wmq.internal.WMQMessageConsumer.receive(WMQMessageConsumer.java:459)
at com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl.receiveInboundMessage(JmsMessageConsumerImpl.java:768)
at com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl.receive(JmsMessageConsumerImpl.java:449)
at com.ibm.mq.jms.MQMessageConsumer.receive(MQMessageConsumer.java:258)
at com.domain.application.core.jms.listener.JmsEndpointListener.runBatch(JmsEndpointListener.java:207)
at com.domain.application.core.jms.listener.JmsEndpointListener.run(JmsEndpointListener.java:104)
Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '1' ('MQCC_WARNING') reason '2111' ('MQRC_SOURCE_CCSID_ERROR').
at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:223)
... 10 more
ERROR><DATE TIME STAMP VALUE> *.core.jms.listener.JmsEndpointListener[uatMqTestEndpoint.listener.0]: Linked Exception is
com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '1' ('MQCC_WARNING') reason '2111' ('MQRC_SOURCE_CCSID_ERROR').
at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:223)
at com.ibm.msg.client.wmq.internal.WMQMessageConsumer.checkJmqiCallSuccess(WMQMessageConsumer.java:128)
at com.ibm.msg.client.wmq.internal.WMQConsumerShadow.getMsg(WMQConsumerShadow.java:1289)
at com.ibm.msg.client.wmq.internal.WMQSyncConsumerShadow.receiveInternal(WMQSyncConsumerShadow.java:233)
at com.ibm.msg.client.wmq.internal.WMQConsumerShadow.receive(WMQConsumerShadow.java:1013)
at com.ibm.msg.client.wmq.internal.WMQMessageConsumer.receive(WMQMessageConsumer.java:459)
at com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl.receiveInboundMessage(JmsMessageConsumerImpl.java:768)
at com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl.receive(JmsMessageConsumerImpl.java:449)
at com.ibm.mq.jms.MQMessageConsumer.receive(MQMessageConsumer.java:258)
at com.domain.application.core.jms.listener.JmsEndpointListener.runBatch(JmsEndpointListener.java:207)
at com.domain.application.core.jms.listener.JmsEndpointListener.run(JmsEndpointListener.java:104)
|
I don't know if that's related to it. ANY Suggestions ? _________________ *Life will beat you down, you need to decide to fight back or leave it. |
|
Back to top |
|
 |
mqjeff |
Posted: Fri Oct 11, 2013 9:13 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
It's not related in the slightest.
It means your applications teams are completely unable to read error messages, that they are bothering you with it. |
|
Back to top |
|
 |
Tibor |
Posted: Fri Oct 11, 2013 9:21 am Post subject: |
|
|
 Grand Master
Joined: 20 May 2001 Posts: 1033 Location: Hungary
|
|
Back to top |
|
 |
shashivarungupta |
Posted: Fri Oct 11, 2013 10:50 am Post subject: |
|
|
 Grand Master
Joined: 24 Feb 2009 Posts: 1343 Location: Floating in space on a round rock.
|
There could be couple of scenarios...
1. Application is multi-threaded.
2. Application is not multi-threaded.
If its case 1, what if SHARECNV altered to 0 from 10 ? would that cause impact on connection applications and message throughput ?
If its case 2, what if SHARECNV alerted to 0 from 10 ? would that cause impact on connection applications and message throughput ? [logically not.] _________________ *Life will beat you down, you need to decide to fight back or leave it. |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Oct 11, 2013 1:31 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
There's also an APAR on that. Check it out  _________________ MQ & Broker admin |
|
Back to top |
|
 |
shashivarungupta |
Posted: Fri Oct 11, 2013 7:37 pm Post subject: |
|
|
 Grand Master
Joined: 24 Feb 2009 Posts: 1343 Location: Floating in space on a round rock.
|
bruce2359 wrote: |
Do any of your applications multi-thread? Most user-written apps do not. |
Multi-thread and single-thread consumers are there !! _________________ *Life will beat you down, you need to decide to fight back or leave it. |
|
Back to top |
|
 |
shashivarungupta |
Posted: Sat Oct 12, 2013 9:45 am Post subject: |
|
|
 Grand Master
Joined: 24 Feb 2009 Posts: 1343 Location: Floating in space on a round rock.
|
mqjeff wrote: |
It's not related in the slightest.
It means your applications teams are completely unable to read error messages, that they are bothering you with it. |
I totally agree with you.. cause we have seen cases like when application team comes up with their message lost request.. and by the end of the hot call.. everytime.. they say.. its not logged in their logs .. and receiver gets that but they didn't acknowledge... huh....  _________________ *Life will beat you down, you need to decide to fight back or leave it. |
|
Back to top |
|
 |
|