May 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4308) ISPN testsuite fails randomly with OOM, HEAP size

by Vitalii Chepeliuk (JIRA)

Vitalii Chepeliuk created ISPN-4308: --------------------------------------- Summary: ISPN testsuite fails randomly with OOM, HEAP size Key: ISPN-4308 URL: https://issues.jboss.org/browse/ISPN-4308 Project: Infinispan Issue Type: Bug Components: Build process Affects Versions: 7.0.0.Alpha4, 7.0.0.Alpha2, 7.0.0.Alpha1 Environment: All Reporter: Vitalii Chepeliuk Assignee: Mircea Markus Priority: Critical When running ISPN testsuite following error is randomly ocurred {noformat} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.14.1:test (default-test) on project infinispan-core: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.14.1:test failed: There was an error in the forked process [ERROR] java.lang.OutOfMemoryError: Java heap space [ERROR] at java.io.BufferedWriter.<init>(BufferedWriter.java:116) [ERROR] at java.io.BufferedWriter.<init>(BufferedWriter.java:99) [ERROR] at org.testng.internal.Utils.writeFile(Utils.java:190) [ERROR] at org.testng.internal.Utils.writeFile(Utils.java:165) [ERROR] at org.testng.internal.Utils.appendToFile(Utils.java:142) [ERROR] at org.testng.reporters.SuiteHTMLReporter.generateMethodsChronologically(SuiteHTMLReporter.java:442) [ERROR] at org.testng.reporters.SuiteHTMLReporter.generateReport(SuiteHTMLReporter.java:72) [ERROR] at org.testng.TestNG.generateReports(TestNG.java:1089) [ERROR] at org.testng.TestNG.run(TestNG.java:1048) [ERROR] at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:77) [ERROR] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:189) [ERROR] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:105) [ERROR] at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:117) [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:94) [ERROR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) [ERROR] at java.lang.reflect.Method.invoke(Method.java:619) [ERROR] at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) [ERROR] at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:159) [ERROR] at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:87) [ERROR] at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) [ERROR] at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:95) [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. {noformat} Problem is in surefire plugin as it does not inherit JAVA_OPTS or MAVEN_OPTS. Heap settings should be set through argLine in maven-surefire-plugin. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4306) HR client auth over kerberos has wrong AccessControlContext

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4306?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4306: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1099813 > HR client auth over kerberos has wrong AccessControlContext > ----------------------------------------------------------- > > Key: ISPN-4306 > URL: https://issues.jboss.org/browse/ISPN-4306 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Reporter: Vojtech Juranek > Assignee: Tristan Tarrant > > When HotRod client authneticate to HR server via kerberos, HR server obtains wrong {{AccessControlContext}}, which doesn't contain appropriate subject (to be more clear it's in [AuthorizationManagerImpl.checkPermission()|https://github.com/infinispan/...]). Returned subject is {{null}} and moreover this default {{AccessControlContext}} allows to do anything, so effectively the HR client can do anything, no matter what the permissions are. > Need to mention that in this case java {{SecurityManager}} is turned off, but as the same setup works with e.g. MD5 auth, we should keep some consistency and it shouldn't work in any case (and {{SecurityManager}} to be turned on should be a hard requirement to ISPN auth works) or it should work also in case of krb auth. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4306) HR client auth over kerberos has wrong AccessControlContext

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4306?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-4306: ------------------------------------- Assignee: Tristan Tarrant (was: Mircea Markus) > HR client auth over kerberos has wrong AccessControlContext > ----------------------------------------------------------- > > Key: ISPN-4306 > URL: https://issues.jboss.org/browse/ISPN-4306 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Reporter: Vojtech Juranek > Assignee: Tristan Tarrant > > When HotRod client authneticate to HR server via kerberos, HR server obtains wrong {{AccessControlContext}}, which doesn't contain appropriate subject (to be more clear it's in [AuthorizationManagerImpl.checkPermission()|https://github.com/infinispan/...]). Returned subject is {{null}} and moreover this default {{AccessControlContext}} allows to do anything, so effectively the HR client can do anything, no matter what the permissions are. > Need to mention that in this case java {{SecurityManager}} is turned off, but as the same setup works with e.g. MD5 auth, we should keep some consistency and it shouldn't work in any case (and {{SecurityManager}} to be turned on should be a hard requirement to ISPN auth works) or it should work also in case of krb auth. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4306) HR client auth over kerberos has wrong AccessControlContext

by Vojtech Juranek (JIRA)

Vojtech Juranek created ISPN-4306: ------------------------------------- Summary: HR client auth over kerberos has wrong AccessControlContext Key: ISPN-4306 URL: https://issues.jboss.org/browse/ISPN-4306 Project: Infinispan Issue Type: Bug Components: Test Suite - Server Reporter: Vojtech Juranek Assignee: Mircea Markus When HotRod client authneticate to HR server via kerberos, HR server obtains wrong {{AccessControlContext}}, which doesn't contain appropriate subject (to be more clear it's in [AuthorizationManagerImpl.checkPermission()|https://github.com/infinispan/...]). Returned subject is {{null}} and moreover this default {{AccessControlContext}} allows to do anything, so effectively the HR client can do anything, no matter what the permissions are. Need to mention that in this case java {{SecurityManager}} is turned off, but as the same setup works with e.g. MD5 auth, we should keep some consistency and it shouldn't work in any case (and {{SecurityManager}} to be turned on should be a hard requirement to ISPN auth works) or it should work also in case of krb auth. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4305) Add the need to install Protoc for remote query quickstart to documentation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4305?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4305: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1099802 > Add the need to install Protoc for remote query quickstart to documentation > --------------------------------------------------------------------------- > > Key: ISPN-4305 > URL: https://issues.jboss.org/browse/ISPN-4305 > Project: Infinispan > Issue Type: Enhancement > Components: Demos and Tutorials > Affects Versions: 7.0.0.Alpha4 > Reporter: Jiří Holuša > Assignee: Jiří Holuša > > During the build of remote query quickstart there's used protoc. Without protoc being properly installed, the quickstart doesn't build. > Document the fact that installed protoc is necessary for building this quickstart. (add this to README.txt) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4305) Add the need to install Protoc for remote query quickstart to documentation

