[jira] [Updated] (ARIES-1780) Switch Zookeeper Discovery to DS

2018-04-26 Thread Christian Schneider (JIRA) 

 [ 
https://issues.apache.org/jira/browse/ARIES-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Schneider updated ARIES-1780:
---
Fix Version/s: (was: rsa-1.12.0)
   rsa-1.13.0

> Switch Zookeeper Discovery to DS
> 
>
> Key: ARIES-1780
> URL: https://issues.apache.org/jira/browse/ARIES-1780
> Project: Aries
>  Issue Type: Improvement
>  Components: Remote Service Admin
>Affects Versions: rsa-1.11.0
>Reporter: Christian Schneider
>Assignee: Christian Schneider
>Priority: Major
> Fix For: rsa-1.13.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ARIES-1675) Provide a module to run the tck tests

2018-04-26 Thread Christian Schneider (JIRA) 

 [ 
https://issues.apache.org/jira/browse/ARIES-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Schneider updated ARIES-1675:
---
Fix Version/s: (was: rsa-1.12.0)
   rsa-1.13.0

> Provide a module to run the tck tests
> -
>
> Key: ARIES-1675
> URL: https://issues.apache.org/jira/browse/ARIES-1675
> Project: Aries
>  Issue Type: Test
>  Components: Remote Service Admin
>Affects Versions: rsa-1.9.0
>Reporter: Christian Schneider
>Assignee: Christian Schneider
>Priority: Major
> Fix For: rsa-1.13.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ARIES-1778) Use endpoint id as path in zookeeper

2018-04-26 Thread Christian Schneider (JIRA) 

 [ 
https://issues.apache.org/jira/browse/ARIES-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Schneider resolved ARIES-1778.

Resolution: Fixed

> Use endpoint id as path in zookeeper
> 
>
> Key: ARIES-1778
> URL: https://issues.apache.org/jira/browse/ARIES-1778
> Project: Aries
>  Issue Type: Improvement
>  Components: Remote Service Admin
>Affects Versions: rsa-1.11.0
>Reporter: Christian Schneider
>Assignee: Christian Schneider
>Priority: Major
> Fix For: rsa-1.12.0
>
>
> Currently we use a quite complicated and not completely correct way to create 
> zookeeper nodes for endpoints.
> Below the base path we use the fully qualified interfacename and below the 
> endpoint id as path. 
> This creates several problems:
>  * To listen to changes we need to create nodes in zookeeper for every 
> interface that is requested as a service. So we end up with many nodes for 
> non remote services.
>  * As an endpoint may have more than one interface we then end up with more 
> than once endpoint for it in zookeeper. When the endpoint changes this 
> results in multiple change events created
> So I propose to change this to a much simpler scheme by simply using the 
> endpoint id as a path in zookeeper. This will make it much easier to listen 
> to changes and also will cause less nodes to be created in zookeeper.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1795) java.lang.IllegalStateException: The service registration is no longer valid.

2018-04-26 Thread Stefan Bischof (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARIES-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16454603#comment-16454603
 ] 

Stefan Bischof commented on ARIES-1795:
---

Hi,

sorry that was a bit short.
13    STPPD 201830241837  
reference:file:/builds/project-name/mvn-workspace/.m2/repository/org/apache/felix/org.apache.felix.http.jetty/3.4.8/org.apache.felix.http.jetty-3.4.8.jar

-ea, aQute.launcher.Launcher] executed with result=-9, 
I will send you more information when i get all dependencys to work again.  
org.apache.felix.framework 5.9.0-SNAPSHOT uses some pom-references which are 
not awaylible for me. (felix-parent 5-SNAPSHOT).

 

 

> java.lang.IllegalStateException: The service registration is no longer valid.
> -
>
> Key: ARIES-1795
> URL: https://issues.apache.org/jira/browse/ARIES-1795
> Project: Aries
>  Issue Type: Question
>  Components: jax-rs-whiteboard
>Affects Versions: jax-rs-whiteboard-1.0.0
>Reporter: Stefan Bischof
>Priority: Critical
> Attachments: log.txt, log2.txt
>
>
> Hi Carlos,
>  
> is this a Felix, an Aries-Whiteboard or (again) my Error?
> I only have this error on CI-Build using Gitlab-CI with maven-bnd-test-plugin.
>  
> {code:java}
> java.lang.IllegalStateException: The service registration is no longer valid.
>     at 
> org.apache.felix.framework.ServiceRegistrationImpl.getReference(ServiceRegistrationImpl.java:109)
>     at 
> org.apache.aries.jax.rs.whiteboard.internal.utils.Utils.updateProperty(Utils.java:188)
>     at 
> org.apache.aries.jax.rs.whiteboard.internal.Whiteboard.removeHttpEndpoints(Whiteboard.java:737)
>     at org.apache.aries.osgi.functional.OSGi.lambda$null$59(OSGi.java:537)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.ServiceReferenceOSGi$DefaultServiceTrackerCustomizer.removedService(ServiceReferenceOSGi.java:96)
>     at 
> org.apache.aries.osgi.functional.internal.ServiceReferenceOSGi$DefaultServiceTrackerCustomizer.removedService(ServiceReferenceOSGi.java:58)
>     at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:969)
>     at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:871)
>     at org.osgi.util.tracker.AbstractTracked.untrack(AbstractTracked.java:341)
>     at org.osgi.util.tracker.ServiceTracker.close(ServiceTracker.java:380)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at 
> org.apache.aries.osgi.functional.internal.AllOSGi.lambda$null$1(AllOSGi.java:51)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at org.apache.aries.osgi.functional.OSGi.lambda$null$59(OSGi.java:539)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.JustOSGiImpl.lambda$null$1(JustOSGiImpl.java:51)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.ServiceReferenceOSGi$DefaultServiceTrackerCustomizer.removedService(ServiceReferenceOSGi.java:96)
>     at 
> org.apache.aries.osgi.functional.internal.ServiceReferenceOSGi$DefaultServiceTrackerCustomizer.removedService(ServiceReferenceOSGi.java:58)
>     at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:969)
>     at 
>

