February 2013 - infinispan-issues

[JBoss JIRA] (ISPN-2809) Drop startServer.sh and use JDG harness to launch Infinispan servers

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2809?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2809: ---------------------------------- Summary: Drop startServer.sh and use JDG harness to launch Infinispan servers (was: Drop startServer.sh and use JDG harness to lunch Infinispan servers) > Drop startServer.sh and use JDG harness to launch Infinispan servers > -------------------------------------------------------------------- > > Key: ISPN-2809 > URL: https://issues.jboss.org/browse/ISPN-2809 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Reporter: Mircea Markus > Assignee: Tristan Tarrant > Fix For: 5.3.0.Beta1, 5.3.0.Final > > > this JIRA is practically about open sourcing JDG server harness code and use the same way of managing servers' lifecycle between ISPN and JDG. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2820) POST request with multipart/form-data encoding stores wrong content type

by Dan Berindei (JIRA)

Dan Berindei created ISPN-2820: ---------------------------------- Summary: POST request with multipart/form-data encoding stores wrong content type Key: ISPN-2820 URL: https://issues.jboss.org/browse/ISPN-2820 Project: Infinispan Issue Type: Bug Components: Remote protocols Affects Versions: 5.2.1 Reporter: Dan Berindei Assignee: Galder Zamarreño Fix For: 6.0.0.Final The REST server uses the {{Content-Type}} header of the POST request to determine the content type of the stored entry. But with {{Content-Type: multipart/form-data}}, each parameter can have its own content type (and {{multipart/form-data}} is definitely not any parameter's content type). This seems to be the way to do get the content type of each parameter: http://www.mkyong.com/webservices/jax-rs/file-upload-example-in-resteasy/ -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2819) REST server ignores client header Accept-Charset

by Dan Berindei (JIRA)

Dan Berindei created ISPN-2819: ---------------------------------- Summary: REST server ignores client header Accept-Charset Key: ISPN-2819 URL: https://issues.jboss.org/browse/ISPN-2819 Project: Infinispan Issue Type: Bug Components: Remote protocols Affects Versions: 5.2.1 Reporter: Dan Berindei Assignee: Galder Zamarreño Fix For: 6.0.0.Final In a HTTP GET request, the client can specify an {{Accept-Charset}} header. The REST server will ignore it, and it will always send the response with the original PUT/POST request's charset. I think the server should make an effort to transform the value data from the PUT charset to the GET charset. At the moment we don't even parse the PUT charset, we just store the {{Content-Type}} header. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2791) Support Scripted Mapper, Reducer and Collator with JSR 223

by Ray Tsang (JIRA)

