Author |
Message
|
flsb |
Posted: Wed Oct 30, 2019 5:58 pm Post subject: |
|
|
Apprentice
Joined: 01 Apr 2010 Posts: 43
|
bruce2359 wrote: |
Did you try it? What was the result? |
i have not try yet..
there are 3 options in the thread..
1) need to modify registry
2) MQNOREMPOOL
was wondering if anyone has coem across this MQNOREMPOOL setting before? |
|
Back to top |
|
 |
hughson |
Posted: Wed Oct 30, 2019 7:12 pm Post subject: |
|
|
 Padawan
Joined: 09 May 2013 Posts: 1959 Location: Bay of Plenty, New Zealand
|
flsb wrote: |
Will it help if i set MQNOREMPOOL=1 ? |
Seems unlikely - nothing you have told us suggests a change from threads in a pool process, to threads in the listener process will make any difference. You have told us you have network timeout problems.
Cheers,
Morag _________________ Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
Back to top |
|
 |
flsb |
Posted: Wed Oct 30, 2019 11:38 pm Post subject: |
|
|
Apprentice
Joined: 01 Apr 2010 Posts: 43
|
ok I tried MQNOREMPOOL = 1 in MS env variables and it didn't help..
rebooted server, tried sending data via the channel but still stuck in transmit..
Does this MQNOREMPOOL available in MQv9.1?
Syn Attack is not in registry anymore..
this SynAttack is enabled by default and not able to disable anymore from Vista onwards..
now i'm suspecting TCP stack..
what other param can I set on TCP stack? |
|
Back to top |
|
 |
HubertKleinmanns |
Posted: Thu Oct 31, 2019 1:01 am Post subject: |
|
|
 Shaman
Joined: 24 Feb 2004 Posts: 732 Location: Germany
|
You should also check the network card on the remote side. In the past I had the situation, that a setting on the NIC prevented MQ channels to come up. I don't remember the exact flag, but it was some security setting, to prevent DoS attacks o something like this. _________________ Regards
Hubert |
|
Back to top |
|
 |
flsb |
Posted: Sun Nov 03, 2019 6:54 pm Post subject: |
|
|
Apprentice
Joined: 01 Apr 2010 Posts: 43
|
HubertKleinmanns wrote: |
You should also check the network card on the remote side. In the past I had the situation, that a setting on the NIC prevented MQ channels to come up. I don't remember the exact flag, but it was some security setting, to prevent DoS attacks o something like this. |
it is running on VM Windows
my side is running on VM RHEL
i suspect the VM manager setting in Windows side.. and im getting them to check.. |
|
Back to top |
|
 |
flsb |
Posted: Mon Nov 04, 2019 11:25 pm Post subject: |
|
|
Apprentice
Joined: 01 Apr 2010 Posts: 43
|
|
Back to top |
|
 |
HubertKleinmanns |
Posted: Tue Nov 05, 2019 12:49 am Post subject: |
|
|
 Shaman
Joined: 24 Feb 2004 Posts: 732 Location: Germany
|
flsb wrote: |
http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg1IT27924
will ask the third party to update the MQ to 9.0.1.3 fixpack and test again..
hope this solves the issue.. |
Do you mean "9.1.0.3"? _________________ Regards
Hubert |
|
Back to top |
|
 |
Joseph88 |
Posted: Mon Dec 02, 2019 12:27 pm Post subject: Re: 1300 character Message not transmitted |
|
|
Guest
|
flsb wrote: |
Hi everyone,
My issue is similar to the thread "Messages stalled on XMITQ" but it is slightly different..
i usually can google and found the solution to my MQ problems but this issue really had me running in circles..
No FDC file created.. running MQ 9.1.0.3 in Linux RHEL7
Error in AMQERR log
Quote: |
AMQ9259E: Connection timed out from host 'xxx'.
EXPLANATION:
A connection from host 'xxx' over TCP/IP timed out.
ACTION:
The select() [TIMEOUT] 60 seconds call timed out. Check to see why data was not
received in the expected time. Correct the problem. Reconnect the channel, or
wait for a retrying channel to reconnect itself.
AMQ9999E: Channel 'xxx.CHANNEL' to host 'xxx' ended
abnormally.
EXPLANATION:
The channel program running under process ID 26742 for channel
'xxx.CHANNEL' ended abnormally. The host name is 'xxx'; in
some cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. |
Other channels to the same location is running OK, and only this channel is with messages stuck in XMITQ.
It looks like the message is not able to fully transmit to the destination.
Unable to find amqsbcg in /opt/mqm/bin
We split the 1.3k characters message to smaller chunks and is able to send through but with altering the channel batchsz to 1.
Another weird thing is we currently migrated to MQ v9.1 from MQv5.3 (AIX).
While it works perfectly in MQv5.3 AIX previously.
WE have few parties with different channels Rachat prêt and destination, but out of 10-20 parties, only 2 parties are having this issue..
I searched high and low and it all asked to contact network side.. but the channel is able to ping, it just data stuck in XMITQ. Network has found no issue at their end.
Would appreciate anybody that has experienced this before..
|
Hi, very interesting thank you for entrusting us this. I wonder if we can know more about it if it's possible? Thank you in advance for your feedback. Good continuation. |
|
Back to top |
|
 |
bruce2359 |
Posted: Mon Dec 02, 2019 1:38 pm Post subject: Re: 1300 character Message not transmitted |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Joseph88 wrote: |
Hi, very interesting thank you for entrusting us this. I wonder if we can know more about it if it's possible? Thank you in advance for your feedback. Good continuation. |
Know more about what? _________________ 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 |
|
 |
RogerLacroix |
Posted: Mon Dec 02, 2019 3:07 pm Post subject: |
|
|
 Jedi Knight
Joined: 15 May 2001 Posts: 3264 Location: London, ON Canada
|
|
Back to top |
|
 |
bruce2359 |
Posted: Mon Dec 02, 2019 3:13 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
RogerLacroix wrote: |
Mostly likely it is spam. Someone should flag that UserId. |
Will give one more chance ... _________________ 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 |
|
 |
gbaddeley |
Posted: Tue Dec 03, 2019 5:52 pm Post subject: Re: 1300 character Message not transmitted |
|
|
 Jedi Knight
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
|
flsb wrote: |
We split the 1.3k characters message to smaller chunks and is able to send through but with altering the channel batchsz to 1. |
Bear in mind that this hack has no technical justification and does not do anything to identify or resolve the root cause of this issue. _________________ Glenn |
|
Back to top |
|
 |
Joseph88 |
Posted: Sun Dec 08, 2019 12:37 pm Post subject: |
|
|
Guest
|
bruce2359 wrote: |
RogerLacroix wrote: |
Mostly likely it is spam. Someone should flag that UserId. |
Will give one more chance ... |
hello, why are you talking about spam? I said that it was interesting because I also had the same problem over the Messages blocked on XMITQ ".
and by reading your words I found the solution to that! |
|
Back to top |
|
 |
gbaddeley |
Posted: Sun Dec 08, 2019 2:32 pm Post subject: |
|
|
 Jedi Knight
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
|
Joseph88 wrote: |
hello, why are you talking about spam? I said that it was interesting because I also had the same problem over the Messages blocked on XMITQ ". and by reading your words I found the solution to that! |
Hi Joseph88. I read a few of your other posts on the forum, to assure myself that you were not a spammer. I suspect that other members of the forum saw your somewhat fractured and unusual English expression in a different light. It would have been good to include at least some MQ technical context on your experiences or concerns. _________________ Glenn |
|
Back to top |
|
 |
bruce2359 |
Posted: Sun Dec 08, 2019 5:07 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Joseph88 wrote: |
I said that it was interesting because I also had the same problem |
From time to time, someone joins this forum, and appears to be a lurker (someone who watches, but doesn't really participate). Lurkers seem to disclose little, like "Interesting" and "I had the same problem" without offering any details (such as experience, o/s, product VMR, testing you've done, results from those tests).
Apologies if I've mis-characterized you. _________________ 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 |
|
 |
|