Portlet deployment on weblogic: db duplicate key exception
----------------------------------------------------------
Key: PORTAL-195
URL: http://www.jahia.net/jira/browse/PORTAL-195
Project: Jahia Corporate Portal Server
Issue Type: Bug
Components: Weblogic
Affects Versions: Portal 5.0 SP4
Reporter: Damien Saulnier
Assignee: Serge Huber
Priority: Critical
Fix For: Portal 5.0 SP5
504 hf10
weblo 10.3
I have deployed a portlet on Weblogic, as module of the Jahia web application.
Then, I have redeployed my Jahia application. It seems that such operation is
enough to register the portlet in Jetspeed (entries added in
portlet_application, portlet_definition, ... ), so that when I try to manually
add my portlet in Jahia admin center, the operation fails due to a constraint
violation (in table portlet_application ). The problem is that I really need to
perform this manual add, as the portlet is only registered in Jetspeed tables,
and not in Jahia tables (nothing in jahia_app* ).
So I think that when we manually add a portlet, it should be detected if the
portlet is already registered in Jetspeed, and if it is, we should at least
skip this operation, as it prevents the portlet being also registered in Jahia
tables. Maybe the best solution would be to update Jetspeed tables if we detect
already existing definitions, but if we could at least skip, it would be great.
2008-12-01 15:47:18,203: ERROR
[org.jahia.services.webapps_deployer.GenericWebAppsDeployerBaseService] - Error
during deployment of your portlet webapps (rewriting of files by jetspeed)
org.springframework.dao.DataIntegrityViolationException: (OJB operation): data
integrity violated by SQL ''; nested exception is
com.mysql.jdbc.exceptions.MySQLIntegrityConstraintViolationException: Duplicate
entry 'JobDetail' for key 2
com.mysql.jdbc.exceptions.MySQLIntegrityConstraintViolationException: Duplicate
entry 'JobDetail' for key 2
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:925)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2864)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1567)
at
com.mysql.jdbc.ServerPreparedStatement.serverExecute(ServerPreparedStatement.java:1154)
at
com.mysql.jdbc.ServerPreparedStatement.executeInternal(ServerPreparedStatement.java:679)
at
com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1394)
at
com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1308)
at
com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1293)
at
weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:159)
at
org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeInsert(JdbcAccessImpl.java:216)
at
org.apache.ojb.broker.core.PersistenceBrokerImpl.storeToDb(PersistenceBrokerImpl.java:1754)
at
org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:813)
at
org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:726)
at
org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersistenceBroker.java:175)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.jahia.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
jira_list mailing list
[email protected]
http://lists.jahia.org/cgi-bin/mailman/listinfo/jira_list
