[JBoss JIRA] (ISPN-4299) Authentication configuration builder requires CallbackHandle also when subject it set
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4299?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4299:
-----------------------------------------------
Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1099055|https://bugzilla.redhat.com/show_bug.cgi?id=1099055] from MODIFIED to ON_QA
> Authentication configuration builder requires CallbackHandle also when subject it set
> -------------------------------------------------------------------------------------
>
> Key: ISPN-4299
> URL: https://issues.jboss.org/browse/ISPN-4299
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Reporter: Vojtech Juranek
> Assignee: Tristan Tarrant
> Priority: Minor
> Fix For: 7.0.0.Alpha5
>
>
> Authentication configuration builder allows to setup direcly subject under which action are performed. In this case there's no need for any additional authentication. However authentication configuration builder requires {{CallbackHandler}} also in this case and without it it fails with
> {noformat}
> org.infinispan.commons.CacheConfigurationException: ISPN004030: Cannot enable authentication without specifying a Callback Handler
> at org.infinispan.client.hotrod.configuration.AuthenticationConfigurationBuilder.validate(AuthenticationConfigurationBuilder.java:86)
> at org.infinispan.client.hotrod.configuration.SecurityConfigurationBuilder.validate(SecurityConfigurationBuilder.java:43)
> at org.infinispan.client.hotrod.configuration.ConfigurationBuilder.validate(ConfigurationBuilder.java:280)
> at org.infinispan.client.hotrod.configuration.ConfigurationBuilder.build(ConfigurationBuilder.java:314)
> at org.infinispan.client.hotrod.configuration.ConfigurationBuilder.build(ConfigurationBuilder.java:309)
> at org.infinispan.server.test.client.hotrod.security.HotRodSaslAuthTestBase.getRemoteCacheManagerConfig(HotRodSaslAuthTestBase.java:104)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 4 months
[JBoss JIRA] (ISPN-4351) Clarify the behaviour of putForExternalRead in clustered caches
by Dan Berindei (JIRA)
Dan Berindei created ISPN-4351:
----------------------------------
Summary: Clarify the behaviour of putForExternalRead in clustered caches
Key: ISPN-4351
URL: https://issues.jboss.org/browse/ISPN-4351
Project: Infinispan
Issue Type: Task
Components: Core, Documentation-Core
Affects Versions: 6.0.2.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 7.0.0.Final
The {{putForExternal}} [documentation|http://infinispan.org/docs/7.0.x/user_guide/user_guide.html...] says
{quote}
putForExternalRead is consider to be a fast operation because regardless of whether it’s successful or not, it doesn’t wait for any locks, and so returns to the caller promptly.
{quote}
But the documentation doesn't say how {{putForExternalRead}} should behave in a clustered cache. Currently, the command is replicated to all the owners in distributed mode, and to all the cluster members in replicated mode. So the command may be delayed while waiting for the responses from those other nodes. The exception is invalidation mode, which doesn't replicate {{putForExternalRead}} commands - only regular {{put}}s generate invalidations.
The documentation also doesn't mention the interaction of {{putForExternalRead}} operations with transactions. Currently, {{PUT_FOR_EXTERNAL_READ}}-flagged commands are executed as non-transactional commands even when the cache is transactional, presumably to avoid the overhead of transactions. But this undermines the argument for wrapping regular write operations in an implicit transaction, when running in a transactional cache.
I propose changing {{putForExternalRead}} to only write on the local node (as it already does in invalidation mode), and documenting it as such. In distribution mode, it should be a no-op when the local node is not an owner.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 4 months
[JBoss JIRA] (ISPN-4349) Configuration parser doesn't allow to have <async/>, <properties/> and <singleton/> elements inside of <store/> element
by Alexey Olenev (JIRA)
[ https://issues.jboss.org/browse/ISPN-4349?page=com.atlassian.jira.plugin.... ]
Alexey Olenev updated ISPN-4349:
--------------------------------
Description:
Despite infinispan-config-6.0.xsd says that there can be a <async/>, <properties/> and <singleton/> elements inside of <store/>, actually if you configure custom store using <store/> element, configuration parser (org.infinispan.configuration.parsing.Parser60) throws exception:
org.infinispan.commons.CacheConfigurationException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[104,29]
Message: Unexpected element '{urn:infinispan:config:6.0}properties'
at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:102)
at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:253)
at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:226)
at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:213)
at org.sproot_grid.cache.ClusterFacade.init(ClusterFacade.java:48)
at org.sproot_grid.cache.ClusterFacade.getFacade(ClusterFacade.java:41)
at org.sproot_grid.cache.ClusterFacadeTest.initCluster(ClusterFacadeTest.java:21)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[104,29]
Message: Unexpected element '{urn:infinispan:config:6.0}properties'
at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:139)
at org.infinispan.configuration.parsing.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:37)
at org.infinispan.configuration.parsing.Parser60.parsePersistence(Parser60.java:558)
at org.infinispan.configuration.parsing.Parser60.parseCache(Parser60.java:150)
at org.infinispan.configuration.parsing.Parser60.parseNamedCache(Parser60.java:109)
at org.infinispan.configuration.parsing.Parser60.readElement(Parser60.java:76)
at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:141)
at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:123)
at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:110)
at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:97)
... 21 more
This exception occurs because of org.infinispan.configuration.parsing.Parser60.parseStore (lines 668-685). This code means that method parseStoreChildren() will be called just if my custom store is a subclass of SingleFileStore, and this method is responsible for parsing such elements as <async/>, <properties/> and <singleton/>
was:
Despite infinispan-config-6.0.xsd says that there can be a <async/>, <properties/> and <singleton/> elements inside of <store/>, actually if you configure custom store using <store/> element, configuration parser (org.infinispan.configuration.parsing.Parser60) throws exception:
org.infinispan.commons.CacheConfigurationException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[104,29]
Message: Unexpected element '{urn:infinispan:config:6.0}properties'
at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:102)
at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:253)
at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:226)
at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:213)
at org.sproot_grid.cache.ClusterFacade.init(ClusterFacade.java:48)
at org.sproot_grid.cache.ClusterFacade.getFacade(ClusterFacade.java:41)
at org.sproot_grid.cache.ClusterFacadeTest.initCluster(ClusterFacadeTest.java:21)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[104,29]
Message: Unexpected element '{urn:infinispan:config:6.0}properties'
at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:139)
at org.infinispan.configuration.parsing.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:37)
at org.infinispan.configuration.parsing.Parser60.parsePersistence(Parser60.java:558)
at org.infinispan.configuration.parsing.Parser60.parseCache(Parser60.java:150)
at org.infinispan.configuration.parsing.Parser60.parseNamedCache(Parser60.java:109)
at org.infinispan.configuration.parsing.Parser60.readElement(Parser60.java:76)
at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:141)
at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:123)
at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:110)
at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:97)
... 21 more
This exception occurs because of following code snippet from org.infinispan.configuration.parsing.Parser60 (lines 668-685):
if (store != null) {
if (store instanceof SingleFileStore) {
SingleFileStoreConfigurationBuilder sfs = builder.persistence().addSingleFileStore();
if (fetchPersistentState != null)
sfs.fetchPersistentState(fetchPersistentState);
if (ignoreModifications != null)
sfs.ignoreModifications(ignoreModifications);
if (purgeOnStartup != null)
sfs.purgeOnStartup(purgeOnStartup);
if (preload != null)
sfs.preload(preload);
if (shared != null)
sfs.shared(shared);
parseStoreChildren(reader, sfs);
} else if (store instanceof ClusterLoader) {
ClusterLoaderConfigurationBuilder cscb = builder.persistence().addClusterLoader();
parseLoaderChildren(reader, cscb);
}
It means that method parseStoreChildren() will be called just if my custom store is a subclass of SingleFileStore, and this method is responsible for parsing such elements as <async/>, <properties/> and <singleton/>
> Configuration parser doesn't allow to have <async/>, <properties/> and <singleton/> elements inside of <store/> element
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-4349
> URL: https://issues.jboss.org/browse/ISPN-4349
> Project: Infinispan
> Issue Type: Bug
> Components: Configuration, Loaders and Stores
> Affects Versions: 6.0.2.Final
> Reporter: Alexey Olenev
> Assignee: Dan Berindei
>
> Despite infinispan-config-6.0.xsd says that there can be a <async/>, <properties/> and <singleton/> elements inside of <store/>, actually if you configure custom store using <store/> element, configuration parser (org.infinispan.configuration.parsing.Parser60) throws exception:
> org.infinispan.commons.CacheConfigurationException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[104,29]
> Message: Unexpected element '{urn:infinispan:config:6.0}properties'
> at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:102)
> at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:253)
> at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:226)
> at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:213)
> at org.sproot_grid.cache.ClusterFacade.init(ClusterFacade.java:48)
> at org.sproot_grid.cache.ClusterFacade.getFacade(ClusterFacade.java:41)
> at org.sproot_grid.cache.ClusterFacadeTest.initCluster(ClusterFacadeTest.java:21)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[104,29]
> Message: Unexpected element '{urn:infinispan:config:6.0}properties'
> at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:139)
> at org.infinispan.configuration.parsing.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:37)
> at org.infinispan.configuration.parsing.Parser60.parsePersistence(Parser60.java:558)
> at org.infinispan.configuration.parsing.Parser60.parseCache(Parser60.java:150)
> at org.infinispan.configuration.parsing.Parser60.parseNamedCache(Parser60.java:109)
> at org.infinispan.configuration.parsing.Parser60.readElement(Parser60.java:76)
> at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:141)
> at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:123)
> at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:110)
> at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:97)
> ... 21 more
> This exception occurs because of org.infinispan.configuration.parsing.Parser60.parseStore (lines 668-685). This code means that method parseStoreChildren() will be called just if my custom store is a subclass of SingleFileStore, and this method is responsible for parsing such elements as <async/>, <properties/> and <singleton/>
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 4 months