| Author |
Message
|
| Vitor |
 Posted: Thu Oct 30, 2014 4:47 am Post subject: |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pandeg wrote: |
| Not sure if I am using the old version |
You need to be sure.
You certainly can't eliminate it as a source of your problem until you are.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| pandeg |
| Posted: Thu Oct 30, 2014 5:35 am Post subject: |
|
|
Disciple
Joined: 21 Oct 2014
Posts: 195
|
| I replaced all the existing IBM mq jars from my application with version 8.0.0 version , but it is still showing the same exception. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 30, 2014 6:42 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pandeg wrote: |
| I replaced all the existing IBM mq jars from my application with version 8.0.0 version , but it is still showing the same exception. |
a) The jar files shouldn't be in your application they should be in the classpath
b) Did you remove the old jar files from the classpath?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| pandeg |
| Posted: Thu Oct 30, 2014 7:53 am Post subject: |
|
|
Disciple
Joined: 21 Oct 2014
Posts: 195
|
| I have added these jar files as external jars from java build path in eclipse. Is it not correct way. |
|
| Back to top |
|
|
| pandeg |
| Posted: Thu Oct 30, 2014 8:47 am Post subject: |
|
|
Disciple
Joined: 21 Oct 2014
Posts: 195
|
I am able to execute with these jar but getting following exception although I have no security enabled on MQ. It is asking for username and password.
Should I remove the jar which contains security exception
com.ibm.msg.client.jms.DetailedJMSSecurityException: JMSWMQ2013: The security authentication was not valid that was supplied for QueueManager 'QM01' with connection mode 'Client' and host name '14.13.22.125(1425)'.
Please check if the supplied username and password are correct on the QueueManager to which you are connecting.
at com.ibm.msg.client.wmq.common.internal.Reason.reasonToException(Reason.java:514)
at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:214)
at com.ibm.msg.client.wmq.internal.WMQConnection.<init>(WMQConnection.java:406)
at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createV7ProviderConnection(WMQConnectionFactory.java:6381)
at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createProviderConnection(WMQConnectionFactory.java:5737)
at com.ibm.msg.client.jms.admin.JmsConnectionFactoryImpl._createConnection(JmsConnectionFactoryImpl.java:285)
at com.ibm.msg.client.jms.admin.JmsConnectionFactoryImpl.createConnection(JmsConnectionFactoryImpl.java:233)
at com.ibm.mq.jms.MQConnectionFactory.createCommonConnection(MQConnectionFactory.java:6016)
at com.ibm.mq.jms.MQConnectionFactory.createConnection(MQConnectionFactory.java:6041)
at MQJMSUtil.getConnection(MQJMSUtil.java:237)
at MQJMSUtil.getSession(MQJMSUtil.java:232)
at MQJMSUtil.mqPut(MQJMSUtil.java:65)
at MQMainSenderThread.processmessage(MQMainSenderThread.java:1597)
at MQMainSenderThread$1.run(MQMainSenderThread.java:1552)
Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED').
at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:202)
... 12 more |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 30, 2014 9:05 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pandeg wrote: |
| I have no security enabled on MQ. |
How have you disabled the security? Or have you simply not set any security up?
| pandeg wrote: |
| Should I remove the jar which contains security exception |
Is it your standard practice every time you get a Java exception to simply remove the offending jar? You must have very few functions available.....
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Oct 30, 2014 9:07 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Good you are making progress. But MQ V8 introduced a feature where you could authenticate the connection with a username/password.
There are some intersting posts in the Security forum about how to setup the QMGR, SVRCONN Channel and Queues for the connection
There will be events recorded in the Server MQ Error logs that tell you exactly what is not authorised.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| pandeg |
| Posted: Thu Oct 30, 2014 9:39 am Post subject: |
|
|
Disciple
Joined: 21 Oct 2014
Posts: 195
|
| There is no security setup on the Queue Manager. I don't just simply remove the jar ,here I copied all the jars as I didn't know what all jars are useful for me. |
|
| Back to top |
|
|
| pandeg |
| Posted: Thu Oct 30, 2014 9:50 am Post subject: |
|
|
Disciple
Joined: 21 Oct 2014
Posts: 195
|
| as i checked , exception is getting generated from com.ibm.mqjms.jar. Can we disable this feature of authenticating the connection with a username/password in version 8. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 30, 2014 9:53 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pandeg wrote: |
| There is no security setup on the Queue Manager. |
Then I repeat, how did you disable it? By default the queue manager security component (OAM) which is giving you that 2035 error is enabled so what steps have you taken to make you claim it's not set up?
Or (again repeating) do you mean that there's no security set up in the sense that you've taken no action to configure the OAM and add any authorisations? In which case I've found your problem.
I also echo the comments of my worthy associate about the v8 client
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 30, 2014 9:56 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pandeg wrote: |
| exception is getting generated from com.ibm.mqjms.jar. |
So the JMS exception is being generated from the jar file that provides all of the JMS support for WMQ? Who would have guessed?
| pandeg wrote: |
| Can we disable this feature of authenticating the connection with a username/password in version 8. |
You're very much of the "doesn't work, don't like it, rip it out" school of thought aren't you? Have you even taken the advice of my worthy associate and attempted to set up the connection correctly, or just decided you'll disable the function and move on?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 30, 2014 9:57 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pandeg wrote: |
| Can we disable this feature of authenticating the connection with a username/password in version 8. |
No.
You can go back to an earlier version of the client and try installing that properly if you don't want the feature.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| pandeg |
| Posted: Thu Oct 30, 2014 10:02 am Post subject: |
|
|
Disciple
Joined: 21 Oct 2014
Posts: 195
|
In my case I am using jar version 8.0.0 to connect to queue manager version 7.01.9. Also , i found from one of the IBM link
http://www-01.ibm.com/support/docview.wss?uid=swg21577137
which you also said that security is enabled from MQ 7.1 onwards, so its basically a client jar which may be creating a problem. |
|
| Back to top |
|
|
| pandeg |
| Posted: Thu Oct 30, 2014 10:08 am Post subject: |
|
|
Disciple
Joined: 21 Oct 2014
Posts: 195
|
| My only intention here is to perform the load testing by getting rid of the exceptions that I was getting initially. If I try to setup it may complicate my situation , that's why I asked if we can disable in my application jar. Please suggest me now what is the best possible option for me. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 30, 2014 10:58 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pandeg wrote: |
| which you also said that security is enabled from MQ 7.1 onwards, so its basically a client jar which may be creating a problem. |
You'd certainly need to go back to a version that didn't attempt to implement the security you've not got set up on the queue manager.
Or set up the security on the queue manager.
Or disable the security on the queue manager.
Or answer my questions about the security on the queue manager.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
