[ https://issues.jboss.org/browse/ISPN-4030?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic edited comment on ISPN-4030 at 2/27/14 11:28 AM:
---------------------------------------------------------------------
This is already possible as users can in the implementation of their DistributedCallable access any defined cache and write result to it. [~dan.berindei] please confirm and close the issue. See message post [1] and the enclosing discussion thread for more details.
[1] http://lists.jboss.org/pipermail/infinispan-dev/2014-February/014604.html
was (Author: vblagojevic):
This is already possible as users can in the implementation of their DistributedCallable access any defined cache and write result to it. [~dan.berindei] please confirm and close the issue. See message post [1] and the enclosing discussion thread.
[1] http://lists.jboss.org/pipermail/infinispan-dev/2014-February/014604.html
> Allow distributed executors to store results into cache
> -------------------------------------------------------
>
> Key: ISPN-4030
> URL: https://issues.jboss.org/browse/ISPN-4030
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core, Distributed Execution and Map/Reduce
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
>
> As soon as we introduce this API we need a notification mechanism about task/subtaks completion/failure. It should be introduced as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/ISPN-4030?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic commented on ISPN-4030:
-------------------------------------------
This is already possible as users can in the implementation of their DistributedCallable access any defined cache and write result to it. [~dan.berindei] please confirm and close the issue. See message post [1] and the enclosing discussion thread.
[1] http://lists.jboss.org/pipermail/infinispan-dev/2014-February/014604.html
> Allow distributed executors to store results into cache
> -------------------------------------------------------
>
> Key: ISPN-4030
> URL: https://issues.jboss.org/browse/ISPN-4030
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core, Distributed Execution and Map/Reduce
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
>
> As soon as we introduce this API we need a notification mechanism about task/subtaks completion/failure. It should be introduced as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Vojtech Juranek created ISPN-4061:
-------------------------------------
Summary: JPA Cache Store fails on Oracle, Postgres and MsSQL
Key: ISPN-4061
URL: https://issues.jboss.org/browse/ISPN-4061
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Reporter: Vojtech Juranek
Assignee: Dan Berindei
Current snapshot version of JPA Cache Store fails on Oracle (see [failed tests|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/infinispan-jpa...] with stack traces), Postgres ([failed tests|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/infinispan-jpa...]) and MsSQL ([failed tests|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/infinispan-jpa...]).
While in case of Oracle and Postgres the problem is probably in {{\_\_ispn_metadata__}} table, in case of MsSQL problem is in "User" entity, as User is reserved name in MySQL. In case of MySQL I'm not completely sure if it's bug or if it should be handled by user, but IMHO it should be considered as a bug, as JPA/Hibernate should provide DB agnostic interface and handle such cases.
Besides that {{VARBINARY}} type used in {{\_\_ispn_metadata__}} is not available in Postgres.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/ISPN-4041?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-4041:
------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> ForceWriteLockTest.testWriteLockIsAcquired always fails
> -------------------------------------------------------
>
> Key: ISPN-4041
> URL: https://issues.jboss.org/browse/ISPN-4041
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 6.0.1.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Labels: testsuite_stability
> Fix For: 7.0.0.Alpha1
>
>
> It appears the test is invalid, acquiring a write lock before the commit is not supported in optimistic mode: http://markmail.org/message/zvvxm4fjncjaktt2
> http://ci.infinispan.org/viewLog.html?buildId=6695&tab=buildResultsDiv&bu...
> {noformat}
> java.lang.NullPointerException
> at org.infinispan.api.ForceWriteLockTest.testWriteLockIsAcquired(ForceWriteLockTest.java:40)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/ISPN-4054?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-4054:
------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Scripts to analyze test failures and corresponding issues
> ---------------------------------------------------------
>
> Key: ISPN-4054
> URL: https://issues.jboss.org/browse/ISPN-4054
> Project: Infinispan
> Issue Type: Task
> Components: Test Suite - Core
> Affects Versions: 6.0.1.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 7.0.0.Alpha1
>
>
> Need an easy way to find scripts that fail in CI but don't have a corresponding issue in JIRA, or are not in the unstable group.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/ISPN-4035?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-4035:
------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> SingleFileStore.FileEntry.compareTo is wrong
> --------------------------------------------
>
> Key: ISPN-4035
> URL: https://issues.jboss.org/browse/ISPN-4035
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Loaders and Stores
> Affects Versions: 6.0.1.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Critical
> Fix For: 7.0.0.Alpha1
>
>
> Because {{FileEntry.compareTo(fe)}} never returns 0, allocated entries are not properly removed from the free list (at least on IBM JDK 6).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Jakub Markos created ISPN-4060:
----------------------------------
Summary: Update the recovery documentation
Key: ISPN-4060
URL: https://issues.jboss.org/browse/ISPN-4060
Project: Infinispan
Issue Type: Enhancement
Reporter: Jakub Markos
Assignee: Mircea Markus
Priority: Minor
I think we should mention that the recovery won't work with single-node infinispan. http://infinispan.org/docs/6.0.x/user_guide/user_guide.html#_transaction_...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/ISPN-3736?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-3736:
-----------------------------------------------
Richard Janík <rjanik(a)redhat.com> changed the Status of [bug 1036889|https://bugzilla.redhat.com/show_bug.cgi?id=1036889] from ON_QA to VERIFIED
> Backport to 5.2.x for EAP 6.3
> -----------------------------
>
> Key: ISPN-3736
> URL: https://issues.jboss.org/browse/ISPN-3736
> Project: Infinispan
> Issue Type: Task
> Components: Core
> Affects Versions: 5.2.7.Final
> Reporter: Paul Ferraro
> Assignee: Dan Berindei
> Fix For: 5.2.8.Final
>
>
> This JIRA will track the issues that need to be backported to the 5.2.x branch for EAP 6.3.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira