Using Turbine-4 M1, Torque 3.3, and MySQL connector 5.1.21 running in Tomcat 7.0.39

I get an Exception, Failed to retrieve users, thrown from line 238 in TorqueUserManager.retrieveList()
when executing TurbineSecurity.getAuthenticatedUser("user");

When I try
criteria.clear();
        criteria.addSelectColumn("TURBINE_USER.LOGIN_NAME");
        List userList = TurbineUserPeer.doSelect(criteria);
 I get
com.workingdogs.village.DataSetException: Bad conversion: java.lang.NumberFormatException: For input string: "admin"
from the line
336    obj.setUserId(row.getValue(offset + 0).asInt());
in 329 public static void populateObject(Record row, int Offset, TurbineUser obj)
which is called from
296 public static TurbineUser row2Object(Record row,  int offset, Class cls)

TURBINE_USER is defined as
+----------------+-------------+------+-----+---------------------+-----------------------------+
| Field | Type | Null | Key | Default | Extra |
+----------------+-------------+------+-----+---------------------+-----------------------------+
| USER_ID | int(11) | NO | PRI | NULL | | | LOGIN_NAME | varchar(64) | NO | UNI | NULL | | | PASSWORD_VALUE | varchar(16) | NO | | NULL | | | FIRST_NAME | varchar(64) | NO | | NULL | | | LAST_NAME | varchar(64) | NO | | NULL | | | EMAIL | varchar(64) | YES | | NULL | | | CONFIRM_VALUE | varchar(16) | YES | | NULL | | | MODIFIED | timestamp | NO | | CURRENT_TIMESTAMP | on update CURRENT_TIMESTAMP | | CREATED | timestamp | NO | | 0000-00-00 00:00:00 | | | LAST_LOGIN | timestamp | NO | | 0000-00-00 00:00:00 | | | OBJECTDATA | mediumblob | YES | | NULL | |
+----------------+-------------+------+-----+---------------------+-----------------------------+
11 rows in set (1.16 sec)b
and contains
+---------+--------------+----------------+------------+-----------+-------+---------------+---------------------+---------------------+---------------------+------------+
| USER_ID | LOGIN_NAME | PASSWORD_VALUE | FIRST_NAME | LAST_NAME | EMAIL | CONFIRM_VALUE | MODIFIED | CREATED | LAST_LOGIN | OBJECTDATA |
+---------+--------------+----------------+------------+-----------+-------+---------------+---------------------+---------------------+---------------------+------------+
| 1 | admin | password | Turbine | Admin | NULL | NULL | 2013-04-01 09:26:38 | 0000-00-00 00:00:00 | 0000-00-00 00:00:00 | NULL | | 2 | user | password | Turbine | User | NULL | NULL | 2013-04-01 09:26:38 | 0000-00-00 00:00:00 | 0000-00-00 00:00:00 | NULL | | 3 | TurbineUser1 | password | Turbine | Usera | NULL | NULL | 2013-04-01 09:26:38 | 0000-00-00 00:00:00 | 0000-00-00 00:00:00 | NULL | | 4 | TurbineUser2 | password | Turbine | Userb | NULL | NULL | 2013-04-01 09:26:38 | 0000-00-00 00:00:00 | 0000-00-00 00:00:00 | NULL |
+---------+--------------+----------------+------------+-----------+-------+---------------+---------------------+---------------------+---------------------+------------+
4 rows in set (0.01 sec)

I surmise that the row is being read incorrectly and that the first row (at least) did not include the USER_ID column. But it does convince me that I should be able to get to the database. The problem I really want to solve is getAuthenticatedUser("user")

TR.props contains
services.SecurityService.classname=org.apache.turbine.services.security.torque.TorqueSecurityService
services.SecurityService.user.manager = org.apache.turbine.services.security.torque.TorqueUserManager



#services.SecurityService.user.class = org.apache.turbine.services.security.torque.TorqueUser #services.SecurityService.group.class = org.apache.turbine.services.security.torque.TorqueGroup #services.SecurityService.permission.class = org.apache.turbine.services.security.torque.TorquePermission #services.SecurityService.role.class = org.apache.turbine.services.security.torque.TorqueRole

services.SecurityService.userPeer.class=org.apache.turbine.om.security.peer.TurbineUserPeer

Can some give me an some ideas on debugging this?


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to