ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » DB2 JDBC Connection - version v6107 - Null userid

Post new topic  Reply to topic
 DB2 JDBC Connection - version v6107 - Null userid « View previous topic :: View next topic » 
Author Message
wyatt
PostPosted: Tue May 10, 2011 7:13 am    Post subject: DB2 JDBC Connection - version v6107 - Null userid Reply with quote

Voyager

Joined: 28 Nov 2004
Posts: 76
Hello

Any suggestions for resolving the following error

An error occurred in node: TestJDBCType4 There was a problem establishing a connection to the given database URL: datasource URL = jdbc:db2://dds1.d6.devl.simon.works.com:50000/APPB1:user=xxxx Exception details: [ibm][db2][jcc][t4][10205][11234] Null userid is not supported. : MSAD6.dcffbbd5-2e01-0000-0080-c648e32044c5: /build/S610_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 739: JDBCType4Connection::createXAConnection: :

May 9 16:39:42 dms1 user:info WebSphere Broker v6107[864334]: (MSAD6.MKRUEGER)[6434]BIP6232E: An error occurred in node: <com.ibm.broker.plugin.MbRecoverableException class:com.ibm.broker.jdbctype4.localtrxn.JDBCType4SinglePhaseTrxnHandlerErrors@26442644 method:JDBCType4SinglePhaseTrxnHandler::getConnection source:BIPv610 key:4362 > at com.ibm.broker.jdbctype4.localtrxn.JDBCType4SinglePhaseTrxnHandlerErrors.throwException(JDBCType4SinglePhaseTrxnHandlerErrors.java:213) at com.ibm.broker.jdbctype4.localtrxn.JDBCType4SinglePhaseTrxnHandler.getConnection(JDBCType4SinglePhaseTrxnHandler.java:371) at com.ibm.broker.jdbctype4.connfact.JDBCType4ConnectionFactory.getConnection(JDBCType4ConnectionFactory.java:158) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at com.ibm.broker.plugin.MbNode.ge




..this error is occurring with/without using
"mqsichangeproperties MSAD6 -c JDBCProviders -o DB2 -n securityIdentity -v jdbcSecurityIdentity"

Thanks
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue May 10, 2011 8:16 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447
The error you're getting indicates that Broker is not passing a userId to the JDBC connection.

So the -n securityIdentity parameter identifies that you have created an mqsisetdbparms entry with the name 'jdbcSecurityIdentity'.

So did you issue an mqsisetdbparms command? Did you properly format the id to include the relevant jdbc: portion, so that Broker would know you wanted to use it as a JDBC security entry?
Back to top
View user's profile Send private message
wyatt
PostPosted: Tue May 10, 2011 8:32 am    Post subject: Reply with quote

Voyager

Joined: 28 Nov 2004
Posts: 76
Thanks for the quick reply.

Yes,
mqsisetdbparms MSAD6 -n jdbc::jdbcSecurityIdentity -u someuser -p somesecretpassword


The corresponding securityIdentity property for the JDBCProvider configurable service..
securityIdentity='jdbcSecurityIdentity'

..didnt really want to use the securityIdentity but I was getting the same problem when the userid/password were provided in the connectionUrlFormat; For example
mqsichangeproperties MSAD6 -c JDBCProviders -o DB2 -n connectionUrlFormat -v jdbc:db2://dds1.d6.devl.simon.com:50000/APPDB:user=someuser;password=somesecretpassword;
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue May 10, 2011 8:47 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447
Ah!

So the problem is that you changed the connectionURLFormat to stop being a pattern.

DO NOT EVER CHANGE THE CONNECTIONURLFORMAT.

Restore it back to the sample, including the "[user]" values.
Back to top
View user's profile Send private message
wyatt
PostPosted: Tue May 10, 2011 9:06 am    Post subject: Reply with quote

Voyager

Joined: 28 Nov 2004
Posts: 76
Thank You Much.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » DB2 JDBC Connection - version v6107 - Null userid
Jump to:  



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
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.