Re: [VOTE] Release Aries JPA 2.7.0

2018-04-26 Thread Christian Schneider 
+1 (binding)

Christian


2018-04-26 12:48 GMT+02:00 Timothy Ward :

> As discussed in an earlier mail thread, Aries JPA will be the reference
> implementation for the JPA Service 1.1 from OSGi R7. This requires a
> release of the Aries JPA container, but the whole project has moved to Git
> and started using the OSGi contract namespace since its previous release.
> I’ve therefore staged a release candidate for the whole Aries JPA project.
> The module is staged and tagged in https://git-wip-us.apache.org/
> repos/asf?p=aries-jpa.git;a=tag;h=refs/tags/2.7.0.
>
> Instructions for verifying the release are at http://aries.apache.org/
> development/verifyingrelease.html. Alternately, cut and paste the
> following to run a full check:
>
> wget --no-check-certificate https://svn.apache.org/repos/
> asf/aries/scripts/verify_staged_release.sh
> chmod a+x verify_staged_release.sh
> ./verify_staged_release.sh 1125 mytempdirectory 2>&1 | tee
> verifyresults.txt
> grep FAIL verifyresults.txt
> grep ERROR verifyresults.txt
>
> Artifacts are in one staged repo, https://repository.apache.org/
> content/repositories/orgapachearies-1125/. The main source zip file for
> is available at https://repository.apache.org/content/repositories/
> orgapachearies-1125/org/apache/aries/jpa/org.apache.
> aries.jpa.main/2.7.0/org.apache.aries.jpa.main-2.7.0-source-release.zip.
>
> The RAT and IANAL build checks flag errors in the README.md and .gitignore
> files, but I could see no issues in actual sources or resources.
>
> The vote will be open for at least 72 hours, but as that takes us into a
> weekend I will leave it open until at least midday UTC on Monday 30th. [ ]
> +1 [ ] 0 [ ] -1
>
>


-- 
-- 
Christian Schneider
http://www.liquid-reality.de

Computer Scientist
http://www.adobe.com

Re: [VOTE] Release Aries JPA 2.7.0

2018-04-26 Thread Raymond Auge 
+1 (non-binding)

- Ray

On Thu, Apr 26, 2018 at 8:02 AM, Francois Papon <
francois.pa...@openobject.fr> wrote:

> +1 (non-binding)
>
> Thanks,
>
> François
>
>
> Le 26/04/2018 à 14:48, Timothy Ward a écrit :
> > As discussed in an earlier mail thread, Aries JPA will be the reference
> implementation for the JPA Service 1.1 from OSGi R7. This requires a
> release of the Aries JPA container, but the whole project has moved to Git
> and started using the OSGi contract namespace since its previous release.
> I’ve therefore staged a release candidate for the whole Aries JPA project.
> The module is staged and tagged in https://git-wip-us.apache.org/
> repos/asf?p=aries-jpa.git;a=tag;h=refs/tags/2.7.0.
> >
> > Instructions for verifying the release are at http://aries.apache.org/
> development/verifyingrelease.html. Alternately, cut and paste the
> following to run a full check:
> >
> > wget --no-check-certificate https://svn.apache.org/repos/
> asf/aries/scripts/verify_staged_release.sh
> > chmod a+x verify_staged_release.sh
> > ./verify_staged_release.sh 1125 mytempdirectory 2>&1 | tee
> verifyresults.txt
> > grep FAIL verifyresults.txt
> > grep ERROR verifyresults.txt
> >
> > Artifacts are in one staged repo, https://repository.apache.org/
> content/repositories/orgapachearies-1125/. The main source zip file for
> is available at https://repository.apache.org/content/repositories/
> orgapachearies-1125/org/apache/aries/jpa/org.apache.
> aries.jpa.main/2.7.0/org.apache.aries.jpa.main-2.7.0-source-release.zip.
> >
> > The RAT and IANAL build checks flag errors in the README.md and
> .gitignore files, but I could see no issues in actual sources or resources.
> >
> > The vote will be open for at least 72 hours, but as that takes us into a
> weekend I will leave it open until at least midday UTC on Monday 30th. [ ]
> +1 [ ] 0 [ ] -1
> >
>
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

Re: [VOTE] Release Aries JPA 2.7.0

2018-04-26 Thread Francois Papon 
+1 (non-binding)

Thanks,

François


