Thanks, I will continue looking at this.
The section that I am concerned about is the one with the null username;
2013-04-07 19:08:08,658 [http-bio-80-exec-13] DEBUG
org.apache.torque.util.SQLBuilder - SELECT TURBINE_USER.USER_ID,
TURBINE_USER.LOGIN_NAME, TURBINE_USER.PASSWORD_VALUE,
TURBINE_USER.FIRST_NAME, TURBINE_USER.LAST_NAME,
TURBINE_USER.EMAIL, TURBINE_USER.CONFIRM_VALUE, TURBINE_USER.MODIFIED,
TURBINE_USER.CREATED, TURBINE_USER.LAST_LOGIN, TURBINE_USER.OBJECTDATA
FROM TURBINE_USER WHERE TURBINE_USER.LOGIN_NAME='user'
2013-04-07 19:08:08,662 [http-bio-80-exec-13] DEBUG
org.apache.torque.util.BasePeer - Elapsed time=4 ms
2013-04-07 19:08:08,673 [http-bio-80-exec-13] DEBUG
org.apache.torque.util.SQLBuilder - SELECT TURBINE_USER.USER_ID,
TURBINE_USER.LOGIN_NAME, TURBINE_USER.PASSWORD_VALUE,
TURBINE_USER.FIRST_NAME, TURBINE_USER.LAST_NAME,
TURBINE_USER.EMAIL, TURBINE_USER.CONFIRM_VALUE, TURBINE_USER.MODIFIED,
TURBINE_USER.CREATED, TURBINE_USER.LAST_LOGIN, TURBINE_USER.OBJECTDATA
FROM TURBINE_USER WHERE TURBINE_USER.LOGIN_NAME=''
2013-04-07 19:08:08,673 [http-bio-80-exec-13] DEBUG
org.apache.torque.util.BasePeer - Elapsed time=0 ms
2013-04-07 19:13:45,884 [http-bio-80-exec-19] DEBUG
org.apache.torque.util.SQLBuilder - SELECT TURBINE_USER.USER_ID,
TURBINE_USER.LOGIN_NAME, TURBINE_USER.PASSWORD_VALUE,
TURBINE_USER.FIRST_NAME, TURBINE_USER.LAST_NAME,
TURBINE_USER.EMAIL, TURBINE_USER.CONFIRM_VALUE, TURBINE_USER.MODIFIED,
TURBINE_USER.CREATED, TURBINE_USER.LAST_LOGIN, TURBINE_USER.OBJECTDATA
FROM TURBINE_USER WHERE TURBINE_USER.LOGIN_NAME='user'
2013-04-07 19:13:45,889 [http-bio-80-exec-19] DEBUG
org.apache.torque.util.BasePeer - Elapsed time=5 ms
2013-04-07 19:13:45,898 [http-bio-80-exec-19] DEBUG
org.apache.torque.util.SQLBuilder - SELECT TURBINE_USER.USER_ID,
TURBINE_USER.LOGIN_NAME, TURBINE_USER.PASSWORD_VALUE,
TURBINE_USER.FIRST_NAME, TURBINE_USER.LAST_NAME,
TURBINE_USER.EMAIL, TURBINE_USER.CONFIRM_VALUE, TURBINE_USER.MODIFIED,
TURBINE_USER.CREATED, TURBINE_USER.LAST_LOGIN, TURBINE_USER.OBJECTDATA
FROM TURBINE_USER WHERE TURBINE_USER.LOGIN_NAME='user'
2013-04-07 19:13:45,899 [http-bio-80-exec-19] DEBUG
org.apache.torque.util.SQLBuilder - SELECT TURBINE_USER.USER_ID,
TURBINE_USER.LOGIN_NAME, TURBINE_USER.PASSWORD_VALUE,
TURBINE_USER.FIRST_NAME, TURBINE_USER.LAST_NAME,
TURBINE_USER.EMAIL, TURBINE_USER.CONFIRM_VALUE, TURBINE_USER.MODIFIED,
TURBINE_USER.CREATED, TURBINE_USER.LAST_LOGIN, TURBINE_USER.OBJECTDATA
FROM TURBINE_USER WHERE TURBINE_USER.LOGIN_NAME='user'
2013-04-07 19:13:45,900 [http-bio-80-exec-19] DEBUG
org.apache.torque.util.BasePeer - Elapsed time=1 ms
2013-04-07 19:13:45,901 [http-bio-80-exec-19] DEBUG
org.apache.torque.util.SQLBuilder - SELECT TURBINE_USER.USER_ID,
TURBINE_USER.LOGIN_NAME, TURBINE_USER.PASSWORD_VALUE,
TURBINE_USER.FIRST_NAME, TURBINE_USER.LAST_NAME,
TURBINE_USER.EMAIL, TURBINE_USER.CONFIRM_VALUE, TURBINE_USER.MODIFIED,
TURBINE_USER.CREATED, TURBINE_USER.LAST_LOGIN, TURBINE_USER.OBJECTDATA
FROM TURBINE_USER WHERE TURBINE_USER.LOGIN_NAME='user'
On 4/8/2013 2:32 AM, Thomas Vandahl wrote:
Hi Robert,
On 07.04.2013 17:58, Robert Lee wrote:
thrown from TorqueUserManager at accountExists(user.getName());
public boolean accountExists(User user)
throws DataBackendException
{
return accountExists(user.getName());
}
If I dig further down in this code I get a call to
UserPeerManager.doSelect(Criteria) which directly calls the user peer
class method doSelect() via reflection. So everything looks fine here.
The error message you get comes from a BasePeer.doSelect(). I cannot
see a call to this method in the stack trace you mention.
You may want to bump up the log level of the Turbine and Torque
loggers to DEBUG to see what really happens.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
