ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » AMQ9213 Communications error in getpeername

Post new topic  Reply to topic
 AMQ9213 Communications error in getpeername « View previous topic :: View next topic » 
Author Message
iberejr
PostPosted: Mon Feb 24, 2014 7:31 am    Post subject: AMQ9213 Communications error in getpeername Reply with quote

Newbie

Joined: 24 Feb 2014
Posts: 3

Hi, I am a MQ administrator, and also a network guy, and one of my MQs start to flood my logs with 3 or 4 occurrences of AMQ9213 and AMQ9492. The messagens seems to go to the other side, despite that every day we had some kind of outage, or slow throughput
I realize that 107 (X'6B') means ENOTCONN - Transport endpoint is not connected, and I saw here in this forum the thread: "AMQ 9213 for amqrmppa" but I cannot figure out why this is happening, or how can I troubleshoot this

The log messages are:


----- amqrmrsa.c : 524 --------------------------------------------------------
02/24/2014 12:23:01 PM - Process(21271.1863529) User(mqm) Program(amqrmppa)
Host(xxxxmq.xxxx.br)
AMQ9213: A communications error for TCP/IP occurred.

EXPLANATION:
An unexpected error occurred in communications.
ACTION:
The return code from the TCP/IP (getpeername) call was 107 (X'6B'). Record
these values and tell the systems administrator.
----- amqccita.c : 1897 -------------------------------------------------------
02/24/2014 12:23:01 PM - Process(21271.1863529) User(mqm) Program(amqrmppa)
Host(xxxxmq.xxxx.br)
AMQ9492: The TCP/IP responder program encountered an error.

EXPLANATION:
The responder program was started but detected an error.
ACTION:
Look at previous error messages in the error files to determine the error
encountered by the responder program.
Back to top
View user's profile Send private message Send e-mail
JosephGramig
PostPosted: Mon Feb 24, 2014 10:01 am    Post subject: Reply with quote

Grand Master

Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA

What platform and fix level of OS?
What version and fix level of MQ?
What do your channel and TCP stanzas say (that's in your qm.ini file)?
Back to top
View user's profile Send private message AIM Address
iberejr
PostPosted: Mon Feb 24, 2014 11:27 am    Post subject: Reply with quote

Newbie

Joined: 24 Feb 2014
Posts: 3

Hi, I am running a:
Name: WebSphere MQ
Version: 7.0.1.3
CMVC level: p701-103-100813
BuildType: IKAP - (Production)

in:

mqconfig: V3.7 analyzing Red Hat Enterprise Linux Server release 6.1
(Santiago) settings for WebSphere MQ V7.0

System V Semaphores
semmsl (sem:1) 500 semaphores IBM>=500 PASS
semmns (sem:2) 11558 of 256000 semaphores (4%) IBM>=256000 PASS
semopm (sem:3) 250 operations IBM>=250 PASS
semmni (sem:4) 105 of 1024 sets (10%) IBM>=1024 PASS

System V Shared Memory
shmmax 68719476736 bytes IBM>=268435456 PASS
shmmni 123 of 4096 sets (3%) IBM>=4096 PASS
shmall 130530 of 4294967296 pages (0%) IBM>=2097152 PASS

System Settings
file-max 8096 of 524288 files (1%) IBM>=524288 PASS
tcp_keepalive_time 300 seconds IBM<=300 PASS

Current User Limits (mqm)
nofile (-Hn) 10240 files IBM>=10240 PASS
nofile (-Sn) 10240 files IBM>=10240 PASS
nproc (-Hu) 122 of 4096 processes (2%) IBM>=4096 PASS
nproc (-Su) 122 of 4096 processes (2%) IBM>=4096 PASS


And in mq.ini, I had only these lines for channels:
mq.ini:
TCP:
Port=1414
KeepAlive=YES
CHANNELS:
MaxInitiators=100
MaxActiveChannels=1000
MaxChannels=1000
Back to top
View user's profile Send private message Send e-mail
JosephGramig
PostPosted: Mon Feb 24, 2014 11:41 am    Post subject: Reply with quote

Grand Master

Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA

You are way behind on maintenance, so apply that.
And add the following two lines to your Channel stanzas:
Code:
   AdoptNewMCACheck=ALL
   AdoptNewMCA=ALL


This should help with channel operation. Not sure it will fix your specific issue. Of course, you have to stop/start the Qmgr to have changes take effect.
Back to top
View user's profile Send private message AIM Address
iberejr
PostPosted: Thu Feb 27, 2014 8:40 am    Post subject: Reply with quote

Newbie

Joined: 24 Feb 2014
Posts: 3

Hi Joseph, I added the two AdoptNewMCA lines in mq.ini and restart my mq, and the errors still happening...

Any other idea ?
Back to top
View user's profile Send private message Send e-mail
Vitor
PostPosted: Thu Feb 27, 2014 9:03 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

iberejr wrote:
Any other idea ?


JosephGramig wrote:
You are way behind on maintenance, so apply that

_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
JosephGramig
PostPosted: Thu Feb 27, 2014 10:56 am    Post subject: Reply with quote

Grand Master

Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA

Do you need me to Google the link to the fixes for you?

And if you open a PMR, they will want you to apply maintenance to RHEL if you need it.
Back to top
View user's profile Send private message AIM Address
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » AMQ9213 Communications error in getpeername
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.