Le 26/04/2018 à 14:48, Timothy Ward a écrit :
> As discussed in an earlier mail thread, Aries JPA will be the reference 
> implementation for the JPA Service 1.1 from OSGi R7. This requires a release 
> of the Aries JPA container, but the whole project has moved to Git and 
> started using the OSGi contract namespace since its previous release. I’ve 
> therefore staged a release candidate for the whole Aries JPA project. The 
> module is staged and tagged in 
> https://git-wip-us.apache.org/repos/asf?p=aries-jpa.git;a=tag;h=refs/tags/2.7.0.
>
> Instructions for verifying the release are at 
> http://aries.apache.org/development/verifyingrelease.html. Alternately, cut 
> and paste the following to run a full check:
>
> wget --no-check-certificate 
> https://svn.apache.org/repos/asf/aries/scripts/verify_staged_release.sh
> chmod a+x verify_staged_release.sh
> ./verify_staged_release.sh 1125 mytempdirectory 2>&1 | tee verifyresults.txt
> grep FAIL verifyresults.txt
> grep ERROR verifyresults.txt
>
> Artifacts are in one staged repo, 
> https://repository.apache.org/content/repositories/orgapachearies-1125/. The 
> main source zip file for is available at 
> https://repository.apache.org/content/repositories/orgapachearies-1125/org/apache/aries/jpa/org.apache.aries.jpa.main/2.7.0/org.apache.aries.jpa.main-2.7.0-source-release.zip.
>
> The RAT and IANAL build checks flag errors in the README.md and .gitignore 
> files, but I could see no issues in actual sources or resources.
>
> The vote will be open for at least 72 hours, but as that takes us into a 
> weekend I will leave it open until at least midday UTC on Monday 30th. [ ] +1 
> [ ] 0 [ ] -1
>

Re: [VOTE] Release Aries JPA 2.7.0

2018-04-26 Thread Jean-Baptiste Onofré 
+1 (binding)

Regards
JB

Le 26 avr. 2018 à 14:48, à 14:48, Timothy Ward  a 
écrit:
>As discussed in an earlier mail thread, Aries JPA will be the reference
>implementation for the JPA Service 1.1 from OSGi R7. This requires a
>release of the Aries JPA container, but the whole project has moved to
>Git and started using the OSGi contract namespace since its previous
>release. I’ve therefore staged a release candidate for the whole Aries
>JPA project. The module is staged and tagged in
>https://git-wip-us.apache.org/repos/asf?p=aries-jpa.git;a=tag;h=refs/tags/2.7.0.
>
>Instructions for verifying the release are at
>http://aries.apache.org/development/verifyingrelease.html. Alternately,
>cut and paste the following to run a full check:
>
>wget --no-check-certificate
>https://svn.apache.org/repos/asf/aries/scripts/verify_staged_release.sh
>chmod a+x verify_staged_release.sh
>./verify_staged_release.sh 1125 mytempdirectory 2>&1 | tee
>verifyresults.txt
>grep FAIL verifyresults.txt
>grep ERROR verifyresults.txt
>
>Artifacts are in one staged repo,
>https://repository.apache.org/content/repositories/orgapachearies-1125/.
>The main source zip file for is available at
>https://repository.apache.org/content/repositories/orgapachearies-1125/org/apache/aries/jpa/org.apache.aries.jpa.main/2.7.0/org.apache.aries.jpa.main-2.7.0-source-release.zip.
>
>The RAT and IANAL build checks flag errors in the README.md and
>.gitignore files, but I could see no issues in actual sources or
>resources.
>
>The vote will be open for at least 72 hours, but as that takes us into
>a weekend I will leave it open until at least midday UTC on Monday
>30th. [ ] +1 [ ] 0 [ ] -1

Re: [VOTE] Release Aries JPA 2.7.0

2018-04-26 Thread David Bosschaert 
+1

David

On 26 April 2018 at 11:48, Timothy Ward  wrote:

> As discussed in an earlier mail thread, Aries JPA will be the reference
> implementation for the JPA Service 1.1 from OSGi R7. This requires a
> release of the Aries JPA container, but the whole project has moved to Git
> and started using the OSGi contract namespace since its previous release.
> I’ve therefore staged a release candidate for the whole Aries JPA project.
> The module is staged and tagged in https://git-wip-us.apache.org/
> repos/asf?p=aries-jpa.git;a=tag;h=refs/tags/2.7.0.
>
> Instructions for verifying the release are at http://aries.apache.org/
> development/verifyingrelease.html. Alternately, cut and paste the
> following to run a full check:
>
> wget --no-check-certificate https://svn.apache.org/repos/
> asf/aries/scripts/verify_staged_release.sh
> chmod a+x verify_staged_release.sh
> ./verify_staged_release.sh 1125 mytempdirectory 2>&1 | tee
> verifyresults.txt
> grep FAIL verifyresults.txt
> grep ERROR verifyresults.txt
>
> Artifacts are in one staged repo, https://repository.apache.org/
> content/repositories/orgapachearies-1125/. The main source zip file for
> is available at https://repository.apache.org/content/repositories/
> orgapachearies-1125/org/apache/aries/jpa/org.apache.
> aries.jpa.main/2.7.0/org.apache.aries.jpa.main-2.7.0-source-release.zip.
>
> The RAT and IANAL build checks flag errors in the README.md and .gitignore
> files, but I could see no issues in actual sources or resources.
>
> The vote will be open for at least 72 hours, but as that takes us into a
> weekend I will leave it open until at least midday UTC on Monday 30th. [ ]
> +1 [ ] 0 [ ] -1
>
>