[ https://issues.jboss.org/browse/ISPN-2791?page=com.atlassian.jira.plugin.... ] Ray Tsang commented on ISPN-2791: --------------------------------- Mircea - my understanding of the ISPN-1090 subtask is to make M/R work over Hotrod protocol. It would be nice to make sure for that implementation, Scripted mapper, reduce, and collator can also work w/o hotrod as well. > Support Scripted Mapper, Reducer and Collator with JSR 223 > ---------------------------------------------------------- > > Key: ISPN-2791 > URL: https://issues.jboss.org/browse/ISPN-2791 > Project: Infinispan > Issue Type: Feature Request > Components: Core API > Reporter: Ray Tsang > Assignee: Mircea Markus > > Support scripted mapper, reducer, and collator for MR tasks. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2396) For failing injected transactions, the rollback is incorrectly invoked

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2396?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2396: -------------------------------- Issue Type: Bug (was: Feature Request) > For failing injected transactions, the rollback is incorrectly invoked > ----------------------------------------------------------------------- > > Key: ISPN-2396 > URL: https://issues.jboss.org/browse/ISPN-2396 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.1.0.FINAL > Reporter: Mircea Markus > Assignee: Mircea Markus > Priority: Minor > Fix For: 5.2.0.Beta3, 5.2.0.Final > > -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2426) putForExternalRead() does not unlock if entry already exists

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2426?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2426: -------------------------------- Issue Type: Bug (was: Patch) > putForExternalRead() does not unlock if entry already exists > ------------------------------------------------------------ > > Key: ISPN-2426 > URL: https://issues.jboss.org/browse/ISPN-2426 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.1.6.FINAL > Reporter: Jan Boehm > Assignee: Manik Surtani > Priority: Blocker > Fix For: 5.1.9.Final, 5.2.0.Beta4, 5.2.0.Final > > Attachments: ISPN-2426-Set-looked-up-key-in-InvocationContext-on-.patch > > > When performing a {{putForExternalRead()}} for an existing entry, the entry factory fails to provide the InvocationContext with the key for the entry. This makes it impossible for the locking interceptors to release the lock. > Note that this is only a problem when used in a non-transactional context. When transactions are used, no stale locks are observed. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2818) Update the quickstart pom files to match changes made in the jboss-jdf repository

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/ISPN-2818?page=com.atlassian.jira.plugin.... ] Sande Gilda updated ISPN-2818: ------------------------------ Description: There were numerous changes to the quickstart pom files: - property names were shortened and standardized - property versions were updated - comments were standardized around product/community version numbers It may be easiest just to copy and paste the corresponding jboss-jdf quickstart pom.xml files into your repository, however, these are the commits: https://github.com/sgilda/quickstart/commit/ca2a7bea84262a7aa28b082760746... https://github.com/sgilda/quickstart/commit/d951d07c1a2e980b0550ff62145cf... was: There were numerous changes to the quickstart pom files: - property names were shortened and standardized - property versions were updated - comments were standardized around product/community version numbers It may be easiest just to copy and paste the corresponding quickstart pom.xml files from jboss-jdf into your repository. > Update the quickstart pom files to match changes made in the jboss-jdf repository > --------------------------------------------------------------------------------- > > Key: ISPN-2818 > URL: https://issues.jboss.org/browse/ISPN-2818 > Project: Infinispan > Issue Type: Bug > Components: Demos and Tutorials > Reporter: Sande Gilda > Assignee: Mircea Markus > > There were numerous changes to the quickstart pom files: > - property names were shortened and standardized > - property versions were updated > - comments were standardized around product/community version numbers > It may be easiest just to copy and paste the corresponding jboss-jdf quickstart pom.xml files into your repository, however, these are the commits: > https://github.com/sgilda/quickstart/commit/ca2a7bea84262a7aa28b082760746... > https://github.com/sgilda/quickstart/commit/d951d07c1a2e980b0550ff62145cf... -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2737) Thread naming anomaly when reporting lock timeout

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2737?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2737: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Thread naming anomaly when reporting lock timeout > ------------------------------------------------- > > Key: ISPN-2737 > URL: https://issues.jboss.org/browse/ISPN-2737 > Project: Infinispan > Issue Type: Bug > Components: Locking and Concurrency, RPC > Affects Versions: 5.2.0.CR1 > Reporter: Michal Linhard > Assignee: Galder Zamarreño > Priority: Minor > Fix For: 5.2.2, 5.3.0.Final > > > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... > {code} > 11:47:30,859 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (MemcachedServerWorker-277) ISPN000136: Execution error: org.infinispan.util.concurrent.TimeoutException: Unable to acquire lock after [3 seconds] on key [memcachedCache#key763328] for requestor [Thread[OOB-127,null,5,Thread Pools]]! Lock held by [Thread[OOB-150,null,5,Thread Pools]] > at org.infinispan.util.concurrent.locks.LockManagerImpl.lock(LockManagerImpl.java:217) [infinispan-core-5.2.0.CR1-redhat-1.jar:5.2.0.CR1-redhat-1] > at org.infinispan.util.concurrent.locks.LockManagerImpl.acquireLockNoCheck(LockManagerImpl.java:200) [infinispan-core-5.2.0.CR1-redhat-1.jar:5.2.0.CR1-redhat-1] > at org.infinispan.interceptors.locking.AbstractLockingInterceptor.lockKey(AbstractLockingInterceptor.java:114) [infinispan-core-5.2.0.CR1-redhat-1.jar:5.2.0.CR1-redhat-1] > .... > at org.jgroups.protocols.MERGE2.up(MERGE2.java:205) [jgroups-3.2.5.Final-redhat-1.jar:3.2.5.Final-redhat-1] > at org.jgroups.protocols.Discovery.up(Discovery.java:359) [jgroups-3.2.5.Final-redhat-1.jar:3.2.5.Final-redhat-1] > at org.jgroups.protocols.TP$ProtocolAdapter.up(TP.java:2640) [jgroups-3.2.5.Final-redhat-1.jar:3.2.5.Final-redhat-1] > at org.jgroups.protocols.TP.passMessageUp(TP.java:1287) [jgroups-3.2.5.Final-redhat-1.jar:3.2.5.Final-redhat-1] > at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1850) [jgroups-3.2.5.Final-redhat-1.jar:3.2.5.Final-redhat-1] > at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1823) [jgroups-3.2.5.Final-redhat-1.jar:3.2.5.Final-redhat-1] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_38] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_38] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_38] > {code} > note the thread name "MemcachedServerWorker" in an operation coming from the JGroups stack... -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2818) Update the quickstart pom files to match changes made in the jboss-jdf repository

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/ISPN-2818?page=com.atlassian.jira.plugin.... ] Sande Gilda updated ISPN-2818: ------------------------------ Description: There were numerous changes to the quickstart pom files: - property names were shortened and standardized - property versions were updated - comments were standardized around product/community version numbers It may be easiest just to copy and paste the corresponding quickstart pom.xml files from jboss-jdf into your repository. was: There were numerous changes to the pom files: - property names were shortened and standardized - property versions were updated - comments were standardized around product/community version numbers It may be easiest just to copy and paste the corresponding quickstart pom.xml files from jboss-jdf into your repository. > Update the quickstart pom files to match changes made in the jboss-jdf repository > --------------------------------------------------------------------------------- > > Key: ISPN-2818 > URL: https://issues.jboss.org/browse/ISPN-2818 > Project: Infinispan > Issue Type: Bug > Components: Demos and Tutorials > Reporter: Sande Gilda > Assignee: Mircea Markus > > There were numerous changes to the quickstart pom files: > - property names were shortened and standardized > - property versions were updated > - comments were standardized around product/community version numbers > It may be easiest just to copy and paste the corresponding quickstart pom.xml files from jboss-jdf into your repository. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2818) Update the quickstart pom files to match changes made in the jboss-jdf repository

by Sande Gilda (JIRA)

Sande Gilda created ISPN-2818: --------------------------------- Summary: Update the quickstart pom files to match changes made in the jboss-jdf repository Key: ISPN-2818 URL: https://issues.jboss.org/browse/ISPN-2818 Project: Infinispan Issue Type: Bug Components: Demos and Tutorials Reporter: Sande Gilda Assignee: Mircea Markus There were numerous changes to the pom files: - property names were shortened and standardized - property versions were updated - comments were standardized around product/community version numbers It may be easiest just to copy and paste the corresponding quickstart pom.xml files from jboss-jdf into your repository. -- 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

13 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2013