[jira] [Commented] (OFBIZ-7265) Could not obtain Lock on lucene index Lock
[ https://issues.apache.org/jira/browse/OFBIZ-7265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070737#comment-16070737 ] Jacques Le Roux commented on OFBIZ-7265: Michael, you mean the error in description? This should no longer happen. I reopened for another (not functional) reason explained in the comment above. > Could not obtain Lock on lucene index Lock > -- > > Key: OFBIZ-7265 > URL: https://issues.apache.org/jira/browse/OFBIZ-7265 > Project: OFBiz > Issue Type: Bug > Components: lucene >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Release > > > I found this message in error.log > |xer_default_products |DocumentIndexer |E| Could not obtain > Lock on lucene index Lock held by this virtual machine: > C:\projectASF-Mars\ofbiz\runtime\indexes\products\write.lock > Here is Jacopo's answer: > bq. We should not worry (because the "lucene" component is just an > experimental one) but let's keep an eye on it: it is caused when two threads > are trying to update documents in the Lucene index; it may happen when two > events modify data that trigger the execution of the document update. We > could consider to enhance the DocumentIndexer to properly manage these > scenarios. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9375) Missing Java Option solr.log.dir. Logging may be missing or incomplete
[
https://issues.apache.org/jira/browse/OFBIZ-9375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-9375.
--
Resolution: Fixed
At revision 1800457 I reverted r1795781 and offered a better solid solution.
Byproduct: fixed imports and tabs in OFBizSolrContextFilter.java
> Missing Java Option solr.log.dir. Logging may be missing or incomplete
> --
>
> Key: OFBIZ-9375
> URL: https://issues.apache.org/jira/browse/OFBIZ-9375
> Project: OFBiz
> Issue Type: Improvement
> Components: lucene, solr
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Release
>
>
> I noticed this error in trunk demo error.log
> bq. 2017-05-16 03:05:38,898 |0.0.0.0-startStop-1 |StartupLoggingUtils
> |E| Missing Java Option solr.log.dir. Logging may be missing or incomplete.
> It's thrown by
> https://github.com/apache/lucene-solr/blob/master/solr/core/src/java/org/apache/solr/servlet/StartupLoggingUtils.java
> I can't see nothing at https://localhost:8443/solr/#/~logging
> On dev ML Jinghai suggested to add
> {code}
> def jvmArguments = ['-Xms128M', '-Xmx1024M',
> '-Dsolr.log.dir=runtime/logs',
> '-Dsolr.log.level=INFO']
> {code}
> to main gradle. Taher mentionned that "The master build.gradle file should
> not point to any plugins"
> I put the same in both lucene and solr components build. gradle (Solrs relies
> on Lucene but our usage is specific) and saw no drawbacks.
> I must say I was not able to reproduce the "error" locally. But I anyway I
> propose to commit in the 2 plugins to reassur people who could else wonder.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Reopened] (OFBIZ-9375) Missing Java Option solr.log.dir. Logging may be missing or incomplete
[
https://issues.apache.org/jira/browse/OFBIZ-9375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reopened OFBIZ-9375:
Reopening actually the tip suggested by Jinghai did not work. I'll revert and
commit another change
> Missing Java Option solr.log.dir. Logging may be missing or incomplete
> --
>
> Key: OFBIZ-9375
> URL: https://issues.apache.org/jira/browse/OFBIZ-9375
> Project: OFBiz
> Issue Type: Improvement
> Components: lucene, solr
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Release
>
>
> I noticed this error in trunk demo error.log
> bq. 2017-05-16 03:05:38,898 |0.0.0.0-startStop-1 |StartupLoggingUtils
> |E| Missing Java Option solr.log.dir. Logging may be missing or incomplete.
> It's thrown by
> https://github.com/apache/lucene-solr/blob/master/solr/core/src/java/org/apache/solr/servlet/StartupLoggingUtils.java
> I can't see nothing at https://localhost:8443/solr/#/~logging
> On dev ML Jinghai suggested to add
> {code}
> def jvmArguments = ['-Xms128M', '-Xmx1024M',
> '-Dsolr.log.dir=runtime/logs',
> '-Dsolr.log.level=INFO']
> {code}
> to main gradle. Taher mentionned that "The master build.gradle file should
> not point to any plugins"
> I put the same in both lucene and solr components build. gradle (Solrs relies
> on Lucene but our usage is specific) and saw no drawbacks.
> I must say I was not able to reproduce the "error" locally. But I anyway I
> propose to commit in the 2 plugins to reassur people who could else wonder.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OFBIZ-8316) Update Apache Solr/Lucene to release 6.2.1
[ https://issues.apache.org/jira/browse/OFBIZ-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070673#comment-16070673 ] Jacques Le Roux commented on OFBIZ-8316: BTW [~shi.jinghai] updating from 6.2.1 to 6.5.1 should have been a new issue with the commit referenced, thanks. > Update Apache Solr/Lucene to release 6.2.1 > -- > > Key: OFBIZ-8316 > URL: https://issues.apache.org/jira/browse/OFBIZ-8316 > Project: OFBiz > Issue Type: Improvement > Components: lucene, solr >Affects Versions: Trunk >Reporter: Michael Brohl >Assignee: Shi Jinghai >Priority: Minor > Fix For: Upcoming Release > > Attachments: OFBIZ-8316_corrected.patch, > ofbiz-truck-lucene-6.2.1.patch, ofbiz-truck-solr-6.2.1.patch, > solr6.2.1_1.patch > > > According to the announcements in > https://lists.apache.org/thread.html/5d2cb1ecbe04c6c40b8eeba3b7f8da586d1271af98c9b07ceee8ada2@%3Cannounce.apache.org%3E > and > https://lists.apache.org/thread.html/c1269b52229f6bce68399e813b7c6b79eb3f6283ae21bde11c82fc7c@%3Cannounce.apache.org%3E > there is a new Solr/Lucene release available. > This issue takes care of the update. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-7265) Could not obtain Lock on lucene index Lock
[ https://issues.apache.org/jira/browse/OFBIZ-7265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-7265. -- Resolution: Fixed Fix Version/s: (was: 16.11.02) (was: Release Branch 15.12) At r1794771 Jinghai committed for OFBIZ-8316 with this comment Updated Solr from 6.2.1 to 6.5.1...[snip]... But unfortunately he reintroduced the path for indexes to /runtime/indexes/products which breaks OFBIZ-7265 on this aspect where I then set it to runtime/indexes/solr to not confuse with Lucene index I have decide to make things even more clear by using now runtime/indexes/solr/products I hope nobody will break it again, even if it has no functional impact. Fixed at revision: 1800453 > Could not obtain Lock on lucene index Lock > -- > > Key: OFBIZ-7265 > URL: https://issues.apache.org/jira/browse/OFBIZ-7265 > Project: OFBiz > Issue Type: Bug > Components: lucene >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Release > > > I found this message in error.log > |xer_default_products |DocumentIndexer |E| Could not obtain > Lock on lucene index Lock held by this virtual machine: > C:\projectASF-Mars\ofbiz\runtime\indexes\products\write.lock > Here is Jacopo's answer: > bq. We should not worry (because the "lucene" component is just an > experimental one) but let's keep an eye on it: it is caused when two threads > are trying to update documents in the Lucene index; it may happen when two > events modify data that trigger the execution of the document update. We > could consider to enhance the DocumentIndexer to properly manage these > scenarios. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-8316) Update Apache Solr/Lucene to release 6.2.1
[ https://issues.apache.org/jira/browse/OFBIZ-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070662#comment-16070662 ] Jacques Le Roux commented on OFBIZ-8316: At r1794771 Jinghai committed with this comment bq. Updated Solr from 6.2.1 to 6.5.1 and the point fields generated by Lucene are ok now for Solr component. The 'original UI' link is commented in admin.html and the relative files under solr/webapp/solr/tpl are all removed. But unfortunately he reintroduced the path for indexes to /runtime/indexes/products which breaks OFBIZ-7265 on this aspect (I then set it to runtime/indexes/solr) > Update Apache Solr/Lucene to release 6.2.1 > -- > > Key: OFBIZ-8316 > URL: https://issues.apache.org/jira/browse/OFBIZ-8316 > Project: OFBiz > Issue Type: Improvement > Components: lucene, solr >Affects Versions: Trunk >Reporter: Michael Brohl >Assignee: Shi Jinghai >Priority: Minor > Fix For: Upcoming Release > > Attachments: OFBIZ-8316_corrected.patch, > ofbiz-truck-lucene-6.2.1.patch, ofbiz-truck-solr-6.2.1.patch, > solr6.2.1_1.patch > > > According to the announcements in > https://lists.apache.org/thread.html/5d2cb1ecbe04c6c40b8eeba3b7f8da586d1271af98c9b07ceee8ada2@%3Cannounce.apache.org%3E > and > https://lists.apache.org/thread.html/c1269b52229f6bce68399e813b7c6b79eb3f6283ae21bde11c82fc7c@%3Cannounce.apache.org%3E > there is a new Solr/Lucene release available. > This issue takes care of the update. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-7265) Could not obtain Lock on lucene index Lock
[ https://issues.apache.org/jira/browse/OFBIZ-7265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070661#comment-16070661 ] Michael Brohl commented on OFBIZ-7265: -- I had this error today also while testing. > Could not obtain Lock on lucene index Lock > -- > > Key: OFBIZ-7265 > URL: https://issues.apache.org/jira/browse/OFBIZ-7265 > Project: OFBiz > Issue Type: Bug > Components: lucene >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Release Branch 15.12, Upcoming Release, 16.11.02 > > > I found this message in error.log > |xer_default_products |DocumentIndexer |E| Could not obtain > Lock on lucene index Lock held by this virtual machine: > C:\projectASF-Mars\ofbiz\runtime\indexes\products\write.lock > Here is Jacopo's answer: > bq. We should not worry (because the "lucene" component is just an > experimental one) but let's keep an eye on it: it is caused when two threads > are trying to update documents in the Lucene index; it may happen when two > events modify data that trigger the execution of the document update. We > could consider to enhance the DocumentIndexer to properly manage these > scenarios. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (OFBIZ-7265) Could not obtain Lock on lucene index Lock
[ https://issues.apache.org/jira/browse/OFBIZ-7265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reopened OFBIZ-7265: The index directory name has been changed by OFBIZ-8316, setting it again > Could not obtain Lock on lucene index Lock > -- > > Key: OFBIZ-7265 > URL: https://issues.apache.org/jira/browse/OFBIZ-7265 > Project: OFBiz > Issue Type: Bug > Components: lucene >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Release Branch 15.12, Upcoming Release, 16.11.02 > > > I found this message in error.log > |xer_default_products |DocumentIndexer |E| Could not obtain > Lock on lucene index Lock held by this virtual machine: > C:\projectASF-Mars\ofbiz\runtime\indexes\products\write.lock > Here is Jacopo's answer: > bq. We should not worry (because the "lucene" component is just an > experimental one) but let's keep an eye on it: it is caused when two threads > are trying to update documents in the Lucene index; it may happen when two > events modify data that trigger the execution of the document update. We > could consider to enhance the DocumentIndexer to properly manage these > scenarios. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9443) Missing port.https configuration value breaks Solr
Michael Brohl created OFBIZ-9443: Summary: Missing port.https configuration value breaks Solr Key: OFBIZ-9443 URL: https://issues.apache.org/jira/browse/OFBIZ-9443 Project: OFBiz Issue Type: Bug Components: framework, solr Affects Versions: Trunk Reporter: Michael Brohl Following OFBIZ-9206 the port.https value was removed from the configuration. This breaks the Solr functionality because it reads the ports for http/https from this file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-6595) Have the ability to test solr queries through widgets (screens & forms)
[ https://issues.apache.org/jira/browse/OFBIZ-6595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl reassigned OFBIZ-6595: Assignee: Michael Brohl (was: Jacques Le Roux) > Have the ability to test solr queries through widgets (screens & forms) > --- > > Key: OFBIZ-6595 > URL: https://issues.apache.org/jira/browse/OFBIZ-6595 > Project: OFBiz > Issue Type: Sub-task > Components: solr >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Michael Brohl > Attachments: OFBIZ-6595-r1.patch > > > Adding widgest (screens, forms, etc) so that an end-user can execute a search > against the data indexed would enhance the applicability of the application. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-6595) Have the ability to test solr queries through widgets (screens & forms)
[ https://issues.apache.org/jira/browse/OFBIZ-6595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070142#comment-16070142 ] Jacques Le Roux commented on OFBIZ-6595: Not at all, please do Michael > Have the ability to test solr queries through widgets (screens & forms) > --- > > Key: OFBIZ-6595 > URL: https://issues.apache.org/jira/browse/OFBIZ-6595 > Project: OFBiz > Issue Type: Sub-task > Components: solr >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Jacques Le Roux > Attachments: OFBIZ-6595-r1.patch > > > Adding widgest (screens, forms, etc) so that an end-user can execute a search > against the data indexed would enhance the applicability of the application. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9442) Provide (more) tests for the Solr and Lucene components
Michael Brohl created OFBIZ-9442: Summary: Provide (more) tests for the Solr and Lucene components Key: OFBIZ-9442 URL: https://issues.apache.org/jira/browse/OFBIZ-9442 Project: OFBiz Issue Type: Sub-task Components: lucene, solr Affects Versions: Trunk Reporter: Michael Brohl Assignee: Michael Brohl The Lucene component has only one test, the Solr component has none. There should be some integration tests to test the creation of index entries and reading from the index. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-6595) Have the ability to test solr queries through widgets (screens & forms)
[ https://issues.apache.org/jira/browse/OFBIZ-6595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-6595: - Issue Type: Sub-task (was: Improvement) Parent: OFBIZ-9440 > Have the ability to test solr queries through widgets (screens & forms) > --- > > Key: OFBIZ-6595 > URL: https://issues.apache.org/jira/browse/OFBIZ-6595 > Project: OFBiz > Issue Type: Sub-task > Components: solr >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Jacques Le Roux > Attachments: OFBIZ-6595-r1.patch > > > Adding widgest (screens, forms, etc) so that an end-user can execute a search > against the data indexed would enhance the applicability of the application. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-6595) Have the ability to test solr queries through widgets (screens & forms)
[ https://issues.apache.org/jira/browse/OFBIZ-6595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070099#comment-16070099 ] Michael Brohl commented on OFBIZ-6595: -- [~jacques.le.roux], do you mind if I assign this issue to myself? > Have the ability to test solr queries through widgets (screens & forms) > --- > > Key: OFBIZ-6595 > URL: https://issues.apache.org/jira/browse/OFBIZ-6595 > Project: OFBiz > Issue Type: Improvement > Components: solr >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Jacques Le Roux > Attachments: OFBIZ-6595-r1.patch > > > Adding widgest (screens, forms, etc) so that an end-user can execute a search > against the data indexed would enhance the applicability of the application. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-6595) Have the ability to test solr queries through widgets (screens & forms)
[ https://issues.apache.org/jira/browse/OFBIZ-6595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070098#comment-16070098 ] Michael Brohl commented on OFBIZ-6595: -- I just stumbled upon this during my work on OFBIZ-9440. As Amardeep said, the functionality is incomplete. For the average user, the query widget pretends to provide a search functionality but there is nothing more than this widget (like Pierre rightly mentioned providing the patch). I see no reason why this work was committed in this state because it only causes confusion. We should definitely be more cautious when adding new functionality to the codebase. In a case like this, we should have waited until the work provides a minimum of functionality and ist tested accordingly. I will add this as a subtask to the refactoring issue and work out a minimal functional solution in the course of this work. > Have the ability to test solr queries through widgets (screens & forms) > --- > > Key: OFBIZ-6595 > URL: https://issues.apache.org/jira/browse/OFBIZ-6595 > Project: OFBiz > Issue Type: Improvement > Components: solr >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Jacques Le Roux > Attachments: OFBIZ-6595-r1.patch > > > Adding widgest (screens, forms, etc) so that an end-user can execute a search > against the data indexed would enhance the applicability of the application. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9439) Lucene tests fail due to problems in the test data
[
https://issues.apache.org/jira/browse/OFBIZ-9439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brohl closed OFBIZ-9439.
Resolution: Fixed
This is now fixed in r1800376. Lucene tests are passing now.
> Lucene tests fail due to problems in the test data
> --
>
> Key: OFBIZ-9439
> URL: https://issues.apache.org/jira/browse/OFBIZ-9439
> Project: OFBiz
> Issue Type: Sub-task
> Components: lucene
>Affects Versions: Trunk
>Reporter: Michael Brohl
>Assignee: Michael Brohl
> Fix For: Upcoming Release
>
>
> While working on OFBIZ-9391 the tests fail with the following errors:
> {code:java}
> 2017-06-29 18:58:29,700 |main |EntitySaxReader
> |I| Beginning import from URL:
> file:/Users/mbrohl/Projects/apache-ofbiz/trunk/ofbiz/plugins/lucene/testdef/data/LuceneTestsData.xml
> 2017-06-29 18:58:29,701 |main |EntitySaxReader
> |I| Transaction Timeout set to 2 hours (7200 seconds)
> 2017-06-29 18:58:29,739 |main |GenericDelegator
> |E| Failure in create operation for entity [Content]:
> org.apache.ofbiz.entity.GenericEntityException: Error while inserting:
> [GenericEntity:Content][contentId,CNTGIZMOSLRG(java.lang.String)][contentName,Large
>
> Gizmos(java.lang.String)][contentTypeId,WEB_SITE_PUB_PT(java.lang.String)][createdByUserLogin,admin(java.lang.String)][createdDate,2001-05-13
> 12:00:00.0(java.sql.Timestamp)][createdStamp,2017-06-29
> 18:58:29.729(java.sql.Timestamp)][createdTxStamp,2017-06-29
> 18:58:29.701(java.sql.Timestamp)][dataResourceId,CNTGIZMOSLRG(java.lang.String)][description,Large
> Widgets(java.lang.String)][lastUpdatedStamp,2017-06-29
> 18:58:29.729(java.sql.Timestamp)][lastUpdatedTxStamp,2017-06-29
> 18:58:29.701(java.sql.Timestamp)][localeString,en_US(java.lang.String)][mimeTypeId,text/html(java.lang.String)][ownerContentId,CNTGIZMOS(java.lang.String)]
> (SQL Exception while executing the following:INSERT INTO OFBIZ.CONTENT
> (CONTENT_ID, CONTENT_TYPE_ID, OWNER_CONTENT_ID, DECORATOR_CONTENT_ID,
> INSTANCE_OF_CONTENT_ID, DATA_RESOURCE_ID, TEMPLATE_DATA_RESOURCE_ID,
> DATA_SOURCE_ID, STATUS_ID, PRIVILEGE_ENUM_ID, SERVICE_NAME, CUSTOM_METHOD_ID,
> CONTENT_NAME, DESCRIPTION, LOCALE_STRING, MIME_TYPE_ID, CHARACTER_SET_ID,
> CHILD_LEAF_COUNT, CHILD_BRANCH_COUNT, CREATED_DATE, CREATED_BY_USER_LOGIN,
> LAST_MODIFIED_DATE, LAST_MODIFIED_BY_USER_LOGIN, LAST_UPDATED_STAMP,
> LAST_UPDATED_TX_STAMP, CREATED_STAMP, CREATED_TX_STAMP) VALUES (?, ?, ?, ?,
> ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (INSERT
> on table 'CONTENT' caused a violation of foreign key constraint
> 'CONTENT_PCNTNT' for key (CNTGIZMOS). The statement has been rolled back.)).
> Rolling back transaction.
> 2017-06-29 18:58:29,739 |main |TransactionUtil
> |W| Calling transaction setRollbackOnly; this stack trace shows where this is
> happening:
> java.lang.Exception: Failure in create operation for entity [Content]:
> org.apache.ofbiz.entity.GenericEntityException: Error while inserting:
> [GenericEntity:Content][contentId,CNTGIZMOSLRG(java.lang.String)][contentName,Large
>
> Gizmos(java.lang.String)][contentTypeId,WEB_SITE_PUB_PT(java.lang.String)][createdByUserLogin,admin(java.lang.String)][createdDate,2001-05-13
> 12:00:00.0(java.sql.Timestamp)][createdStamp,2017-06-29
> 18:58:29.729(java.sql.Timestamp)][createdTxStamp,2017-06-29
> 18:58:29.701(java.sql.Timestamp)][dataResourceId,CNTGIZMOSLRG(java.lang.String)][description,Large
> Widgets(java.lang.String)][lastUpdatedStamp,2017-06-29
> 18:58:29.729(java.sql.Timestamp)][lastUpdatedTxStamp,2017-06-29
> 18:58:29.701(java.sql.Timestamp)][localeString,en_US(java.lang.String)][mimeTypeId,text/html(java.lang.String)][ownerContentId,CNTGIZMOS(java.lang.String)]
> (SQL Exception while executing the following:INSERT INTO OFBIZ.CONTENT
> (CONTENT_ID, CONTENT_TYPE_ID, OWNER_CONTENT_ID, DECORATOR_CONTENT_ID,
> INSTANCE_OF_CONTENT_ID, DATA_RESOURCE_ID, TEMPLATE_DATA_RESOURCE_ID,
> DATA_SOURCE_ID, STATUS_ID, PRIVILEGE_ENUM_ID, SERVICE_NAME, CUSTOM_METHOD_ID,
> CONTENT_NAME, DESCRIPTION, LOCALE_STRING, MIME_TYPE_ID, CHARACTER_SET_ID,
> CHILD_LEAF_COUNT, CHILD_BRANCH_COUNT, CREATED_DATE, CREATED_BY_USER_LOGIN,
> LAST_MODIFIED_DATE, LAST_MODIFIED_BY_USER_LOGIN, LAST_UPDATED_STAMP,
> LAST_UPDATED_TX_STAMP, CREATED_STAMP, CREATED_TX_STAMP) VALUES (?, ?, ?, ?,
> ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (INSERT
> on table 'CONTENT' caused a violation of foreign key constraint
> 'CONTENT_PCNTNT' for key (CNTGIZMOS). The statement has been rolled back.)).
> Rolling back transaction.
> at
> org.apache.ofbiz.entity.transaction.TransactionUtil.setRollbackOnly(Tran
[jira] [Reopened] (OFBIZ-9439) Lucene tests fail due to problems in the test data
[
https://issues.apache.org/jira/browse/OFBIZ-9439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brohl reopened OFBIZ-9439:
--
The data is missing some content associations and the test code is not
reflecting the new data, will fix this.
> Lucene tests fail due to problems in the test data
> --
>
> Key: OFBIZ-9439
> URL: https://issues.apache.org/jira/browse/OFBIZ-9439
> Project: OFBiz
> Issue Type: Sub-task
> Components: lucene
>Affects Versions: Trunk
>Reporter: Michael Brohl
>Assignee: Michael Brohl
> Fix For: Upcoming Release
>
>
> While working on OFBIZ-9391 the tests fail with the following errors:
> {code:java}
> 2017-06-29 18:58:29,700 |main |EntitySaxReader
> |I| Beginning import from URL:
> file:/Users/mbrohl/Projects/apache-ofbiz/trunk/ofbiz/plugins/lucene/testdef/data/LuceneTestsData.xml
> 2017-06-29 18:58:29,701 |main |EntitySaxReader
> |I| Transaction Timeout set to 2 hours (7200 seconds)
> 2017-06-29 18:58:29,739 |main |GenericDelegator
> |E| Failure in create operation for entity [Content]:
> org.apache.ofbiz.entity.GenericEntityException: Error while inserting:
> [GenericEntity:Content][contentId,CNTGIZMOSLRG(java.lang.String)][contentName,Large
>
> Gizmos(java.lang.String)][contentTypeId,WEB_SITE_PUB_PT(java.lang.String)][createdByUserLogin,admin(java.lang.String)][createdDate,2001-05-13
> 12:00:00.0(java.sql.Timestamp)][createdStamp,2017-06-29
> 18:58:29.729(java.sql.Timestamp)][createdTxStamp,2017-06-29
> 18:58:29.701(java.sql.Timestamp)][dataResourceId,CNTGIZMOSLRG(java.lang.String)][description,Large
> Widgets(java.lang.String)][lastUpdatedStamp,2017-06-29
> 18:58:29.729(java.sql.Timestamp)][lastUpdatedTxStamp,2017-06-29
> 18:58:29.701(java.sql.Timestamp)][localeString,en_US(java.lang.String)][mimeTypeId,text/html(java.lang.String)][ownerContentId,CNTGIZMOS(java.lang.String)]
> (SQL Exception while executing the following:INSERT INTO OFBIZ.CONTENT
> (CONTENT_ID, CONTENT_TYPE_ID, OWNER_CONTENT_ID, DECORATOR_CONTENT_ID,
> INSTANCE_OF_CONTENT_ID, DATA_RESOURCE_ID, TEMPLATE_DATA_RESOURCE_ID,
> DATA_SOURCE_ID, STATUS_ID, PRIVILEGE_ENUM_ID, SERVICE_NAME, CUSTOM_METHOD_ID,
> CONTENT_NAME, DESCRIPTION, LOCALE_STRING, MIME_TYPE_ID, CHARACTER_SET_ID,
> CHILD_LEAF_COUNT, CHILD_BRANCH_COUNT, CREATED_DATE, CREATED_BY_USER_LOGIN,
> LAST_MODIFIED_DATE, LAST_MODIFIED_BY_USER_LOGIN, LAST_UPDATED_STAMP,
> LAST_UPDATED_TX_STAMP, CREATED_STAMP, CREATED_TX_STAMP) VALUES (?, ?, ?, ?,
> ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (INSERT
> on table 'CONTENT' caused a violation of foreign key constraint
> 'CONTENT_PCNTNT' for key (CNTGIZMOS). The statement has been rolled back.)).
> Rolling back transaction.
> 2017-06-29 18:58:29,739 |main |TransactionUtil
> |W| Calling transaction setRollbackOnly; this stack trace shows where this is
> happening:
> java.lang.Exception: Failure in create operation for entity [Content]:
> org.apache.ofbiz.entity.GenericEntityException: Error while inserting:
> [GenericEntity:Content][contentId,CNTGIZMOSLRG(java.lang.String)][contentName,Large
>
> Gizmos(java.lang.String)][contentTypeId,WEB_SITE_PUB_PT(java.lang.String)][createdByUserLogin,admin(java.lang.String)][createdDate,2001-05-13
> 12:00:00.0(java.sql.Timestamp)][createdStamp,2017-06-29
> 18:58:29.729(java.sql.Timestamp)][createdTxStamp,2017-06-29
> 18:58:29.701(java.sql.Timestamp)][dataResourceId,CNTGIZMOSLRG(java.lang.String)][description,Large
> Widgets(java.lang.String)][lastUpdatedStamp,2017-06-29
> 18:58:29.729(java.sql.Timestamp)][lastUpdatedTxStamp,2017-06-29
> 18:58:29.701(java.sql.Timestamp)][localeString,en_US(java.lang.String)][mimeTypeId,text/html(java.lang.String)][ownerContentId,CNTGIZMOS(java.lang.String)]
> (SQL Exception while executing the following:INSERT INTO OFBIZ.CONTENT
> (CONTENT_ID, CONTENT_TYPE_ID, OWNER_CONTENT_ID, DECORATOR_CONTENT_ID,
> INSTANCE_OF_CONTENT_ID, DATA_RESOURCE_ID, TEMPLATE_DATA_RESOURCE_ID,
> DATA_SOURCE_ID, STATUS_ID, PRIVILEGE_ENUM_ID, SERVICE_NAME, CUSTOM_METHOD_ID,
> CONTENT_NAME, DESCRIPTION, LOCALE_STRING, MIME_TYPE_ID, CHARACTER_SET_ID,
> CHILD_LEAF_COUNT, CHILD_BRANCH_COUNT, CREATED_DATE, CREATED_BY_USER_LOGIN,
> LAST_MODIFIED_DATE, LAST_MODIFIED_BY_USER_LOGIN, LAST_UPDATED_STAMP,
> LAST_UPDATED_TX_STAMP, CREATED_STAMP, CREATED_TX_STAMP) VALUES (?, ?, ?, ?,
> ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (INSERT
> on table 'CONTENT' caused a violation of foreign key constraint
> 'CONTENT_PCNTNT' for key (CNTGIZMOS). The statement has been rolled back.)).
> Rolling back transaction.
> at
> org.apache.ofbiz.entity.transaction.Tra
[jira] [Commented] (OFBIZ-9439) Lucene tests fail due to problems in the test data
[
https://issues.apache.org/jira/browse/OFBIZ-9439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16069868#comment-16069868
]
Jacques Le Roux commented on OFBIZ-9439:
bq. There might be cases where one plugin relies on another, but this should be
well thought and not happen by accident.
# Agreed
bq. Regarding data: plugins should only add and reference data to the existing
set in the base application, not to other plugins.
# Agreed, but I fear issues if 2 plugins have initially the same data and they
later differ in time (one replaces the other)
bq. We should then have an automatic mechanism to pull dependencies on other
plugins.
# Yes would be the right solution, we NEED something like that because of the
point 2
I'll soon answer you on the main issue (OFBIZ-9440)
> Lucene tests fail due to problems in the test data
> --
>
> Key: OFBIZ-9439
> URL: https://issues.apache.org/jira/browse/OFBIZ-9439
> Project: OFBiz
> Issue Type: Sub-task
> Components: lucene
>Affects Versions: Trunk
>Reporter: Michael Brohl
>Assignee: Michael Brohl
> Fix For: Upcoming Release
>
>
> While working on OFBIZ-9391 the tests fail with the following errors:
> {code:java}
> 2017-06-29 18:58:29,700 |main |EntitySaxReader
> |I| Beginning import from URL:
> file:/Users/mbrohl/Projects/apache-ofbiz/trunk/ofbiz/plugins/lucene/testdef/data/LuceneTestsData.xml
> 2017-06-29 18:58:29,701 |main |EntitySaxReader
> |I| Transaction Timeout set to 2 hours (7200 seconds)
> 2017-06-29 18:58:29,739 |main |GenericDelegator
> |E| Failure in create operation for entity [Content]:
> org.apache.ofbiz.entity.GenericEntityException: Error while inserting:
> [GenericEntity:Content][contentId,CNTGIZMOSLRG(java.lang.String)][contentName,Large
>
> Gizmos(java.lang.String)][contentTypeId,WEB_SITE_PUB_PT(java.lang.String)][createdByUserLogin,admin(java.lang.String)][createdDate,2001-05-13
> 12:00:00.0(java.sql.Timestamp)][createdStamp,2017-06-29
> 18:58:29.729(java.sql.Timestamp)][createdTxStamp,2017-06-29
> 18:58:29.701(java.sql.Timestamp)][dataResourceId,CNTGIZMOSLRG(java.lang.String)][description,Large
> Widgets(java.lang.String)][lastUpdatedStamp,2017-06-29
> 18:58:29.729(java.sql.Timestamp)][lastUpdatedTxStamp,2017-06-29
> 18:58:29.701(java.sql.Timestamp)][localeString,en_US(java.lang.String)][mimeTypeId,text/html(java.lang.String)][ownerContentId,CNTGIZMOS(java.lang.String)]
> (SQL Exception while executing the following:INSERT INTO OFBIZ.CONTENT
> (CONTENT_ID, CONTENT_TYPE_ID, OWNER_CONTENT_ID, DECORATOR_CONTENT_ID,
> INSTANCE_OF_CONTENT_ID, DATA_RESOURCE_ID, TEMPLATE_DATA_RESOURCE_ID,
> DATA_SOURCE_ID, STATUS_ID, PRIVILEGE_ENUM_ID, SERVICE_NAME, CUSTOM_METHOD_ID,
> CONTENT_NAME, DESCRIPTION, LOCALE_STRING, MIME_TYPE_ID, CHARACTER_SET_ID,
> CHILD_LEAF_COUNT, CHILD_BRANCH_COUNT, CREATED_DATE, CREATED_BY_USER_LOGIN,
> LAST_MODIFIED_DATE, LAST_MODIFIED_BY_USER_LOGIN, LAST_UPDATED_STAMP,
> LAST_UPDATED_TX_STAMP, CREATED_STAMP, CREATED_TX_STAMP) VALUES (?, ?, ?, ?,
> ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (INSERT
> on table 'CONTENT' caused a violation of foreign key constraint
> 'CONTENT_PCNTNT' for key (CNTGIZMOS). The statement has been rolled back.)).
> Rolling back transaction.
> 2017-06-29 18:58:29,739 |main |TransactionUtil
> |W| Calling transaction setRollbackOnly; this stack trace shows where this is
> happening:
> java.lang.Exception: Failure in create operation for entity [Content]:
> org.apache.ofbiz.entity.GenericEntityException: Error while inserting:
> [GenericEntity:Content][contentId,CNTGIZMOSLRG(java.lang.String)][contentName,Large
>
> Gizmos(java.lang.String)][contentTypeId,WEB_SITE_PUB_PT(java.lang.String)][createdByUserLogin,admin(java.lang.String)][createdDate,2001-05-13
> 12:00:00.0(java.sql.Timestamp)][createdStamp,2017-06-29
> 18:58:29.729(java.sql.Timestamp)][createdTxStamp,2017-06-29
> 18:58:29.701(java.sql.Timestamp)][dataResourceId,CNTGIZMOSLRG(java.lang.String)][description,Large
> Widgets(java.lang.String)][lastUpdatedStamp,2017-06-29
> 18:58:29.729(java.sql.Timestamp)][lastUpdatedTxStamp,2017-06-29
> 18:58:29.701(java.sql.Timestamp)][localeString,en_US(java.lang.String)][mimeTypeId,text/html(java.lang.String)][ownerContentId,CNTGIZMOS(java.lang.String)]
> (SQL Exception while executing the following:INSERT INTO OFBIZ.CONTENT
> (CONTENT_ID, CONTENT_TYPE_ID, OWNER_CONTENT_ID, DECORATOR_CONTENT_ID,
> INSTANCE_OF_CONTENT_ID, DATA_RESOURCE_ID, TEMPLATE_DATA_RESOURCE_ID,
> DATA_SOURCE_ID, STATUS_ID, PRIVILEGE_ENUM_ID, SERVICE_NAME, CUSTOM_METHOD_ID,
> CONTENT_NAME, DESCRIPTION, LOCALE_STRING, MIME_TYP
[jira] [Commented] (OFBIZ-9424) Typo in value of SfaAddSalesForecastDetail uiLabel in MarketingUiLabels.xml
[ https://issues.apache.org/jira/browse/OFBIZ-9424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16069864#comment-16069864 ] Aditya Sharma commented on OFBIZ-9424: -- Thanks, Jacques :) Indeed a typo doesn't require such a vivid description I don't know what was in my mind at that time I guess I gave those links to show where it will impact. > Typo in value of SfaAddSalesForecastDetail uiLabel in MarketingUiLabels.xml > --- > > Key: OFBIZ-9424 > URL: https://issues.apache.org/jira/browse/OFBIZ-9424 > Project: OFBiz > Issue Type: Bug > Components: marketing >Reporter: Aditya Sharma >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Release Branch 14.12, Release Branch 15.12, 16.11.04 > > > SfaAddSalesForecastDetail is used in EditSalesForecastDetail page. > Steps: > 1. Go to SFA component (https://demo-trunk.ofbiz.apache.org/sfa/control/main) > 2. Click on Forecast from > submenu.(https://demo-trunk.ofbiz.apache.org/sfa/control/FindSalesForecast) > 3. Create a new Sales Forecast by clicking on New Sales Forecast > (https://demo-trunk.ofbiz.apache.org/sfa/control/EditSalesForecast). > Or > Find an existing Sales Forecast & click on any ID > link.(https://demo-trunk.ofbiz.apache.org/sfa/control/EditSalesForecast?salesForecastId=1) > 4. Click on Detail subtab > (https://demo-trunk.ofbiz.apache.org/sfa/control/EditSalesForecastDetail?salesForecastId=1) > Title of the form will be Add Sales Forcast Detail For [salesForecastId] > It should be Forecast. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9435) Refactor Config.java and properties files
[ https://issues.apache.org/jira/browse/OFBIZ-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taher Alkhateeb closed OFBIZ-9435. -- Resolution: Fixed Fix Version/s: Upcoming Release Refactoring complete in r1800368. Closing issue > Refactor Config.java and properties files > - > > Key: OFBIZ-9435 > URL: https://issues.apache.org/jira/browse/OFBIZ-9435 > Project: OFBiz > Issue Type: Improvement >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb >Priority: Minor > Fix For: Upcoming Release > > Attachments: OFBIZ-9435.patch, OFBIZ-9435.patch > > > Apply further refactoring in the start component by reducing some complex > logic. Patch will be provided momentarily -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9441) Refactor OFBiz containers and remove StartupCommandToArgsAdapter
Taher Alkhateeb created OFBIZ-9441: -- Summary: Refactor OFBiz containers and remove StartupCommandToArgsAdapter Key: OFBIZ-9441 URL: https://issues.apache.org/jira/browse/OFBIZ-9441 Project: OFBiz Issue Type: Improvement Reporter: Taher Alkhateeb Assignee: Taher Alkhateeb Priority: Minor We have already refactored the ComponentContainer and CatalinaContainer in OFBIZ-8337 and OFBIZ-9392. The objective of this JIRA is to apply the following: - Refactor EntityDataLoadContainer to simplify the code and remove dependencies on "args" and convert instead the logic to use StartupCommands - Refactor TestRunContainer the same way - Delete the class StartupCommandToArgsAdapter -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9439) Lucene tests fail due to problems in the test data
[
https://issues.apache.org/jira/browse/OFBIZ-9439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16069725#comment-16069725
]
Michael Brohl commented on OFBIZ-9439:
--
Hi Jacques,
I think this would only cover the real problems. Plugins should be
self-contained and only rely on the base application. There should be no
cross-reference between other (non-related) plugins. There might be cases where
one plugin relies on another, but this should be well thought and not happen by
accident.
Regarding data: plugins should only add and reference data to the existing set
in the base application, not to other plugins.
We should then have an automatic mechanism to pull dependencies on other
plugins.
I was stumbling across several other issues in the Lucene and Solr components
last night, the code quality should be improved and will work on this further.
So -1 for the easy way out and +1 for sorting out the mess and making the
plugins real plugins.
> Lucene tests fail due to problems in the test data
> --
>
> Key: OFBIZ-9439
> URL: https://issues.apache.org/jira/browse/OFBIZ-9439
> Project: OFBiz
> Issue Type: Sub-task
> Components: lucene
>Affects Versions: Trunk
>Reporter: Michael Brohl
>Assignee: Michael Brohl
> Fix For: Upcoming Release
>
>
> While working on OFBIZ-9391 the tests fail with the following errors:
> {code:java}
> 2017-06-29 18:58:29,700 |main |EntitySaxReader
> |I| Beginning import from URL:
> file:/Users/mbrohl/Projects/apache-ofbiz/trunk/ofbiz/plugins/lucene/testdef/data/LuceneTestsData.xml
> 2017-06-29 18:58:29,701 |main |EntitySaxReader
> |I| Transaction Timeout set to 2 hours (7200 seconds)
> 2017-06-29 18:58:29,739 |main |GenericDelegator
> |E| Failure in create operation for entity [Content]:
> org.apache.ofbiz.entity.GenericEntityException: Error while inserting:
> [GenericEntity:Content][contentId,CNTGIZMOSLRG(java.lang.String)][contentName,Large
>
> Gizmos(java.lang.String)][contentTypeId,WEB_SITE_PUB_PT(java.lang.String)][createdByUserLogin,admin(java.lang.String)][createdDate,2001-05-13
> 12:00:00.0(java.sql.Timestamp)][createdStamp,2017-06-29
> 18:58:29.729(java.sql.Timestamp)][createdTxStamp,2017-06-29
> 18:58:29.701(java.sql.Timestamp)][dataResourceId,CNTGIZMOSLRG(java.lang.String)][description,Large
> Widgets(java.lang.String)][lastUpdatedStamp,2017-06-29
> 18:58:29.729(java.sql.Timestamp)][lastUpdatedTxStamp,2017-06-29
> 18:58:29.701(java.sql.Timestamp)][localeString,en_US(java.lang.String)][mimeTypeId,text/html(java.lang.String)][ownerContentId,CNTGIZMOS(java.lang.String)]
> (SQL Exception while executing the following:INSERT INTO OFBIZ.CONTENT
> (CONTENT_ID, CONTENT_TYPE_ID, OWNER_CONTENT_ID, DECORATOR_CONTENT_ID,
> INSTANCE_OF_CONTENT_ID, DATA_RESOURCE_ID, TEMPLATE_DATA_RESOURCE_ID,
> DATA_SOURCE_ID, STATUS_ID, PRIVILEGE_ENUM_ID, SERVICE_NAME, CUSTOM_METHOD_ID,
> CONTENT_NAME, DESCRIPTION, LOCALE_STRING, MIME_TYPE_ID, CHARACTER_SET_ID,
> CHILD_LEAF_COUNT, CHILD_BRANCH_COUNT, CREATED_DATE, CREATED_BY_USER_LOGIN,
> LAST_MODIFIED_DATE, LAST_MODIFIED_BY_USER_LOGIN, LAST_UPDATED_STAMP,
> LAST_UPDATED_TX_STAMP, CREATED_STAMP, CREATED_TX_STAMP) VALUES (?, ?, ?, ?,
> ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (INSERT
> on table 'CONTENT' caused a violation of foreign key constraint
> 'CONTENT_PCNTNT' for key (CNTGIZMOS). The statement has been rolled back.)).
> Rolling back transaction.
> 2017-06-29 18:58:29,739 |main |TransactionUtil
> |W| Calling transaction setRollbackOnly; this stack trace shows where this is
> happening:
> java.lang.Exception: Failure in create operation for entity [Content]:
> org.apache.ofbiz.entity.GenericEntityException: Error while inserting:
> [GenericEntity:Content][contentId,CNTGIZMOSLRG(java.lang.String)][contentName,Large
>
> Gizmos(java.lang.String)][contentTypeId,WEB_SITE_PUB_PT(java.lang.String)][createdByUserLogin,admin(java.lang.String)][createdDate,2001-05-13
> 12:00:00.0(java.sql.Timestamp)][createdStamp,2017-06-29
> 18:58:29.729(java.sql.Timestamp)][createdTxStamp,2017-06-29
> 18:58:29.701(java.sql.Timestamp)][dataResourceId,CNTGIZMOSLRG(java.lang.String)][description,Large
> Widgets(java.lang.String)][lastUpdatedStamp,2017-06-29
> 18:58:29.729(java.sql.Timestamp)][lastUpdatedTxStamp,2017-06-29
> 18:58:29.701(java.sql.Timestamp)][localeString,en_US(java.lang.String)][mimeTypeId,text/html(java.lang.String)][ownerContentId,CNTGIZMOS(java.lang.String)]
> (SQL Exception while executing the following:INSERT INTO OFBIZ.CONTENT
> (CONTENT_ID, CONTENT_TYPE_ID, OWNER_CONTENT_ID, DECORATOR_CONTENT_ID,
> INSTANCE_OF_CONTENT_ID, DA
[jira] [Commented] (OFBIZ-9439) Lucene tests fail due to problems in the test data
[
https://issues.apache.org/jira/browse/OFBIZ-9439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16069705#comment-16069705
]
Jacques Le Roux commented on OFBIZ-9439:
I Michael,
I think we will cross this type of issue again and again, I mean not only with
the lucene component (which was initially part of the content application cf.
r1518925).
So I wonder if we should not create a commonplugins component where we would
put all cases which end with duplicated data, model, etc. This component would
be always pulled if at least one of the OOTB plugins would be pulled and
automatically loaded before other plugins, like datamodel in application, here
also for common data. Is that worth a discussion?
> Lucene tests fail due to problems in the test data
> --
>
> Key: OFBIZ-9439
> URL: https://issues.apache.org/jira/browse/OFBIZ-9439
> Project: OFBiz
> Issue Type: Sub-task
> Components: lucene
>Affects Versions: Trunk
>Reporter: Michael Brohl
>Assignee: Michael Brohl
> Fix For: Upcoming Release
>
>
> While working on OFBIZ-9391 the tests fail with the following errors:
> {code:java}
> 2017-06-29 18:58:29,700 |main |EntitySaxReader
> |I| Beginning import from URL:
> file:/Users/mbrohl/Projects/apache-ofbiz/trunk/ofbiz/plugins/lucene/testdef/data/LuceneTestsData.xml
> 2017-06-29 18:58:29,701 |main |EntitySaxReader
> |I| Transaction Timeout set to 2 hours (7200 seconds)
> 2017-06-29 18:58:29,739 |main |GenericDelegator
> |E| Failure in create operation for entity [Content]:
> org.apache.ofbiz.entity.GenericEntityException: Error while inserting:
> [GenericEntity:Content][contentId,CNTGIZMOSLRG(java.lang.String)][contentName,Large
>
> Gizmos(java.lang.String)][contentTypeId,WEB_SITE_PUB_PT(java.lang.String)][createdByUserLogin,admin(java.lang.String)][createdDate,2001-05-13
> 12:00:00.0(java.sql.Timestamp)][createdStamp,2017-06-29
> 18:58:29.729(java.sql.Timestamp)][createdTxStamp,2017-06-29
> 18:58:29.701(java.sql.Timestamp)][dataResourceId,CNTGIZMOSLRG(java.lang.String)][description,Large
> Widgets(java.lang.String)][lastUpdatedStamp,2017-06-29
> 18:58:29.729(java.sql.Timestamp)][lastUpdatedTxStamp,2017-06-29
> 18:58:29.701(java.sql.Timestamp)][localeString,en_US(java.lang.String)][mimeTypeId,text/html(java.lang.String)][ownerContentId,CNTGIZMOS(java.lang.String)]
> (SQL Exception while executing the following:INSERT INTO OFBIZ.CONTENT
> (CONTENT_ID, CONTENT_TYPE_ID, OWNER_CONTENT_ID, DECORATOR_CONTENT_ID,
> INSTANCE_OF_CONTENT_ID, DATA_RESOURCE_ID, TEMPLATE_DATA_RESOURCE_ID,
> DATA_SOURCE_ID, STATUS_ID, PRIVILEGE_ENUM_ID, SERVICE_NAME, CUSTOM_METHOD_ID,
> CONTENT_NAME, DESCRIPTION, LOCALE_STRING, MIME_TYPE_ID, CHARACTER_SET_ID,
> CHILD_LEAF_COUNT, CHILD_BRANCH_COUNT, CREATED_DATE, CREATED_BY_USER_LOGIN,
> LAST_MODIFIED_DATE, LAST_MODIFIED_BY_USER_LOGIN, LAST_UPDATED_STAMP,
> LAST_UPDATED_TX_STAMP, CREATED_STAMP, CREATED_TX_STAMP) VALUES (?, ?, ?, ?,
> ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (INSERT
> on table 'CONTENT' caused a violation of foreign key constraint
> 'CONTENT_PCNTNT' for key (CNTGIZMOS). The statement has been rolled back.)).
> Rolling back transaction.
> 2017-06-29 18:58:29,739 |main |TransactionUtil
> |W| Calling transaction setRollbackOnly; this stack trace shows where this is
> happening:
> java.lang.Exception: Failure in create operation for entity [Content]:
> org.apache.ofbiz.entity.GenericEntityException: Error while inserting:
> [GenericEntity:Content][contentId,CNTGIZMOSLRG(java.lang.String)][contentName,Large
>
> Gizmos(java.lang.String)][contentTypeId,WEB_SITE_PUB_PT(java.lang.String)][createdByUserLogin,admin(java.lang.String)][createdDate,2001-05-13
> 12:00:00.0(java.sql.Timestamp)][createdStamp,2017-06-29
> 18:58:29.729(java.sql.Timestamp)][createdTxStamp,2017-06-29
> 18:58:29.701(java.sql.Timestamp)][dataResourceId,CNTGIZMOSLRG(java.lang.String)][description,Large
> Widgets(java.lang.String)][lastUpdatedStamp,2017-06-29
> 18:58:29.729(java.sql.Timestamp)][lastUpdatedTxStamp,2017-06-29
> 18:58:29.701(java.sql.Timestamp)][localeString,en_US(java.lang.String)][mimeTypeId,text/html(java.lang.String)][ownerContentId,CNTGIZMOS(java.lang.String)]
> (SQL Exception while executing the following:INSERT INTO OFBIZ.CONTENT
> (CONTENT_ID, CONTENT_TYPE_ID, OWNER_CONTENT_ID, DECORATOR_CONTENT_ID,
> INSTANCE_OF_CONTENT_ID, DATA_RESOURCE_ID, TEMPLATE_DATA_RESOURCE_ID,
> DATA_SOURCE_ID, STATUS_ID, PRIVILEGE_ENUM_ID, SERVICE_NAME, CUSTOM_METHOD_ID,
> CONTENT_NAME, DESCRIPTION, LOCALE_STRING, MIME_TYPE_ID, CHARACTER_SET_ID,
> CHILD_LEAF_COUNT, CHILD_BRANCH_COUNT, CREA
