NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
8 replies Latest Post - 2012-12-14T09:11:58Z by asmoljo
Pinned topic null userid not supportedDSRA0010E
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
I have an application on WAS 6.0 and I get this error "Caused by: java.sql.SQLException: null userid not supportedDSRA0010E: SQL State = null, Error Code =-99.999DSRA0010E: SQL State = null, Error Code = -99,999." in SystemOut log. Test connection normally goes without error. I tried to define a user by the JAAS - J2C authentication data and also through Custom properties but the problem is always there. Does anyone have any idea what could be the problem?
Updated on 2012-12-14T09:11:58Z at 2012-12-14T09:11:58Z by asmoljo
Re: null userid not supportedDSRA0010E2012-12-13T10:51:21Z in response to asmoljoHi,
Looks like you dont have JAAS alias set, while making connection.
- create JAAS alias
- set this alias as Component auth alias and Container auth alias in Datasource.
- save changes
- restart WAS
Re: null userid not supportedDSRA0010E2012-12-13T11:43:16Z in response to gasThe problem is that the user is created and the test connection goes well , but I get this error :"Caused by: java.sql.SQLException: null userid not supportedDSRA0010E: SQL State = null, Error Code = -99.999DSRA0010E: SQL State = null, Error Code = -99.999"
Re: null userid not supportedDSRA0010E2012-12-13T11:52:36Z in response to asmoljoWhat kind of db are you using?
How are you getting DataSource, and connection from data source?
Are you using resource ref in your application?
Looks like eihter you are not getting connection from datasource configured in WAS, or you are using getConnection(user, pass) method in the code.
Re: null userid not supportedDSRA0010E2012-12-13T16:04:55Z in response to asmoljoYou need to check, if there is no same data source defined on different scope (check cell, node, server, cluster if you have).
Also verify that nodes (if you have ND) are synchronized.
If test connection from console works, and you are accessing correct jndi, then it should work. So you must have some error in your config somewhere.