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 » WebSphere Message Broker (ACE) Support » Can not connect to Broker (2035)

Post new topic  Reply to topic
 Can not connect to Broker (2035) « View previous topic :: View next topic » 
Author Message
Gideon
PostPosted: Wed Jan 30, 2013 1:30 pm    Post subject: Can not connect to Broker (2035) Reply with quote

Chevalier

Joined: 18 Aug 2009
Posts: 403

I am using WMQ 7.5 and WMB 8.0.0.1 (I have never used either version of these before). I isntalled both on RHEL 6.2 and brought down the firewall.

I created a Qmgr, started it and created a broker (trusted)

I rebooted and started the Qmgr and listener and was able to connect through the Windows WMQ explorer (proving the firewall is down)

So I tried to connect to the broker form that same Windows machine, but I get the following error

The user 'brk' is not authorized to connect to the queue manager 'WWQ' (MQ reason code 2035 while trying to connect.

Code:
Check that,
  1. The broker is running
  2. The TC/PIP port of the queue manager is active if it is remote


The broker is running

-bash-4.1$ mqsilist
BIP1284I: Broker 'WQM' on queue manager 'WQM' is running.
BIP8071I: Successful command completion.

The port is active


Code:
-bash-4.1$ ps -ef | grep runmqlsr
mqm       2392     1  0 14:51 pts/0    00:00:00 runmqlsr -m WQM -t tcp -p 1414
mqm       2876  2729  0 15:59 pts/0    00:00:00 grep runmqlsr


2035 is defined as MQRC_NOT_AUTHORIZED

The broker channel has the following def (ref MCAUSER)

Code:
AMQ8414: Display Channel details.
   CHANNEL(SYSTEM.BKR.CONFIG)              CHLTYPE(SVRCONN)
   ALTDATE(2013-01-29)                     ALTTIME(14.25.00)
   COMPHDR(NONE)                           COMPMSG(NONE)
   DESCR( )                                DISCINT(0)
   HBINT(300)                              KAINT(AUTO)
   MAXINST(999999999)                      MAXINSTC(999999999)
   MAXMSGL(4194304)                        MCAUSER(mqm)
   MONCHL(QMGR)                            RCVDATA( )
   RCVEXIT( )                              SCYDATA( )
   SCYEXIT( )                              SENDDATA( )
   SENDEXIT( )                             SHARECNV(10)
   SSLCAUTH(REQUIRED)                      SSLCIPH( )
   SSLPEER( )                              TRPTYPE(TCP)


When the connection to the broker is refused, the error comes back instantly, does not take any time at all

I try to connect to the Qmgr successfully from the same windows user ID as I do the broker. What it looks to me is that when I try to connect to the broker I am connecting to the machine, Qmgr and port successfully, but I am violating some authorization rule, and that authorization issues does not prevent me from connecting to theQmgr from the explorer, but I do not see any

How can I research to resolve ?
Back to top
View user's profile Send private message Send e-mail
lancelotlinc
PostPosted: Wed Jan 30, 2013 1:40 pm    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=%2Fcom.ibm.mq.csqzas.doc%2Fsy13630_.htm

Make sure your user identity is properly propagated to the Broker runtime. (Does the brk user have an account on the RHEL and is this the identity that is being used and not an Active Directory user?)
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
mgk
PostPosted: Wed Jan 30, 2013 1:54 pm    Post subject: Reply with quote

Padawan

Joined: 31 Jul 2003
Posts: 1642

MQ 7.1 and 7.5 Queue Managers are secure by default and there is some channel config to do to set it up manually (http://publib.boulder.ibm.com/infocenter/wmbhelp/v8r0m0/topic/com.ibm.etools.mft.doc/bk58230_.htm). However, if you let the Broker mqsicreatebroker command create the QM for you when you create the Broker then it will do enough of this for you automatically to allow a connection (again see the same link).

Kind regards
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Can not connect to Broker (2035)
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.