| Author |
Message
|
| psiracusa |
 Posted: Tue Jun 05, 2007 6:53 am Post subject: 2012 when testing Java Program |
 |
|
Apprentice
Joined: 17 Nov 2006
Posts: 34
|
I installed the 6.0 trial version on a Windows server for a project we are considering using MQ on and tried to run a java application that worked on my desktop. However on the server I received a 2012. The possible reasons listed in the manual for this are:
-The application is linked to the wrong libraries
(threaded or nonthreaded).
(Windows install sets env automatically and I'm just importing the com.ibm.mq object in the program. This is the only reason that seems feasible to me but I don't see where the issue is.)
– 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.
(I'm not using syncpoint control)
– The MQBEGIN call was issued in an MQ client
environment.
(Not using syncppoint.)
– An MQXCLWLN call was issued, but the call did
not originate from a cluster workload exit.
(Not using cluster workload exits.)
Any ideas? My initial thought is that it might just be an issue with the trial version because I've never encountered an issue like this using the regular version of the software. |
|
| Back to top |
|
 |
| rparti |
| Posted: Tue Jun 05, 2007 11:45 am Post subject: |
|
|
Voyager
Joined: 05 Oct 2005
Posts: 86
Location: U.S.A.
|
The manual lists the following as the corrective action
| Quote: |
| In the other environments: -- Link the application with the correct libraries (threaded or nonthreaded). -- Remove from the application the call that is not supported. |
Make sure that the class files are included |
|
| Back to top |
|
|
| psiracusa |
| Posted: Wed Jun 06, 2007 5:22 am Post subject: |
|
|
Apprentice
Joined: 17 Nov 2006
Posts: 34
|
| Just an FYI. The problem was I had specified fastpath application connections (performance testing) and the userid that was running the application wasn't in the mqm group. I took away the fastpath bindings and the error changed to a 2035 (not authorized). I moved the user to the mqm group and the program ran fine. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 06, 2007 5:30 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Fastpath bindings is generally a poor idea, that should only be used when you've already optomized your code as far as you can.
An application in fastpath mode can crash your entire qmgr.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jun 06, 2007 5:37 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| psiracusa wrote: |
| I took away the fastpath bindings and the error changed to a 2035 (not authorized). I moved the user to the mqm group and the program ran fine. |
It's generally better practice to resolve a 2035 by giving the user the authorities he requires rather than making him an administrator.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