[VOTE] Release Aries JPA 2.7.0

2018-04-26 Thread Timothy Ward 
As discussed in an earlier mail thread, Aries JPA will be the reference 
implementation for the JPA Service 1.1 from OSGi R7. This requires a release of 
the Aries JPA container, but the whole project has moved to Git and started 
using the OSGi contract namespace since its previous release. I’ve therefore 
staged a release candidate for the whole Aries JPA project. The module is 
staged and tagged in 
https://git-wip-us.apache.org/repos/asf?p=aries-jpa.git;a=tag;h=refs/tags/2.7.0.

Instructions for verifying the release are at 
http://aries.apache.org/development/verifyingrelease.html. Alternately, cut and 
paste the following to run a full check:

wget --no-check-certificate 
https://svn.apache.org/repos/asf/aries/scripts/verify_staged_release.sh
chmod a+x verify_staged_release.sh
./verify_staged_release.sh 1125 mytempdirectory 2>&1 | tee verifyresults.txt
grep FAIL verifyresults.txt
grep ERROR verifyresults.txt

Artifacts are in one staged repo, 
https://repository.apache.org/content/repositories/orgapachearies-1125/. The 
main source zip file for is available at 
https://repository.apache.org/content/repositories/orgapachearies-1125/org/apache/aries/jpa/org.apache.aries.jpa.main/2.7.0/org.apache.aries.jpa.main-2.7.0-source-release.zip.

The RAT and IANAL build checks flag errors in the README.md and .gitignore 
files, but I could see no issues in actual sources or resources.

The vote will be open for at least 72 hours, but as that takes us into a 
weekend I will leave it open until at least midday UTC on Monday 30th. [ ] +1 [ 
] 0 [ ] -1

[jira] [Commented] (ARIES-1795) java.lang.IllegalStateException: The service registration is no longer valid.

2018-04-26 Thread Carlos Sierra (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARIES-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16453802#comment-16453802
 ] 

Carlos Sierra commented on ARIES-1795:
--

Hi Stefan,

how is it failing?

I could not find any error in the log... maybe I missed something.

Bests.

Carlos.

> java.lang.IllegalStateException: The service registration is no longer valid.
> -
>
> Key: ARIES-1795
> URL: https://issues.apache.org/jira/browse/ARIES-1795
> Project: Aries
>  Issue Type: Question
>  Components: jax-rs-whiteboard
>Affects Versions: jax-rs-whiteboard-1.0.0
>Reporter: Stefan Bischof
>Priority: Critical
> Attachments: log.txt, log2.txt
>
>
> Hi Carlos,
>  
> is this a Felix, an Aries-Whiteboard or (again) my Error?
> I only have this error on CI-Build using Gitlab-CI with maven-bnd-test-plugin.
>  
> {code:java}
> java.lang.IllegalStateException: The service registration is no longer valid.
>     at 
> org.apache.felix.framework.ServiceRegistrationImpl.getReference(ServiceRegistrationImpl.java:109)
>     at 
> org.apache.aries.jax.rs.whiteboard.internal.utils.Utils.updateProperty(Utils.java:188)
>     at 
> org.apache.aries.jax.rs.whiteboard.internal.Whiteboard.removeHttpEndpoints(Whiteboard.java:737)
>     at org.apache.aries.osgi.functional.OSGi.lambda$null$59(OSGi.java:537)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.ServiceReferenceOSGi$DefaultServiceTrackerCustomizer.removedService(ServiceReferenceOSGi.java:96)
>     at 
> org.apache.aries.osgi.functional.internal.ServiceReferenceOSGi$DefaultServiceTrackerCustomizer.removedService(ServiceReferenceOSGi.java:58)
>     at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:969)
>     at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:871)
>     at org.osgi.util.tracker.AbstractTracked.untrack(AbstractTracked.java:341)
>     at org.osgi.util.tracker.ServiceTracker.close(ServiceTracker.java:380)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at 
> org.apache.aries.osgi.functional.internal.AllOSGi.lambda$null$1(AllOSGi.java:51)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at org.apache.aries.osgi.functional.OSGi.lambda$null$59(OSGi.java:539)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.JustOSGiImpl.lambda$null$1(JustOSGiImpl.java:51)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.ServiceReferenceOSGi$DefaultServiceTrackerCustomizer.removedService(ServiceReferenceOSGi.java:96)
>     at 
> org.apache.aries.osgi.functional.internal.ServiceReferenceOSGi$DefaultServiceTrackerCustomizer.removedService(ServiceReferenceOSGi.java:58)
>     at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:969)
>     at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:871)
>     at org.osgi.util.tracker.AbstractTracked.untrack(AbstractTracked.java:341)
>     at 
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:911)
>     at 
> org.apache.felix.framework.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:990)
>     at 
>

[jira] [Comment Edited] (ARIES-1795) java.lang.IllegalStateException: The service registration is no longer valid.

