|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
5.3 client JAR's with WMQ 6.0 |
« View previous topic :: View next topic » |
Author |
Message
|
mqsnbmp1 |
Posted: Wed Mar 08, 2006 6:22 am Post subject: |
|
|
Apprentice
Joined: 18 Oct 2005 Posts: 25
|
Code:
Code: |
...
FileInputStream cfgFile = new FileInputStream(cfgFname);
Properties appProperties = new Properties();
appProperties.load(cfgFile);
InitialContext ctx = new InitialContext(appProperties); //throws Exception
...
|
Exception:
Code: |
javax.naming.NamingException: Unable to connect to the admin queue. Exception was: javax.jms.JMSSecurityException: MQJMS2013: invalid security authentication supplied for MQQueueManager [Root exception is javax.jms.JMSSecurityException: MQJMS2013: invalid security authentication supplied for MQQueueManager]
at com.ibm.mq.jms.context.MQContext.<init>(MQContext.java:278)
at com.ibm.mq.jms.context.WMQInitialContextFactory.getInitialContext(WMQInitialContextFactory.java:29)
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.init(Unknown Source)
at javax.naming.InitialContext.<init>(Unknown Source)
.......
Caused by: javax.jms.JMSSecurityException: MQJMS2013: invalid security authentication supplied for MQQueueManager
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2022)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1496)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:150)
at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:185)
at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:112)
at com.ibm.mq.jms.context.MQContext.<init>(MQContext.java:271)
... 8 more
|
Config File:
Code: |
java.naming.factory.initial = com.ibm.mq.jms.context.WMQInitialContextFactory
java.naming.provider.url = servername:1414/SYSTEM.DEF.SVRCONN
|
Thanks |
|
Back to top |
|
 |
mqsnbmp1 |
Posted: Wed Mar 08, 2006 7:58 am Post subject: |
|
|
Apprentice
Joined: 18 Oct 2005 Posts: 25
|
OK. I found what has changed in 6.0 client JAR's vs. 5.3 client JAR's. I followed the suggestions in this thread: http://www.mqseries.net/phpBB2/viewtopic.php?t=24902. The difference I saw was that it doesn't really matter whether java.namimg.security.principal/credentials are specified for JNDI. All the client JAR on V6.0 cares is that the user ID that the client runs under is present on the server box and is in mqm group (it would work even if the server is a Windows box and the account on the server box is marked as disabled -- as long as it is part of mqm group, it will work). The link I referenced above states that you could submit other user ID's under JNDI properties on the client. The reality is that it doesn't matter -- if *your* user ID is not on the server under mqm group, nothing will work with 6.0 client JAR's. If it is not a bug, we'll call it a "feature" ... On the contrary, 5.3 client JAR's do not require any of this stuff. |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Mar 08, 2006 1:16 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Not quite true, but then I am not necessarily connecting the same way.
I am using the MQQueueConnectionFactory class and determined on some field input on the GUI setting the client properties and doing a qcf.connect(userid, passwd).
Of course you need for the user passed in userid to have proper authorization on the qmgr...
I believe you can no longer pass a blank user id ...
I just did a try with the 6.0 jars to 5.3 manager accross a firewall and had no trouble connecting...
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
|
|
|
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
|
|
|
|