[JBoss JIRA] (ISPN-4862) Race condition in InfinispanResourceDescriptionResolver's usage of resource static fields
by Tristan Tarrant (JIRA)
Tristan Tarrant created ISPN-4862:
-------------------------------------
Summary: Race condition in InfinispanResourceDescriptionResolver's usage of resource static fields
Key: ISPN-4862
URL: https://issues.jboss.org/browse/ISPN-4862
Project: Infinispan
Issue Type: Bug
Components: Server
Affects Versions: 7.0.0.CR1
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 7.0.0.Final
InfinispanResourceDescriptionResolver has a static initializer which fills a hashmap with shared attribute names. To do this it references static fields from the *Resource classes which in some cases also refer to the InfinispanResourceDescriptionResolver thus causing some fields to be null in certain cases.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4814) Publishing the site via awestruct doesn't work
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-4814?page=com.atlassian.jira.plugin.... ]
Dan Berindei edited comment on ISPN-4814 at 10/20/14 8:51 AM:
--------------------------------------------------------------
Work around the problem by running the git commands in the publish script directly.
was (Author: dan.berindei):
Work around the problem by running the explicit git commands.
> Publishing the site via awestruct doesn't work
> ----------------------------------------------
>
> Key: ISPN-4814
> URL: https://issues.jboss.org/browse/ISPN-4814
> Project: Infinispan
> Issue Type: Bug
> Components: Build process
> Affects Versions: 7.0.0.CR1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Labels: site
> Fix For: 7.0.0.CR2
>
>
> The {{publish_production.sh}} script uses {{awestruct --deploy}} to publish the site. Normally it should do something like this:
> {noformat}
> git checkout master
> cp -r _site/* .
> git commit -a -m "Published master to GitHub pages."
> git push origin master
> {noformat}
> Instead, it deletes everything on the master branch and pushes that, taking the site down (because GitHub relies on a CNAME file to find the domain name). The solution is to revert the commit (since some files are not generated) and publish the site manually.
> This could be caused by an incompatibility between the version of git on the CI machine and the 'git' gem used by awestruct.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4814) Publishing the site via awestruct doesn't work
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-4814?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-4814:
-------------------------------
Status: Open (was: New)
> Publishing the site via awestruct doesn't work
> ----------------------------------------------
>
> Key: ISPN-4814
> URL: https://issues.jboss.org/browse/ISPN-4814
> Project: Infinispan
> Issue Type: Bug
> Components: Build process
> Affects Versions: 7.0.0.CR1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Labels: site
> Fix For: 7.0.0.CR2
>
>
> The {{publish_production.sh}} script uses {{awestruct --deploy}} to publish the site. Normally it should do something like this:
> {noformat}
> git checkout master
> cp -r _site/* .
> git commit -a -m "Published master to GitHub pages."
> git push origin master
> {noformat}
> Instead, it deletes everything on the master branch and pushes that, taking the site down (because GitHub relies on a CNAME file to find the domain name). The solution is to revert the commit (since some files are not generated) and publish the site manually.
> This could be caused by an incompatibility between the version of git on the CI machine and the 'git' gem used by awestruct.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4814) Publishing the site via awestruct doesn't work
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-4814?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-4814:
-------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan.github.io/pull/8
Work around the problem by running the explicit git commands.
> Publishing the site via awestruct doesn't work
> ----------------------------------------------
>
> Key: ISPN-4814
> URL: https://issues.jboss.org/browse/ISPN-4814
> Project: Infinispan
> Issue Type: Bug
> Components: Build process
> Affects Versions: 7.0.0.CR1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Labels: site
> Fix For: 7.0.0.CR2
>
>
> The {{publish_production.sh}} script uses {{awestruct --deploy}} to publish the site. Normally it should do something like this:
> {noformat}
> git checkout master
> cp -r _site/* .
> git commit -a -m "Published master to GitHub pages."
> git push origin master
> {noformat}
> Instead, it deletes everything on the master branch and pushes that, taking the site down (because GitHub relies on a CNAME file to find the domain name). The solution is to revert the commit (since some files are not generated) and publish the site manually.
> This could be caused by an incompatibility between the version of git on the CI machine and the 'git' gem used by awestruct.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4681) Preloading from shared cachestore on a new node with non-shared index is skipping indexing
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-4681?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-4681:
------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Preloading from shared cachestore on a new node with non-shared index is skipping indexing
> ------------------------------------------------------------------------------------------
>
> Key: ISPN-4681
> URL: https://issues.jboss.org/browse/ISPN-4681
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Reporter: Sanne Grinovero
> Assignee: Gustavo Fernandes
> Fix For: 7.0.0.CR2, 7.0.0.Final
>
>
> We have a test already: {{org.infinispan.query.persistence.SharedCacheLoaderQueryIndexTest}}
> It was disabled for other reasons, mistakenly identified as a testsuite error.
> The case is simple: the test is configured in such a way to trigger a newly joining node using an in-memory dummy CacheStore which is shared by both nodes, with preloading enabled.
> Index storage is not shared though: uses {{ram}}.
> During the preload phase of the new node, the preload code issues the {{SKIP_INDEXING}} flag.. which in this case it should not.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4857) Extend old value/metadata information to Hot Rod remote events
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-4857?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño resolved ISPN-4857.
------------------------------------
Fix Version/s: (was: 7.0.0.Final)
(was: 7.0.0.CR2)
Resolution: Rejected
There are no changes to be done for Hot Rod remote events. User defined converters can ship old value/metadata information back to clients with custom events. Hot Rod client documentation with new class names...etc will be updated in ISPN-4861.
> Extend old value/metadata information to Hot Rod remote events
> --------------------------------------------------------------
>
> Key: ISPN-4857
> URL: https://issues.jboss.org/browse/ISPN-4857
> Project: Infinispan
> Issue Type: Feature Request
> Components: Remote Protocols
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
>
> Clustered listeners now provide old value and old metadata in their filter/converter callbacks, which can be useful for server-side filter/converter instances used in Hot Rod remote events.
> Investigate whether any code changes required in Hot Rod client/server code to take advantage of this.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4784) TestResourceTracker not working properly for OSGi tests
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-4784?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-4784:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 7.0.0.CR2
Resolution: Done
> TestResourceTracker not working properly for OSGi tests
> --------------------------------------------------------
>
> Key: ISPN-4784
> URL: https://issues.jboss.org/browse/ISPN-4784
> Project: Infinispan
> Issue Type: Enhancement
> Components: Test Suite - Core
> Affects Versions: 7.0.0.Beta2
> Reporter: Ion Savin
> Assignee: Ion Savin
> Fix For: 7.0.0.CR2
>
>
> The OSGi tests are running in a different process from the test driver and are executed through RMI. The assumptions that the test name is contained in the thread name and that there's a one-to-one mapping from thread to test is no longer valid (ThreadLocal used for the test name).
> Executing the tests in integrationtests/osgi will result in many log messages similar to this one:
> {noformat}
> Test name not set in unknown thread RMI TCP Connection(3)-127.0.0.1
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months