2018-04-26 Thread Stefan Bischof (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARIES-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16453751#comment-16453751
 ] 

Stefan Bischof edited comment on ARIES-1795 at 4/26/18 9:32 AM:


Hi,

 

half the way ;)

can't see the whiteboard stacktrace any more, but failes!
{code:java}

Welcome to Apache Felix Gogo

g! gosh: stopping shell and framework
07:47:03.083 [main] DEBUG org.eclipse.jetty.util.component.ContainerLifeCycle - 
org.eclipse.jetty.server.session.SessionHandler@d5b810e added 
{org.eclipse.jetty.server.session.HashSessionManager@43dac38f,AUTO}
07:47:03.083 [main] DEBUG org.eclipse.jetty.util.component.ContainerLifeCycle - 
o.e.j.s.ServletContextHandler@7205765b{/,null,null} added 
{org.eclipse.jetty.server.session.SessionHandler@d5b810e,MANAGED}
07:47:03.085 [main] DEBUG org.eclipse.jetty.util.component.ContainerLifeCycle - 
org.eclipse.jetty.server.session.SessionHandler@d5b810e added 
{org.eclipse.jetty.servlet.ServletHandler@2ea41516,MANAGED}
07:47:03.086 [main] DEBUG org.eclipse.jetty.server.session - Sessions created 
by this manager are immortal (default maxInactiveInterval=0)
07:47:03.086 [main] DEBUG org.eclipse.jetty.util.component.ContainerLifeCycle - 
org.eclipse.jetty.server.session.HashSessionManager@43dac38f added 
{org.apache.felix.http.base.internal.EventDispatcher@194bcebf,UNMANAGED}
07:47:03.087 [main] DEBUG org.eclipse.jetty.util.component.ContainerLifeCycle - 
org.eclipse.jetty.servlet.ServletHandler@2ea41516 added 
{org.apache.felix.http.base.internal.dispatch.DispatcherServlet-550dbc7a@2e1baff0==org.apache.felix.http.base.internal.dispatch.DispatcherServlet,jsp=null,order=-1,inst=true,AUTO}
07:47:03.088 [main] DEBUG org.eclipse.jetty.util.component.ContainerLifeCycle - 
org.eclipse.jetty.servlet.ServletHandler@2ea41516 added 
{[/*]=>org.apache.felix.http.base.internal.dispatch.DispatcherServlet-550dbc7a,POJO}
07:47:03.088 [main] DEBUG org.eclipse.jetty.util.component.ContainerLifeCycle - 
org.eclipse.jetty.server.Server@3514a4c0 added 
{org.eclipse.jetty.server.handler.ContextHandlerCollection@35aea049[o.e.j.s.ServletContextHandler@7205765b{/,null,null}],MANAGED}
07:47:03.088 [main] DEBUG org.eclipse.jetty.util.component.AbstractLifeCycle - 
starting org.eclipse.jetty.server.Server@3514a4c0
07:47:03.089 [main] INFO org.eclipse.jetty.server.Server - 
jetty-9.3.22.v20171030
07:47:03.099 [main] DEBUG org.eclipse.jetty.server.handler.AbstractHandler - 
starting org.eclipse.jetty.server.Server@3514a4c0
07:47:03.100 [main] DEBUG org.eclipse.jetty.util.component.AbstractLifeCycle - 
starting qtp1427040229{STOPPED,8<=0<=200,i=0,q=0}
07:47:03.100 [main] DEBUG org.eclipse.jetty.util.component.AbstractLifeCycle - 
STARTED @531ms qtp1427040229{STARTED,8<=8<=200,i=8,q=0}
07:47:03.100 [main] DEBUG org.eclipse.jetty.util.component.AbstractLifeCycle - 
starting HashLoginService[OSGi HTTP Service Realm]
07:47:03.100 [main] DEBUG org.eclipse.jetty.security.HashLoginService - 
doStart: Starting new PropertyUserStore. PropertiesFile: null hotReload: false
07:47:03.102 [main] DEBUG org.eclipse.jetty.util.component.AbstractLifeCycle - 
starting 
org.eclipse.jetty.security.PropertyUserStore[users.count=0identityService=org.eclipse.jetty.security.DefaultIdentityService@5e600dd5]
07:47:03.102 [main] DEBUG org.eclipse.jetty.util.component.AbstractLifeCycle - 
STARTED @533ms 
org.eclipse.jetty.security.PropertyUserStore[users.count=0identityService=org.eclipse.jetty.security.DefaultIdentityService@5e600dd5]
07:47:03.102 [main] DEBUG org.eclipse.jetty.util.component.AbstractLifeCycle - 
STARTED @533ms HashLoginService[OSGi HTTP Service Realm]
07:47:03.102 [main] DEBUG org.eclipse.jetty.util.component.AbstractLifeCycle - 
starting 
org.eclipse.jetty.server.handler.ContextHandlerCollection@35aea049[o.e.j.s.ServletContextHandler@7205765b{/,null,null}]
07:47:03.102 [main] DEBUG 
org.eclipse.jetty.server.handler.ContextHandlerCollection - 
->[{o.e.j.s.ServletContextHandler@7205765b{/,null,null},[o.e.j.s.ServletContextHandler@7205765b{/,null,null}]}]
07:47:03.102 [main] DEBUG org.eclipse.jetty.server.handler.AbstractHandler - 
starting 
org.eclipse.jetty.server.handler.ContextHandlerCollection@35aea049[o.e.j.s.ServletContextHandler@7205765b{/,null,null}]
07:47:03.102 [main] DEBUG org.eclipse.jetty.util.component.AbstractLifeCycle - 
starting o.e.j.s.ServletContextHandler@7205765b{/,null,null}
07:47:03.104 [main] DEBUG org.eclipse.jetty.http.PreEncodedHttpField - 
HttpField encoders loaded: []
07:47:03.108 [main] DEBUG org.eclipse.jetty.server.handler.AbstractHandler - 
starting o.e.j.s.ServletContextHandler@7205765b{/,null,STARTING}
07:47:03.108 [main] DEBUG org.eclipse.jetty.util.component.AbstractLifeCycle - 
starting org.eclipse.jetty.server.session.SessionHandler@d5b810e
07:47:03.108 [main] DEBUG org.eclipse.jetty.server.handler.AbstractHandler - 
starting

[jira] [Updated] (ARIES-1795) java.lang.IllegalStateException: The service registration is no longer valid.

2018-04-26 Thread Stefan Bischof (JIRA) 

 [ 
https://issues.apache.org/jira/browse/ARIES-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Bischof updated ARIES-1795:
--
Attachment: log2.txt

> java.lang.IllegalStateException: The service registration is no longer valid.
> -
>
> Key: ARIES-1795
> URL: https://issues.apache.org/jira/browse/ARIES-1795
> Project: Aries
>  Issue Type: Question
>  Components: jax-rs-whiteboard
>Affects Versions: jax-rs-whiteboard-1.0.0
>Reporter: Stefan Bischof
>Priority: Critical
> Attachments: log.txt, log2.txt
>
>
> Hi Carlos,
>  
> is this a Felix, an Aries-Whiteboard or (again) my Error?
> I only have this error on CI-Build using Gitlab-CI with maven-bnd-test-plugin.
>  
> {code:java}
> java.lang.IllegalStateException: The service registration is no longer valid.
>     at 
> org.apache.felix.framework.ServiceRegistrationImpl.getReference(ServiceRegistrationImpl.java:109)
>     at 
> org.apache.aries.jax.rs.whiteboard.internal.utils.Utils.updateProperty(Utils.java:188)
>     at 
> org.apache.aries.jax.rs.whiteboard.internal.Whiteboard.removeHttpEndpoints(Whiteboard.java:737)
>     at org.apache.aries.osgi.functional.OSGi.lambda$null$59(OSGi.java:537)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.ServiceReferenceOSGi$DefaultServiceTrackerCustomizer.removedService(ServiceReferenceOSGi.java:96)
>     at 
> org.apache.aries.osgi.functional.internal.ServiceReferenceOSGi$DefaultServiceTrackerCustomizer.removedService(ServiceReferenceOSGi.java:58)
>     at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:969)
>     at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:871)
>     at org.osgi.util.tracker.AbstractTracked.untrack(AbstractTracked.java:341)
>     at org.osgi.util.tracker.ServiceTracker.close(ServiceTracker.java:380)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at 
> org.apache.aries.osgi.functional.internal.AllOSGi.lambda$null$1(AllOSGi.java:51)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at org.apache.aries.osgi.functional.OSGi.lambda$null$59(OSGi.java:539)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.JustOSGiImpl.lambda$null$1(JustOSGiImpl.java:51)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.OSGiResultImpl.close(OSGiResultImpl.java:36)
>     at org.apache.aries.osgi.functional.OSGiResult.run(OSGiResult.java:29)
>     at 
> org.apache.aries.osgi.functional.internal.ServiceReferenceOSGi$DefaultServiceTrackerCustomizer.removedService(ServiceReferenceOSGi.java:96)
>     at 
> org.apache.aries.osgi.functional.internal.ServiceReferenceOSGi$DefaultServiceTrackerCustomizer.removedService(ServiceReferenceOSGi.java:58)
>     at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:969)
>     at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:871)
>     at org.osgi.util.tracker.AbstractTracked.untrack(AbstractTracked.java:341)
>     at 
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:911)
>     at 
> org.apache.felix.framework.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:990)
>     at 
> org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:838)
>     at 
>

[jira] [Comment Edited] (ARIES-1795) java.lang.IllegalStateException: The service registration is no longer valid.

2018-04-26 Thread Stefan Bischof (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARIES-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16453751#comment-16453751
 ] 

Stefan Bischof edited comment on ARIES-1795 at 4/26/18 9:33 AM:


Hi,

 

half the way ;)

can't see the whiteboard stacktrace any more, but failes!

[^log2.txt]
{code:java}

Welcome to Apache Felix Gogo

g! gosh: stopping shell and framework
07:47:03.083 [main] DEBUG org.eclipse.jetty.util.component.ContainerLifeCycle - 
org.eclipse.jetty.server.session.SessionHandler@d5b810e added 
{org.eclipse.jetty.server.session.HashSessionManager@43dac38f,AUTO}
07:47:03.083 [main] DEBUG org.eclipse.jetty.util.component.ContainerLifeCycle - 
o.e.j.s.ServletContextHandler@7205765b{/,null,null} added 
{org.eclipse.jetty.server.session.SessionHandler@d5b810e,MANAGED}
07:47:03.085 [main] DEBUG org.eclipse.jetty.util.component.ContainerLifeCycle - 
org.eclipse.jetty.server.session.SessionHandler@d5b810e added 
{org.eclipse.jetty.servlet.ServletHandler@2ea41516,MANAGED}
07:47:03.086 [main] DEBUG org.eclipse.jetty.server.session - Sessions created 
by this manager are immortal (default maxInactiveInterval=0)
07:47:03.086 [main] DEBUG org.eclipse.jetty.util.component.ContainerLifeCycle - 
org.eclipse.jetty.server.session.HashSessionManager@43dac38f added 
{org.apache.felix.http.base.internal.EventDispatcher@194bcebf,UNMANAGED}
07:47:03.087 [main] DEBUG org.eclipse.jetty.util.component.ContainerLifeCycle - 
org.eclipse.jetty.servlet.ServletHandler@2ea41516 added 
{org.apache.felix.http.base.internal.dispatch.DispatcherServlet-550dbc7a@2e1baff0==org.apache.felix.http.base.internal.dispatch.DispatcherServlet,jsp=null,order=-1,inst=true,AUTO}
07:47:03.088 [main] DEBUG org.eclipse.jetty.util.component.ContainerLifeCycle - 
org.eclipse.jetty.servlet.ServletHandler@2ea41516 added 
{[/*]=>org.apache.felix.http.base.internal.dispatch.DispatcherServlet-550dbc7a,POJO}
07:47:03.088 [main] DEBUG org.eclipse.jetty.util.component.ContainerLifeCycle - 
org.eclipse.jetty.server.Server@3514a4c0 added 
{org.eclipse.jetty.server.handler.ContextHandlerCollection@35aea049[o.e.j.s.ServletContextHandler@7205765b{/,null,null}],MANAGED}
07:47:03.088 [main] DEBUG org.eclipse.jetty.util.component.AbstractLifeCycle - 
starting org.eclipse.jetty.server.Server@3514a4c0
07:47:03.089 [main] INFO org.eclipse.jetty.server.Server - 
jetty-9.3.22.v20171030
07:47:03.099 [main] DEBUG org.eclipse.jetty.server.handler.AbstractHandler - 
starting org.eclipse.jetty.server.Server@3514a4c0
07:47:03.100 [main] DEBUG org.eclipse.jetty.util.component.AbstractLifeCycle - 
starting qtp1427040229{STOPPED,8<=0<=200,i=0,q=0}
07:47:03.100 [main] DEBUG org.eclipse.jetty.util.component.AbstractLifeCycle - 
STARTED @531ms qtp1427040229{STARTED,8<=8<=200,i=8,q=0}
07:47:03.100 [main] DEBUG org.eclipse.jetty.util.component.AbstractLifeCycle - 
starting HashLoginService[OSGi HTTP Service Realm]
07:47:03.100 [main] DEBUG org.eclipse.jetty.security.HashLoginService - 
doStart: Starting new PropertyUserStore. PropertiesFile: null hotReload: false
07:47:03.102 [main] DEBUG org.eclipse.jetty.util.component.AbstractLifeCycle - 
starting 
org.eclipse.jetty.security.PropertyUserStore[users.count=0identityService=org.eclipse.jetty.security.DefaultIdentityService@5e600dd5]
07:47:03.102 [main] DEBUG org.eclipse.jetty.util.component.AbstractLifeCycle - 
STARTED @533ms 
org.eclipse.jetty.security.PropertyUserStore[users.count=0identityService=org.eclipse.jetty.security.DefaultIdentityService@5e600dd5]
07:47:03.102 [main] DEBUG org.eclipse.jetty.util.component.AbstractLifeCycle - 
STARTED @533ms HashLoginService[OSGi HTTP Service Realm]
07:47:03.102 [main] DEBUG org.eclipse.jetty.util.component.AbstractLifeCycle - 
starting 
org.eclipse.jetty.server.handler.ContextHandlerCollection@35aea049[o.e.j.s.ServletContextHandler@7205765b{/,null,null}]
07:47:03.102 [main] DEBUG 
org.eclipse.jetty.server.handler.ContextHandlerCollection - 
->[{o.e.j.s.ServletContextHandler@7205765b{/,null,null},[o.e.j.s.ServletContextHandler@7205765b{/,null,null}]}]
07:47:03.102 [main] DEBUG org.eclipse.jetty.server.handler.AbstractHandler - 
starting 
org.eclipse.jetty.server.handler.ContextHandlerCollection@35aea049[o.e.j.s.ServletContextHandler@7205765b{/,null,null}]
07:47:03.102 [main] DEBUG org.eclipse.jetty.util.component.AbstractLifeCycle - 
starting o.e.j.s.ServletContextHandler@7205765b{/,null,null}
07:47:03.104 [main] DEBUG org.eclipse.jetty.http.PreEncodedHttpField - 
HttpField encoders loaded: []
07:47:03.108 [main] DEBUG org.eclipse.jetty.server.handler.AbstractHandler - 
starting o.e.j.s.ServletContextHandler@7205765b{/,null,STARTING}
07:47:03.108 [main] DEBUG org.eclipse.jetty.util.component.AbstractLifeCycle - 
starting org.eclipse.jetty.server.session.SessionHandler@d5b810e
07:47:03.108 [main] DEBUG org.eclipse.jetty.server.handler.AbstractHandler - 
starting

Re: OSGi R7 releases

2018-04-26 Thread Carlos Sierra Andrés 
thanks Tim...

yes... not challenging at all :-)


El 25/4/18 a las 12:30, Timothy Ward escribió:
> This page helps a lot http://aries.apache.org/development/releasingaries.html!
>
> The first thing to do is to get your GPG signing key generated and added to 
> the Aries release keys. While that’s happening you can run the rat checks and 
> fix up any legal issues (basically just missing licence headers). When both 
> of those things are done you can prepare and stage the release. Then do the 
> vote, then promote the release.
>
> Not too challenging really :)
>
> Tim
>
> On 25 Apr 2018, at 11:05, Carlos Sierra Andrés 
> > wrote:
>
>
> Hi...
>
> I will take on the release of Aries JAX-RS Whiteboard. I can use all the help 
> I can get since I haven't done this before.
>
> Cheers.
>
> Carlos.
>
> El 25/4/18 a las 10:08, Timothy Ward escribió:
>
> Hi all,
>
> The OSGi R7 specifications and API jars are now official.  I know of at least 
> four Aries components that are due to be reference implementations for these 
> specifications - Aries JPA, Aries Tx Control, Aries RSA and Aries JAX-RS 
> whiteboard.
>
> There are only about six weeks now until released versions of these Reference 
> Implementations need to be available, thankfully they’re all passing the 
> relevant CT suites already. There are dependency chains between some of the 
> reference implementations so I’m proposing to start the release processes now 
> rather than having to do things in a mad panic next month.
>
> I’m happy to drive the Aries JPA and Aries Tx Control releases. I imagine 
> that Christian Schneider and Carlos Sierra will want to take on the releases 
> for Aries RSA.
>
> If anyone knows of any showstopper problems then now would be a good time to 
> speak up!
>
> Best Regards,
>
> Tim
>
> --
> Carlos Sierra
> Core Engineer
> Liferay España y Portugal / Liferay Spain and Portugal
> Tel. +34 917336343
> www.liferay.com
>
> 
> Enterprise. Open Source. For Life.
>
> Visit Us: www.liferay.com  |  Like Us: 
> facebook.com/liferay  |  Follow Us: 
> twitter.com/liferay_es
>
> AVISO DE CONFIDENCIALIDAD: “La información contenida en este mensaje y/o 
> archivo(s) adjunto(s), enviada desde LIFERAY SL, es confidencial/privilegiada 
> y está destinada a ser leída sólo por la(s) persona(s) a la(s) que va 
> dirigida. Le recordamos que sus datos han sido incorporados en un fichero y 
> que siempre y cuando se cumplan los requisitos exigidos por la normativa, 
> podrá ejercer los derechos de acceso, rectificación, cancelación y oposición, 
> ante nuestra entidad.
> Si usted lee este mensaje y no es el destinatario señalado, el empleado o el 
> agente responsable de entregar el mensaje al destinatario, o ha recibido esta 
> comunicación por error, le informamos que está totalmente prohibida, y puede 
> ser ilegal, cualquier divulgación, distribución o reproducción de esta 
> comunicación, y le rogamos que nos lo notifique inmediatamente y nos devuelva 
> el mensaje original a la dirección arriba mencionada. Gracias.”
> "The information contained in this message and any attached file(s) sent by 
> Liferay SL is confidential / privileged and intended solely for the 
> addressee(s). If you are not the intended recipient, any form of disclosure, 
> reproduction, distribution or any action taken or refrained from in reliance 
> on it, is prohibited and may be unlawful. Please notify the sender 
> immediately and destroy this e-mail. Thank you."
>

-- 
Carlos Sierra
Core Engineer
Liferay España y Portugal / Liferay Spain and Portugal
Tel. +34 917336343
www.liferay.com 


Enterprise. Open Source. For Life.

Visit Us: www.liferay.com   |  Like
Us: facebook.com/liferay   |  Follow
Us: twitter.com/liferay_es 

*AVISO DE CONFIDENCIALIDAD: */“La información contenida en este mensaje
y/o archivo(s) adjunto(s), enviada desde LIFERAY SL, es
confidencial/privilegiada y está destinada a ser leída sólo por la(s)
persona(s) a la(s) que va dirigida. Le recordamos que sus datos han sido
incorporados en un fichero y que siempre y cuando se cumplan los
requisitos exigidos por la normativa, podrá ejercer los derechos de
acceso, rectificación, cancelación y oposición, ante nuestra entidad./

/Si usted lee este mensaje y no es el destinatario señalado, el empleado
o el agente responsable de entregar el mensaje al destinatario, o ha
recibido esta comunicación por error, le informamos que está totalmente
prohibida, y puede ser ilegal, cualquier divulgación, distribución o
reproducción de esta comunicación, y le rogamos que nos lo notifique
inmediatamente y nos devuelva el mensaje original a la dirección arriba
mencionada. //Gracias.”/* *

/"The information contained in this message and any attached