[JBoss JIRA] (ISPN-7971) Display a warning that changes in standalone mode are not persisted
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-7971?page=com.atlassian.jira.plugin.... ]
Pedro Zapata Fernandez closed ISPN-7971.
----------------------------------------
Resolution: Out of Date
> Display a warning that changes in standalone mode are not persisted
> -------------------------------------------------------------------
>
> Key: ISPN-7971
> URL: https://issues.jboss.org/browse/ISPN-7971
> Project: Infinispan
> Issue Type: Feature Request
> Components: JMX, reporting and management
> Reporter: Sebastian Laskawiec
> Assignee: Vladimir Blagojevic
> Priority: Major
> Attachments: Screen Shot 2017-07-26 at 9.45.27 AM.png
>
>
> The Infinispan Management Console can also operate in Standalone mode. We would like to make it accessible in OpenShift. However we should probably display a warning that the console should be used only for monitoring and none of the changes are persisted.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-7533) Accessing cache with disabled security resolves in SecurityException
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-7533?page=com.atlassian.jira.plugin.... ]
Pedro Zapata Fernandez closed ISPN-7533.
----------------------------------------
Resolution: Out of Date
> Accessing cache with disabled security resolves in SecurityException
> ---------------------------------------------------------------------
>
> Key: ISPN-7533
> URL: https://issues.jboss.org/browse/ISPN-7533
> Project: Infinispan
> Issue Type: Bug
> Components: Security, Server
> Affects Versions: 9.0.0.CR2
> Reporter: Roman Macor
> Assignee: Vojtech Juranek
> Priority: Blocker
>
> This happens when the security is defined in cache container, but the cache has security disabled.
> Steps to reproduce:
> - Start standalone with defined security e.g. docs/examples/configs/standalone-auth.xml
> - try accessing unsecured cache with hotrod e.g.
> {code:title=Reproducer.java|borderStyle=solid}
> ConfigurationBuilder builder = new ConfigurationBuilder();
> builder.addServer().host("127.0.0.1").port(ConfigurationProperties.DEFAULT_HOTROD_PORT)
> RemoteCacheManager cacheManager = new RemoteCacheManager(builder.build());
> RemoteCache<String, String> cache = cacheManager.getCache("default");
> cache.put("key", "value");
> System.out.printf("key = %s\n", cache.get("key"));
> cacheManager.stop();
> {code}
> Result:
> org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=3 returned server error (status=0x85): java.lang.SecurityException: ISPN006017: Unauthorized operation
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:363)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:152)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:138)
> at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:60)
> at org.infinispan.client.hotrod.impl.operations.AbstractKeyValueOperation.sendPutOperation(AbstractKeyValueOperation.java:58)
> at org.infinispan.client.hotrod.impl.operations.PutOperation.executeOperation(PutOperation.java:34)
> at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:56)
> at org.infinispan.client.hotrod.impl.RemoteCacheImpl.put(RemoteCacheImpl.java:269)
> at org.infinispan.client.hotrod.impl.RemoteCacheSupport.put(RemoteCacheSupport.java:79)
> at HotRodAuthTest.test(HotRodAuthTest.java:18)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-10696) Cluster Expiration reaper limits parallel expirations too much
by Pedro Ruivo (Jira)
[ https://issues.jboss.org/browse/ISPN-10696?page=com.atlassian.jira.plugin... ]
Pedro Ruivo reassigned ISPN-10696:
----------------------------------
Assignee: Will Burns
> Cluster Expiration reaper limits parallel expirations too much
> --------------------------------------------------------------
>
> Key: ISPN-10696
> URL: https://issues.jboss.org/browse/ISPN-10696
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 10.0.0.CR2
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
> Fix For: 10.0.0.CR3, 9.4.17.Final
>
>
> The expiration reaper today currently limits the expiration to only allow 5 pending expiration commands at once. It also doesn't submit more expirations until those 5 complete. We should do the following changes:
> # Increase the limit, possibly to 100?
> # Allow for extra expiration commands to be invoked as the others are complete, instead of waiting for all of them.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months