| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Getting MQ connection error 2012 in MQ v7.5 |
« View previous topic :: View next topic » |
| Author |
Message
|
| prempal |
 Posted: Sat Jan 17, 2015 9:04 am Post subject: Getting MQ connection error 2012 in MQ v7.5 |
 |
|
Newbie
Joined: 17 Jan 2015
Posts: 1
|
I have deployed application on 32 bit server which has MQ version 7.0, from this server I am able to connect remote Q server(32bit)] which is also having same MQ 7.0 version. This scenario working fine.
When I have deployed same code to 64bit server which has MQ v7.5.
from this server I am not able to make connection to same remote Q server as connected in 32bit machine with MQ 7.0 version. this scenario is failing and showing below errors.
App+MQ V7.0(32bit server) ----able to connect to --- Remote MQ V7.0(32bit server)
App+MQ V7.5(64bit) ----Not able to connect to --- Remote MQ V7.0(32bit server)
Please help me....
Following are the error logs
Fri Jan 16 06:12:53 **** Slave process #1 [pid=10420368] created for recalling service ****
Fri Jan 16 06:12:53 **** On Main process [pid=10879118] recall master socket [4] closed ****
Fri Jan 16 06:12:53 ------ POST SERVICE INITIATED [pid=10879118] -------
Fri Jan 16 06:12:53 process_post_refund() - starting
Fri Jan 16 06:12:53 ------ RECALL SERVICE INITIATED [pid=10420368][np=1] -------
Fri Jan 16 06:12:53 rsd_signalhandler(): starting ... [pid=10420368] ****
Fri Jan 16 06:12:53 -- Entering to MQ listening loop recalling service [pid=10420368][hid=183413158] --
Fri Jan 16 06:12:53 MSGID stack initiated [sizeof(msgidstack)=768][#entries=32]
Fri Jan 16 06:12:53 start_mq_session(): ERROR - MQCONN(MQSTAGE) failed : mq_retcode - 2, mq_reason - 2012
Fri Jan 16 06:12:53 mq_listener_thread(): sleeping 30 secs ....
Fri Jan 16 06:12:53 --- Entering to TCP/IP listening loop recalling service [pid=10420368] ---
Fri Jan 16 06:12:53 ip_listener_thread(): accepting connection [iteration=1]
Fri Jan 16 06:13:23 start_mq_session(): ERROR - MQCONN(MQSTAGE) failed : mq_retcode - 2, mq_reason - 2012
Fri Jan 16 06:13:23 mq_listener_thread(): sleeping 30 secs ....
Fri Jan 16 06:13:53 start_mq_session(): ERROR - MQCONN(MQSTAGE) failed : mq_retcode - 2, mq_reason - 2012
Fri Jan 16 06:13:53 mq_listener_thread(): sleeping 30 secs ....
Fri Jan 16 06:14:23 start_mq_session(): ERROR - MQCONN(MQSTAGE) failed : mq_retcode - 2, mq_reason - 2012
Fri Jan 16 06:14:23 mq_listener_thread(): sleeping 30 secs ....
Fri Jan 16 06:14:53 start_mq_session(): ERROR - MQCONN(MQSTAGE) failed : mq_retcode - 2, mq_reason - 2012
Fri Jan 16 06:14:53 mq_listener_thread(): sleeping 30 secs .... |
|
| Back to top |
|
 |
| PaulClarke |
| Posted: Sat Jan 17, 2015 11:13 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
Are there any errors reported in the MQ error logs ? Either in the client or the server?
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| tczielke |
| Posted: Sat Jan 17, 2015 12:47 pm Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
| For the application that you have deployed on the 64 bit server, is the application running as a 32 bit or 64 bit application? Based on that answer, are you referencing the correct MQ library directory (i.e. the /opt/mqm/lib 32 bit directory for a 32-bit application or the /opt/mqm/lib64 64-bit directory for a 64 bit application) for the MQ shared object files that your application will need to reference? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Jan 19, 2015 6:08 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| If the machine has MQ 7.5 on it, then you need to either issue setmqenv or setmqinst. |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Mon Jan 19, 2015 12:43 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
From the manual:
| Quote: |
2012 (X'07DC') MQRC_ENVIRONMENT_ERROR
Explanation:
The call is not valid for the current environment.
- On z/OS, one of the following applies:
* An MQCONN or MQCONNX call was issued, but the application has been linked with an adapter that is not supported in the environment in which the application is running. For example, this can arise when the application is linked with the MQ RRS adapter, but the application is running in a DB2 Stored Procedure address space. RRS is not supported in this environment. Stored Procedures wishing to use the MQ RRS adapter must run in a DB2 WLM-managed Stored Procedure address space.
* An MQCMIT or MQBACK call was issued, but the application has been linked with the RRS batch adapter CSQBRSTB. This adapter does not support the MQCMIT and MQBACK calls.
* An MQCMIT or MQBACK call was issued in the CICS or IMS environment.
* The RRS subsystem is not up and running on the z/OS system that ran the application.
- On HP OpenVMS, OS/2«, i5/OS, Compaq NonStop Kernel, UNIX« systems, and Windows, one of the following applies:
* The application is linked to the wrong libraries (threaded or nonthreaded).
* An MQBEGIN, MQCMIT, or MQBACK call was issued, but an external unit-of-work manager is in use. For example, this reason code occurs on Windows when an MTS object is running as a DTC transaction. This reason code also occurs if the queue manager does not support units of work.
* The MQBEGIN call was issued in an MQ client environment.
* An MQXCLWLN call was issued, but the call did not originate from a cluster workload exit.
- On Windows, when using the managed .NET client, an attempt was made to use one of the unsupported features:
* Unmanaged channel exits
* Secure Sockets Layer (SSL)
* XA Transactions
* Communications other than TCP/IP
* Channel compression
Completion Code:
MQCC_FAILED
Programmer Response:
Do one of the following (as appropriate):
- On z/OS:
* Link the application with the correct adapter.
* Modify the application to use the SRRCMIT and SRRBACK calls in place of the MQCMIT and MQBACK calls. Alternatively, link the application with the RRS batch adapter CSQBRRSI. This adapter supports MQCMIT and MQBACK in addition to SRRCMIT and SRRBACK.
* For a CICS or IMS application, issue the appropriate CICS or IMS call to commit or backout the unit of work.
* Start the RRS subsystem on the z/OS system that is running the application.
- In the other environments:
* Link the application with the correct libraries (threaded or nonthreaded).
* Remove from the application the call that is not supported.
|
The part that applies to you is:
| Quote: |
| * The application is linked to the wrong libraries (threaded or nonthreaded). |
On your 32-bit server, the path to the MQ 32-bit library is the default but on the 64-bit server, the path to the MQ 64-bit library is the default. Hence, that is why you are getting RC of 2012.
Use setmqenv command with the "-x 32" option or you can explicitly set LD_LIBRARY_PATH to where you installed the 32-bit MQ libraries (i.e. /opt/mqm/lib/ ).
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
