[MNT-4258] Impossible to create web content (bulk import) Created: 28-Nov-09  Updated: 31-Aug-16  Resolved: 05-Apr-10

Status: Closed
Project: Service Packs and Hot Fixes
Component/s: ZZ_Archive
Affects Version/s: 3.2.1
Fix Version/s: 3.2.1

Type: Bug
Reporter: Enrique Martinez Bonilla (Inactive) Assignee: Closed Bugs (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows XP (SP3), Alfresco-Community-3.2r-Full-Setup.exe, jdk1.6.0_17

Issue Links:
Dependency
Depends on MNT-4177 build 486: deploy on DB2 fails Closed
Related
relates to MNT-4177 build 486: deploy on DB2 fails Closed
Bug Priority:
Category 3

 Description   

An error occurred following "Getting Started with Web Content Management (WCM)
for Alfresco Community Edition 3.2r" example and creating the web content by bulk importing alfresco-sample-website.war.

10:00:56,906 ERROR [org.alfresco.web.ui.common.Utils] A system error happened during the operation: SqlMapClient operation; SQL [];
— The error occurred in alfresco/ibatis/#resource.dialect#/avm-insert-SqlMap.xml.
— The error occurred while applying a parameter map.
— Check the alfresco.avm.insert_AVMNode-InlineParameterMap.
— Check the statement (update failed).
— Cause: org.postgresql.util.PSQLException: ERROR: inserción o actualización en la tabla «avm_nodes» viola la llave foránea «fk_avm_n_acl»
Detail: La llave (acl_id)=(2509) no está presente en la tabla «alf_access_control_list».; nested exception is com.ibatis.common.jdbc.exception.NestedSQLException:
— The error occurred in alfresco/ibatis/#resource.dialect#/avm-insert-SqlMap.xml.
— The error occurred while applying a parameter map.
— Check the alfresco.avm.insert_AVMNode-InlineParameterMap.
— Check the statement (update failed).
— Cause: org.postgresql.util.PSQLException: ERROR: inserción o actualización en la tabla «avm_nodes» viola la llave foránea «fk_avm_n_acl»
Detail: La llave (acl_id)=(2509) no está presente en la tabla «alf_access_control_list».
org.springframework.dao.DataIntegrityViolationException: SqlMapClient operation; SQL [];
— The error occurred in alfresco/ibatis/#resource.dialect#/avm-insert-SqlMap.xml.
— The error occurred while applying a parameter map.
— Check the alfresco.avm.insert_AVMNode-InlineParameterMap.
— Check the statement (update failed).
— Cause: org.postgresql.util.PSQLException: ERROR: inserción o actualización en la tabla «avm_nodes» viola la llave foránea «fk_avm_n_acl»
Detail: La llave (acl_id)=(2509) no está presente en la tabla «alf_access_control_list».; nested exception is com.ibatis.common.jdbc.exception.NestedSQLException:
— The error occurred in alfresco/ibatis/#resource.dialect#/avm-insert-SqlMap.xml.
— The error occurred while applying a parameter map.
— Check the alfresco.avm.insert_AVMNode-InlineParameterMap.
— Check the statement (update failed).
— Cause: org.postgresql.util.PSQLException: ERROR: inserción o actualización en la tabla «avm_nodes» viola la llave foránea «fk_avm_n_acl»
Detail: La llave (acl_id)=(2509) no está presente en la tabla «alf_access_control_list».
...
at com.ibatis.sqlmap.engine.mapping.statement.MappedStatement.sqlExecuteUpdate(MappedStatement.java:216)
at com.ibatis.sqlmap.engine.mapping.statement.MappedStatement.executeUpdate(MappedStatement.java:94)
... 116 more

Every time this operation is done, (acl_id)=(2509) value reported is different. However, looking at alf_access_control_list table, rows with acl_id previous values were not created.

Before testing application on PostgresSQL it was tested with My SQL and error doesn't occurred.

 Comments   
Comment by Derek Hulley [X] (Inactive) [ 30-Mar-10 ]

This is not a problem for PostgreSQL (any more) but the fix may have caused a regression in DB2 on 3.2.

Comment by Derek Hulley [X] (Inactive) [ 30-Mar-10 ]

Steve, please test this scenario on DBs for 3.2SP1. I suspect that DB2 will be a fail. Assign back to me, if necessary.

Comment by Steve Rigby [X] (Inactive) [ 30-Mar-10 ]

For test creation if not alreasdy present

Comment by Alfresco QA Team (Inactive) [ 31-Mar-10 ]

We already have this functionality covered by tests within Getting Started with WCM Enterprise Selenium project we used to perform smoke tests of new Alfresco builds (as well as by a number of test-cases connected with Bulk Import in WCM tes project) . As Getting Started Guides tests are always run before any other testing activities we'll definitely won't miss this issue for DB2 during 3.2 SP1 certification.

Comment by Alfresco QA Team (Inactive) [ 31-Mar-10 ]

Successfully tested in Alfresco 3.2.1 b 486 on Mysql, Oracle, MSSQL, PostgreSQL.
But this buils failed to bootstrap on the DB2 (ALF-2301).

Comment by Steve Rigby [X] (Inactive) [ 04-Apr-10 ]

For retest in 3.3C b2758

Comment by Alfresco QA Team (Inactive) [ 05-Apr-10 ]

Successfully validated on Alfresco 3.3 CE b 2758
RHEL 5.1 x64, Tomcat 6.0.18, Mysql 5.1.40, JDK 6u16 x64, Alfresco + Open LDAP, Windows XP, FF 3

Comment by Alfresco QA Team (Inactive) [ 05-Apr-10 ]

Successfully validated in Alfresco 3.3 CE b 2758
Windows 2008, PostgreSQL 8.4.1, Tomcat 6, JDK 6 x64, Alfresco+ OpenLDAP, Windows 7, IE8

Comment by Alfresco QA Team (Inactive) [ 05-Apr-10 ]

Successfully tested in Alfresco 3.3 CE build 2758 on MySQL and PostgreSQL.
Waiting for the 3.2.1 next build to retest on DB2.
Changed Fix version appropriately.

Comment by Steve Rigby [X] (Inactive) [ 13-Apr-10 ]

For retest in 3.2 sp1 b495

Comment by Alfresco QA Team (Inactive) [ 14-Apr-10 ]

Successfully validated against Alfresco 3.2.1 EE b 495, Suse 11.1, Websphere 7.0.0.7, Oracle 10.2g, Alfresco +OpenLDAP, MacOS X 10.5.5, Safari 3.2.1

Comment by Derek Hulley [X] (Inactive) [ 31-Aug-16 ]

The component originally used was not a supported, recognisable system component with an associated component owner. Either the component never existed (it was fictional) or it has reached end-of-life.
The issues will be closed. Reopen and assign to an existing system component if necessary. Use labels appropriately.

Generated at Sat Feb 27 10:19:57 GMT 2021 using Jira 7.13.15#713015-sha1:7c5ddd2c3e1709974ae9c48c17df8edd3919fe2c.