exo.jcr.component.core.impl.infinispan.v5

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
[maven-release-plugin] prepare for next development iteration

  1. … 26 more files in changeset.
[maven-release-plugin] prepare release 1.15.14-GA

  1. … 26 more files in changeset.
JCR-2389: Add profile mysql-5.6

  1. … 2 more files in changeset.
JCR-2389 : Add profile Mysql-5.6

  1. … 2 more files in changeset.
JCR-2389: Error when start jboss/tomcat with mysql 5.6 in UTF-8 (Part 2)

  1. … 5 more files in changeset.
JCR-2389: Error when start Platform with MySQL 5.6 in UTF-8 (Part 2)

Fix description:

* Restrict the length of CAS_ID when creating index

* Add dialect in test configurations.

  1. … 5 more files in changeset.
[maven-release-plugin] [PLF-6276]prepare for next development iteration

  1. … 26 more files in changeset.
[maven-release-plugin] [PLF-6276]prepare release 1.15.13-GA

  1. … 26 more files in changeset.
[maven-release-plugin] [PLF-6220]prepare for next development iteration

  1. … 26 more files in changeset.
[maven-release-plugin] [PLF-6220]prepare release 1.15.12-GA

  1. … 26 more files in changeset.
SWF-2705, SWF-3117, SWF-3190 : Create pdf-js branch and update projects versions

  1. … 26 more files in changeset.
JCR-2372 : NPE with PostgreSQL 9.2 and 9.3 in jUnit tests

Problem analysis

- The error occurs when we launch tests with the driver 9.3-1102 JDBC4 is due to a

lack of permission for reading system property "org.postgresql.force binary"

Fix description

- Add read permission for the system property org.postgresql.forcebinary (Add this permission in the java.security.policy). This change affects only test execution for jcr.

  1. … 4 more files in changeset.
JCR-2372 : NPE with PostgreSQL 9.2 and 9.3 in jUnit tests

  1. … 4 more files in changeset.
JCR-2372 : NPE with PostgreSQL 9.2 and 9.3 in jUnit tests

  1. … 2 more files in changeset.
[maven-release-plugin] [PLF-6112]prepare for next development iteration

  1. … 26 more files in changeset.
[maven-release-plugin] [PLF-6112]prepare release 1.15.11-GA

  1. … 26 more files in changeset.
JCR-2323: Wrong Upload size on cluster mode

Problem analysis:

- On clustering mode : for files whose size exceeds the buffer value (by default 200K), the steps are as follows:

- The property jcr:data is built in the first node having the value of an object (more precisely of StremValuePropertyData type) that has an instance variable with the name "file" containing the file path in the value storage and point on a path in the swap file.

- When this property is applied to the second node and the object is intercepted, the logic responsible for the serialization of the object simply checks if the file exists in the system or not (which is not the case) and make it "null" if necessary.

Fix description

- When the path file of StremValuePropertyData is null, do forceLoad the property data from the DB storage.

  1. … 7 more files in changeset.
JCR-2323: Wrong Upload size on cluster mode

  1. … 6 more files in changeset.
JCR-2323 : Wrong Upload size on cluster mode (Part 2)

  1. … 5 more files in changeset.
[maven-release-plugin] [PLF-5989]prepare for next development iteration

  1. … 26 more files in changeset.
[maven-release-plugin] [PLF-5989]prepare release 1.15.10-GA

  1. … 26 more files in changeset.
JCR-2312 : Cannot start eXo JCR with MySQL in UTF-8

Fix description:

- Relimit character number of a varchar field if dialect is mysql and utf-8

  1. … 12 more files in changeset.
JCR-2312 : Cannot start eXo JCR with MySQL in UTF-8

  1. … 12 more files in changeset.
JCR-2312 : use the same dialect variable for jcr and lock

  1. … 2 more files in changeset.
JCR-2312 : use the same dialect variable for jcr and lock

  1. … 11 more files in changeset.
JCR-2312 : Cannot start eXo JCR with MySQL in UTF-8

  1. … 13 more files in changeset.
JCR-2312 : Cannot start eXo JCR with MySQL in UTF-8

  1. … 7 more files in changeset.
JCR-2288: JCR-2309 Avoid replication for local changes

  1. … 1 more file in changeset.
JCR-2288: [Cluster] Adding nodes to the same parent node causes TimeoutException

Problem analysis

- The goal of this task is to get rid or limit the risk of getting TimeoutException when we concurrently add nodes to the same parent node in a cluster environment.

Fix description

- When we add a new child node, we have to invalidate the list of child nodes of the parent node in the cache which was done by a simple remove of the related cache entry. The problem with this approach is the fact that this remove was done in a global tx so when it is done concurrently we can face deadlock like in this particular use case. The fix simply isolates the invalidation by doing it outside the global tx in order to highly reduce the risk of such deadlocks. The second part of the fix ensures that if we do a local change, the related commands commit/rollback remain local because before the fix they were replicated even for local changes.

  1. … 7 more files in changeset.
JCR-2288: [Cluster] Adding nodes to the same parent node causes TimeoutException

  1. … 7 more files in changeset.