MQSeries.net :: View topic - Debugging SVRCONN

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Debugging SVRCONN

Goto page Previous 1, 2

Debugging SVRCONN

« View previous topic :: View next topic »

Author

Message

mqjeff

Posted: Tue Oct 25, 2011 4:50 am Post subject:

Grand Master

Joined: 25 Jun 2008
Posts: 17447

It's not a problem that 127.0.0.1 is being used. It's just confusing.

If MQIPT is running on this machine, and then turning around and making client connections back to this same machine on behalf of the external party, then you need to make sure you understand on which side of the MQIPT the connections are being timed out.

If you're seeing lots of errors with 127.0.0.1, then it is likely the connections FROM MQIPT that are the ones timing out. In which case you should look at the MQIPT config, and among other things, change it to not use localhost but to use an actual IP address.

jshailes

Posted: Tue Oct 25, 2011 5:34 am Post subject:

Apprentice

Joined: 18 May 2009
Posts: 31

I've looked in the mqipt logs and when the channel goes down the error is:

Code:

Tue Oct 25 14:08:57 BST 2011 conn close x.x.x.x(3595) y.y.y.y(1414) OK 1414-5
Tue Oct 25 14:08:57 BST 2011 conn close 127.0.0.1(60874) localhost(15001) ERROR 1414-5
Tue Oct 25 14:09:07 BST 2011 conn accept x.x.x.x(4502) y.y.y.y(1414) OK 1414-2
Tue Oct 25 14:09:07 BST 2011 conn conn 127.0.0.1(42414) localhost(15001) OK 1414-2

where y.y.y.y is our external ip and x.x.x.x is the other ends external ip.

Is there any way of increasing the logging level of mqipt to see why the conn gets closed?

Would you mind looking at the config file and seeing if anything jumps out at you.

Code:

[global]
CommandPort=1881
RemoteShutDown=true
MinConnectionThreads=5
MaxConnectionThreads=100
IdleTimeout=20
ClientAccess=true
QMgrAccess=true
HTTP=false
HTTPChunking=false
Trace=0
ConnectionLog=true
MaxLogFileSize=50
AccessPW=MQIPT

#NR Specific config
[route]
Name=ACT Consultancy MQServer router
ListenerPort=1414
Destination=localhost
DestinationPort=15001
SSLServer=true
SSLServerKeyRing=/opt/mqipt/cert/ACTcert.pfx
SSLServerKeyRingPW=/opt/mqipt/cert/ACTcert.pwd
SSLServerCipherSuites=SSL_RSA_EXPORT_WITH_RC4_40_MD5
SSLServerAskClientAuth=true

[/quote]

jshailes

Posted: Tue Oct 25, 2011 7:28 am Post subject:

Apprentice

Joined: 18 May 2009
Posts: 31

I've just realised that my post has been rather misleading. I thought I knew that the channel between the remote MQ server and our own was called a server-connection channel, I've just realised that means something entirely different - in fact it is a receiver channel that keeps going down.

Display posts from previous:

Goto page Previous 1, 2

Page 2 of 2

MQSeries.net Forum Index » General IBM MQ Support » Debugging SVRCONN

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