[ https://jira.jboss.org/jira/browse/JBCACHE-1410?page=com.atlassian.jira.p... ] Manik Surtani commented on JBCACHE-1410: ---------------------------------------- Very hard to recreate or unit test as the timing is subtle, but this is a problem. Managed to reproduce by introducing a barrier in the JDBCCacheLoader.addNewSubtree() method to wiat for > 1 thread hitting this code, and true enough it does happen. Since put() essentially gets a striped lock for the Fqn being written to and not any parent nodes (since we don't know if any of the parents need creation at this stage) the correct solution should be to get a write lock for the node being inserted in addNewSubtree(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBCACHE-1410?page=com.atlassian.jira.p... ] Manik Surtani resolved JBCACHE-1410. ------------------------------------ Resolution: Done -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBCACHE-1410?page=com.atlassian.jira.p... ] Manik Surtani commented on JBCACHE-1410: ---------------------------------------- See JBCACHE-1413 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBCACHE-1410?page=com.atlassian.jira.p... ] Manik Surtani updated JBCACHE-1410: ----------------------------------- Fix Version/s: 2.2.1.GA 2.2.1.CR1 (was: 2.X) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBCACHE-1410?page=com.atlassian.jira.p... ] Manik Surtani reassigned JBCACHE-1410: -------------------------------------- Assignee: Mircea Markus (was: Manik Surtani) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBCACHE-1410?page=com.atlassian.jira.p... ] Tomas Frastia commented on JBCACHE-1410: ---------------------------------------- Hi I have the same problem and I think I managed to get it fixed. The problem was in class org.jboss.cache.loader.AdjListJDBCCacheLoader in method populatePreparedStatementForInsert(). A wrong SQL insert query is used when saving a business-object. If the business-object is larger than 4000 bytes then the SQL insert query fails and returns an error code ORA-01461. My fix: I changed the SQL insert query by replacing the second parameter from '?' to 'empty_blob()' and after a successfull insert into the DB I have selected the inesrted row and put it into blob data via java.sql.ResultSet. I uploaded corrected class and simple to http://community.jboss.org/message/531561#531561 Tomas, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira