| Author |
Message
|
| Vamz |
 Posted: Tue May 02, 2006 7:54 pm Post subject: MQSeries - WL8.1 User name getting truncated to 12 chars |
 |
|
Newbie
Joined: 02 May 2006
Posts: 2
|
I have an MDB deployed on Weblogic 8.1 server, it works fine if I startup weblogic from command promt.
It has authentication issues when I run weblogic as an NT service under a NT Domain account, The NT Domain account used is 16 chars long and I have no control length of account name as it is defined per company IT standards. Looks like the account name is getting truncated to 12 chars, I see this in the Event log
java.naming.provider.url=file:////MQSERVER/JNDI
java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory
SECURITY_AUTHENTICATION=NONE
MQC.TRANSPORT_PROPERTY=MQC.TRANSPORT_MQSERIES_CLIENT
I did setmqaut for the domain account I am using.
Please help! How can I get around this issue of MQSeries truncating the account name to 12 chars? 
Thanks
Vamsi |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue May 02, 2006 7:58 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Maybe it's just the eventlog viewer that's truncating the username. Maybe it's the eventlog writer that's truncating the username.
Maybe the MQ documentation has information on how long usernames can be.
Maybe you didn't issue the correct setmqaut commands.
Maybe you didn't include any actual error messages or MQ reason codes to prove that you are actually having an issue because of the username at all - maybe you did something wrong in the WL config or the MDB code.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vamz |
| Posted: Wed May 03, 2006 12:49 pm Post subject: |
|
|
Newbie
Joined: 02 May 2006
Posts: 2
|
Thanks for you time, here are more details on the issue I am seeing. Appreciate any input. I read information about MQJMS2013 on this forum and also on IBM manuals etc., but I am not able to resolve the issue. 
Thanks
Vamsi
MQ Commands used
setmqaut -m NIAGIM1 -n PDSL.NIAGIM1.XMLEVT -t queue -p AMERICAS\ServiceHarmony +browse +get +put
setmqaut -m NIAGIM1 -n PDSL.NIAGIM1.XMLEVT -t queue -p ServiceHarmony +browse +get +put
setmqaut -m NIAGIM1 -n PDSL.NIAGIM1.XMLEVT -t queue -g mqi +browse +get +put
Event Viewer \ Application log:
Entity 'serviceharmo' has insufficient authority to access object 'NIAGIM1'.
The specified entity is not authorized to access the required object. The following requested permissions are unauthorized: connect
Ensure that the correct level of authority has been set for this entity against the required object, or ensure that the entity is a member of a privileged group.
Exception on Weblogic server:
'javax.jms.JMSSecurityException: MQJMS2013: invalid security authentication supplied for MQQueueManager' Linked exception = 'com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2035
MQJE036: Queue manager rejected connection attempt'.
javax.jms.JMSSecurityException: MQJMS2013: invalid security authentication supplied for MQQueueManager
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2050)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1532)
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 weblogic.ejb20.internal.JMSConnectionPoller.getConnection(JMSConnectionPoller.java:580)
at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1951)
at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1180)
at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:978)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.contact admin(SecurityManager.java:118)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:50)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178) |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed May 03, 2006 6:23 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| jefflowrey wrote: |
Maybe it's just the eventlog viewer that's truncating the username. Maybe it's the eventlog writer that's truncating the username.
Maybe the MQ documentation has information on how long usernames can be.
Maybe you didn't issue the correct setmqaut commands.
Maybe you didn't include any actual error messages or MQ reason codes to prove that you are actually having an issue because of the username at all - maybe you did something wrong in the WL config or the MDB code. |
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Wed May 03, 2006 8:56 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
| fjb_saper wrote: |
| jefflowrey wrote: |
| Maybe the MQ documentation has information on how long usernames can be. |
|
Is it 12.    
Regards,
Roger
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
|
|