by Jiří Holuša (JIRA)

[ https://issues.jboss.org/browse/ISPN-4305?page=com.atlassian.jira.plugin.... ] Jiří Holuša updated ISPN-4305: ------------------------------ Git Pull Request: https://github.com/jboss-developer/jboss-jdg-quickstarts/pull/38 > Add the need to install Protoc for remote query quickstart to documentation > --------------------------------------------------------------------------- > > Key: ISPN-4305 > URL: https://issues.jboss.org/browse/ISPN-4305 > Project: Infinispan > Issue Type: Enhancement > Components: Demos and Tutorials > Affects Versions: 7.0.0.Alpha4 > Reporter: Jiří Holuša > Assignee: Jiří Holuša > > During the build of remote query quickstart there's used protoc. Without protoc being properly installed, the quickstart doesn't build. > Document the fact that installed protoc is necessary for building this quickstart. (add this to README.txt) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4305) Add the need to install Protoc for remote query quickstart to documentation

by Jiří Holuša (JIRA)

Jiří Holuša created ISPN-4305: --------------------------------- Summary: Add the need to install Protoc for remote query quickstart to documentation Key: ISPN-4305 URL: https://issues.jboss.org/browse/ISPN-4305 Project: Infinispan Issue Type: Enhancement Components: Demos and Tutorials Affects Versions: 7.0.0.Alpha4 Reporter: Jiří Holuša Assignee: Jiří Holuša During the build of remote query quickstart there's used protoc. Without protoc being properly installed, the quickstart doesn't build. Document the fact that installed protoc is necessary for building this quickstart. (add this to README.txt) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4293) PR for ISPN-4137 causes a performance drop in repl tx mode

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4293?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-4293: ------------------------------------ The PR for ISPN-4131 also caused a perf drop in tx mode To fix ISPN-4131 we have to keep track of the highest tx id removed from the completed txs map by the cleanup thread. The initial fix thus required accessing two maps both to check if a tx was already completed and to mark a tx as completed. I was able to eliminate the second map lookup for marking the tx as completed in the commit command, reducing the overhead somewhat. > PR for ISPN-4137 causes a performance drop in repl tx mode > ---------------------------------------------------------- > > Key: ISPN-4293 > URL: https://issues.jboss.org/browse/ISPN-4293 > Project: Infinispan > Issue Type: Bug > Reporter: Jakub Markos > Assignee: Dan Berindei > > See the last graph here for example http://jawa36.mw.lab.eng.brq.redhat.com:8080/repo/reports/metric/saved/te... > Caused by this commit https://github.com/infinispan/infinispan/commit/8be817a193699ce8b59aec8da... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1935) Provide tree cache specific listener callbacks

by Deepak Devje (JIRA)

[ https://issues.jboss.org/browse/ISPN-1935?page=com.atlassian.jira.plugin.... ] Deepak Devje commented on ISPN-1935: ------------------------------------ Hello - do we have a solution for this? I am particularly interested in the callback implementation. > Provide tree cache specific listener callbacks > ---------------------------------------------- > > Key: ISPN-1935 > URL: https://issues.jboss.org/browse/ISPN-1935 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 5.1.2.FINAL > Reporter: Michael Gronau > Assignee: Galder Zamarreño > Labels: API, CacheEntryModified, Notifications, TreeCache > Attachments: TreeListenerTest.java > > > A put operation to the TreeCache API causes multiple CacheEntryModified events to be fired. The data map (an AtomicHashMap) is always empty and does not contain the modifications. The notifications are fired twice for isPre=false and isPre=true, which means they are fired 4 times. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4108) Pessimistic tx for a union CH will not be forwarded to all owners.

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-4108?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-4108: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.Beta1 Resolution: Done > Pessimistic tx for a union CH will not be forwarded to all owners. > ------------------------------------------------------------------ > > Key: ISPN-4108 > URL: https://issues.jboss.org/browse/ISPN-4108 > Project: Infinispan > Issue Type: Bug > Components: State Transfer > Affects Versions: 5.2.7.Final > Reporter: Erik Salter > Assignee: Dan Berindei > Fix For: 7.0.0.Beta1 > > > There is a case where transactions originating from a LockControlCommand will not be forwarded to the new owner during state transfer. > If the transactions begin on the old primary owner after the tx list was sent to the new owner, the lock information may not be replicated to the joiner because the originator is still the primary owner in the union CH that we use during state transfer. When state transfer ends and the joiner becomes the new primary owner, it will allow other txs to lock the same key. This leads to data loss/inconsistency. > We should change PessimisticLockingInterceptor to replicate the lock command to the other owners even if the originator is the primary owner when there is a state transfer in progress. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2014