Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 64C83200CD5 for ; Sun, 16 Jul 2017 03:44:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 635561649DD; Sun, 16 Jul 2017 01:44:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (unknown [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 81DCC1649DC for ; Sun, 16 Jul 2017 03:44:05 +0200 (CEST) Received: (qmail 28816 invoked by uid 500); 16 Jul 2017 01:44:04 -0000 Mailing-List: contact dev-help@polygene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@polygene.apache.org Delivered-To: mailing list dev@polygene.apache.org Received: (qmail 28805 invoked by uid 99); 16 Jul 2017 01:44:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 16 Jul 2017 01:44:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 47FB5C140A for ; Sun, 16 Jul 2017 01:44:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 2ac1MGG44_tk for ; Sun, 16 Jul 2017 01:44:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 2865E5FBEA for ; Sun, 16 Jul 2017 01:44:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 51335E0051 for ; Sun, 16 Jul 2017 01:44:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 091F024736 for ; Sun, 16 Jul 2017 01:44:00 +0000 (UTC) Date: Sun, 16 Jul 2017 01:44:00 +0000 (UTC) From: "Niclas Hedhman (JIRA)" To: dev@polygene.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (POLYGENE-269) indexing-sql seems to be broken MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 16 Jul 2017 01:44:06 -0000 Niclas Hedhman created POLYGENE-269: --------------------------------------- Summary: indexing-sql seems to be broken Key: POLYGENE-269 URL: https://issues.apache.org/jira/browse/POLYGENE-269 Project: Polygene Issue Type: Bug Affects Versions: 3.0.0 Reporter: Niclas Hedhman When starting indexing-sql the first time it works. Maybe even the second time, not sure... But eventually the following exception is preventing starts. {code} Exception in thread "main" org.apache.polygene.api.activation.ActivationException: Unable to Activate application. at org.apache.polygene.runtime.activation.ActivationDelegate.activate(ActivationDelegate.java:160) at org.apache.polygene.runtime.activation.ActivationDelegate.activate(ActivationDelegate.java:89) at org.apache.polygene.runtime.service.ServicesInstance.activate(ServicesInstance.java:69) at org.apache.polygene.runtime.activation.ActivationDelegate.activate(ActivationDelegate.java:120) at org.apache.polygene.runtime.activation.ActivationDelegate.activate(ActivationDelegate.java:89) at org.apache.polygene.runtime.structure.ModuleInstance.activate(ModuleInstance.java:432) at org.apache.polygene.runtime.activation.ActivationDelegate.activate(ActivationDelegate.java:120) at org.apache.polygene.runtime.activation.ActivationDelegate.activate(ActivationDelegate.java:89) at org.apache.polygene.runtime.structure.LayerInstance.activate(LayerInstance.java:93) at org.apache.polygene.runtime.activation.ActivationDelegate.activate(ActivationDelegate.java:120) at org.apache.polygene.runtime.activation.ActivationDelegate.activate(ActivationDelegate.java:89) at org.apache.polygene.runtime.structure.ApplicationInstance.activate(ApplicationInstance.java:140) at org.apache.polygene.library.restlet.PolygeneRestApplicationLauncher.activateApplication(PolygeneRestApplicationLauncher.java:65) at org.apache.polygene.library.restlet.PolygeneRestApplicationLauncher.initialize(PolygeneRestApplicationLauncher.java:49) at com.sensetif.sink.app.SinkLauncher.main(SinkLauncher.java:23) Caused by: org.apache.polygene.api.service.ServiceUnavailableException: Could not activate service SecureJettyService at org.apache.polygene.runtime.service.ServiceReferenceInstance.getInstance(ServiceReferenceInstance.java:172) at org.apache.polygene.runtime.service.ServiceReferenceInstance.activate(ServiceReferenceInstance.java:124) at org.apache.polygene.runtime.activation.ActivationDelegate.activate(ActivationDelegate.java:120) ... 14 more Caused by: org.apache.polygene.api.activation.ActivationException: Unable to Activate application. at org.apache.polygene.runtime.activation.ActivationDelegate.activate(ActivationDelegate.java:160) at org.apache.polygene.runtime.activation.ActivationDelegate.activate(ActivationDelegate.java:83) at org.apache.polygene.runtime.service.ServiceReferenceInstance.getInstance(ServiceReferenceInstance.java:166) ... 16 more Caused by: java.lang.IllegalStateException: java.lang.InstantiationException: Could not instantiate configuration, and no configuration initialization file was found (SecureJettyService) at method "get" of SecureJettyService:SecureJettyService in module [HttpServer Module] of layer [Connectivity Layer].(:0) at org.apache.polygene.api.configuration.Configuration$ConfigurationMixin.get(Configuration.java:206) at org.apache.polygene.library.http.SecureJettyMixin.configuration(SecureJettyMixin.java:69) at org.apache.polygene.library.http.AbstractJettyMixin.startJetty(AbstractJettyMixin.java:87) at org.apache.polygene.library.http.JettyActivation$Activator.afterActivation(JettyActivation.java:43) at org.apache.polygene.library.http.JettyActivation$Activator.afterActivation(JettyActivation.java:35) ... 3 more Caused by: java.lang.InstantiationException: Could not instantiate configuration, and no configuration initialization file was found (SecureJettyService) at org.apache.polygene.api.configuration.Configuration$ConfigurationMixin.initializeConfigurationInstance(Configuration.java:319) at org.apache.polygene.api.configuration.Configuration$ConfigurationMixin.findConfigurationInstanceFor(Configuration.java:262) at org.apache.polygene.api.configuration.Configuration$ConfigurationMixin.get(Configuration.java:202) ... 7 more Caused by: org.apache.polygene.api.unitofwork.UnitOfWorkException: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "indexing_entities_entity_identity_key" Detail: Key (entity_identity)=(SecureJettyService) already exists. at method "notifyChanges" of PostgreSQLService:indexing-sql in module [SQLIndexing Module] of layer [Infrastructure Layer].(:0) at org.apache.polygene.index.sql.internal.SQLStateChangeListener.notifyChanges(SQLStateChangeListener.java:46) at org.apache.polygene.spi.entitystore.StateChangeNotificationConcern$1.commit(StateChangeNotificationConcern.java:50) at org.apache.polygene.spi.entitystore.ConcurrentModificationCheckConcern$ConcurrentCheckingEntityStoreUnitOfWork$1.commit(ConcurrentModificationCheckConcern.java:123) at java.util.ArrayList.forEach(ArrayList.java:1249) at org.apache.polygene.api.configuration.Configuration$ConfigurationMixin.initializeConfigurationInstance(Configuration.java:312) ... 9 more Caused by: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "indexing_entities_entity_identity_key" Detail: Key (entity_identity)=(SecureJettyService) already exists. at method "indexEntities" of PostgreSQLService:indexing-sql in module [SQLIndexing Module] of layer [Infrastructure Layer].(:0) at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2412) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2125) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:297) at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:428) at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:354) at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:169) at org.postgresql.jdbc.PgPreparedStatement.executeQuery(PgPreparedStatement.java:117) at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:83) at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:83) at org.apache.polygene.index.sql.support.postgresql.PostgreSQLIndexing.getPKFromAutoGeneratedIDInsert(PostgreSQLIndexing.java:51) at org.apache.polygene.index.sql.support.skeletons.AbstractSQLIndexing.indexEntities(AbstractSQLIndexing.java:226) at org.apache.polygene.index.sql.internal.SQLStateChangeListener.notifyChanges(SQLStateChangeListener.java:41) ... 13 more {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)