March 2010 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-379) JGroupsChannelLookup should take in Properties created from props set on the transport

by Manik Surtani (JIRA)

JGroupsChannelLookup should take in Properties created from props set on the transport -------------------------------------------------------------------------------------- Key: ISPN-379 URL: https://jira.jboss.org/jira/browse/ISPN-379 Project: Infinispan Issue Type: Feature Request Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.ALPHA2, 4.1.0.Final The current JGroupsChannelLookup interface - http://docs.jboss.org/infinispan/4.1/apidocs/org/infinispan/remoting/tran... - does not have a mechanism to receive any configuration props. When configuring a transport, Infinispan allows arbitrary <properties /> to be set (see http://docs.jboss.org/infinispan/4.1/apidocs/config.html#ce_global_transport). These should simply be passed in to JGroupsChannelLookup.getJGroupsChannel(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (ISPN-365) Topology diagrams for different Infinispan clustering modes

by Manik Surtani (JIRA)

Topology diagrams for different Infinispan clustering modes ----------------------------------------------------------- Key: ISPN-365 URL: https://jira.jboss.org/jira/browse/ISPN-365 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.0.1.Final See forum post for request details. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
1
0 / 0

[JBoss JIRA] Updated: (ISPN-27) RemoteCacheStore, based on delegating to a CacheServer

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-27?page=com.atlassian.jira.plugin... ] Manik Surtani updated ISPN-27: ------------------------------ Fix Version/s: 4.1.0.BETA1 (was: 4.1.0.ALPHA2) > RemoteCacheStore, based on delegating to a CacheServer > ------------------------------------------------------ > > Key: ISPN-27 > URL: https://jira.jboss.org/jira/browse/ISPN-27 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Reporter: Manik Surtani > Assignee: Mircea Markus > Fix For: 4.1.0.BETA1, 4.1.0.Final > > > RemoteCacheStore should use the custom binary protocol that is capable of failing over and load balancing. If the backend is configured to use distribution, the same consisitent hashing algorithm should be used by the loader to select the cache server instance in a cluster. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-381) See if JGroupsChannelLookup API can be improved

by Brian Stansberry (JIRA)

See if JGroupsChannelLookup API can be improved ----------------------------------------------- Key: ISPN-381 URL: https://jira.jboss.org/jira/browse/ISPN-381 Project: Infinispan Issue Type: Task Components: Configuration Reporter: Brian Stansberry Assignee: Manik Surtani Priority: Minor All you can do is specify a class with a no-arg constructor, which Infinispan instantiates. Then when it asks for the channel, it doesn't provide any params. So it's not configurable. Perhaps the configuration properties should be passed to lookupChannel. I mark this as minor as injecting the Channel is probably a better alternative for use cases that would use this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (ISPN-96) Generate configuration XSD schema and parse configuration XML files

by Vladimir Blagojevic (JIRA)

Generate configuration XSD schema and parse configuration XML files -------------------------------------------------------------------- Key: ISPN-96 URL: https://jira.jboss.org/jira/browse/ISPN-96 Project: Infinispan Issue Type: Task Affects Versions: 4.0.0.ALPHA4 Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 4.0.0.BETA1 Currently we have a hand maintained XSD schema and manual processing/reading of XML configuration documents. If we introduce annotations for configuration elements we could automatically create XSD schema as well as automatically read XML configuration files. The end results is much less maintenance for configuration part of infinispan. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (ISPN-89) Document all configuration options available in XML and the Configuration beans on the wiki

by Manik Surtani (JIRA)

Document all configuration options available in XML and the Configuration beans on the wiki ------------------------------------------------------------------------------------------- Key: ISPN-89 URL: https://jira.jboss.org/jira/browse/ISPN-89 Project: Infinispan Issue Type: Task Components: Configuration Reporter: Manik Surtani Assignee: Galder Zamarreño Fix For: 4.0.0.GA This used to be in the User Guide of JBC, and now since we don't have a User Guide and everything is maintained on the wiki, we need a table on the wiki. Perhaps something that looks like this: http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... Should explain each XML element, attribute, allowed values, default values, and equivalent setter in the Configuration bean. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

3
15
0 / 0

[JBoss JIRA] Created: (ISPN-97) Improve configuration processing and maintenance

by Vladimir Blagojevic (JIRA)

Improve configuration processing and maintenance ------------------------------------------------ Key: ISPN-97 URL: https://jira.jboss.org/jira/browse/ISPN-97 Project: Infinispan Issue Type: Task Affects Versions: 4.0.0.ALPHA4 Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 4.0.0.BETA1 In order to improve configuration processing and maintenance we have to use Java annotations. We could keep all current configuration beans, that is all subclasses of AbstractConfigurationBean but introduce annotation(s) for those beans that would: - annotate each bean setter with a reference to the XML element in question (full path to it - e.g., infinispan/namedCache/cluster/sync) - provide default configuration value - describe human readable documentation for each configuration option in plain english - references to classes to process certain complex elements and others as the need arise. Furthermore we could also: - remove current hand maintained schema - create schema by automated tools given metadata in annotations - create all human readable documentation from these annotations for manuals. wiki etc etc - read all configuration elements from xml configuration files using metadata in annotations thus avoiding "by hand" reading we have now -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (ISPN-304) REST API should not use POST

by Jozef Hartinger (JIRA)

REST API should not use POST ---------------------------- Key: ISPN-304 URL: https://jira.jboss.org/jira/browse/ISPN-304 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 4.0.0.CR2 Reporter: Jozef Hartinger Assignee: Manik Surtani Priority: Optional Fix For: 4.0.0.CR3 Currently, the REST API provided by Infinispan uses POST for creating new resources, for example: POST to /infinispan/rest/data/foo containing "bar" will create a new key-value pair (foo, bar) However, the HTTP spec says that POST should be used for creating *subordinate* resources, which is not done in this case because the resource itself is created and not a subordinate one. Moreover, the RESTful Web Services book which is kind of a bible for writting RESTful applications claims that the POST method can be used for creating resources *only if the server is in charge of choosing the URI for a new resource* (for example if a POST sent to /infinispan/rest/data would cause server to choose a key for the given value and make it available under /infinispan/rest/data/choosenKey). In contrast, if the *client is responsible for creating the URI* (which is the case of Infinispan), the client should use a PUT sent to the chosen URI (PUT /infinispan/rest/data/foo) to create the resource. That means that there is no difference between the initial creation of a resource and a subsequent update (both request are PUT requests to the same URI) - fits exactly how cache.put() works. The downside of this approach is that the client does not get 409 when he/she tries to overwrite an existing value. Nevertheless, if this behavior is really needed, it can be achieved alternatively, for example by introducing a path parameter "overwrite" which if set to "false" and the resource already exists, will cause the server to return 409. To summarize, IMHO it would be cleaner to stop using POST for creating new cache records and use PUT for this purpose instead. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

3
14
0 / 0

[JBoss JIRA] Commented: (ISPN-57) Support Google App Engine

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-57?page=com.atlassian.jira.plugin... ] Manik Surtani commented on ISPN-57: ----------------------------------- Essentially the only way to make this work on GAE (the way things stand with GAE's whitelist right now) would be to seriously cripple Infinispan's functionality. While this is possible (a separate infinispan-gae distro), I don't see much value in this as you would be left with a glorified hashmap. > Support Google App Engine > ------------------------- > > Key: ISPN-57 > URL: https://jira.jboss.org/jira/browse/ISPN-57 > Project: Infinispan > Issue Type: Feature Request > Components: Core API > Reporter: Adrian Cole > Assignee: Manik Surtani > Fix For: 5.1.0.BETA1, 5.1.0.Final > > > Google App Engine for Java is a restricted JVM. It prevents such things as file access and thread creation. Currently, Infinispan requires at least thread creation and depending on the cachestore mechanism, potentially file as well. > This is a container to investigate other related issues that may prevent Infinispan from running on GAE. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
0
0 / 0

[JBoss JIRA] Commented: (ISPN-57) Support Google App Engine

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-57?page=com.atlassian.jira.plugin... ] Manik Surtani commented on ISPN-57: ----------------------------------- Some discussions on the subject: http://lists.jboss.org/pipermail/infinispan-dev/2009-November/001953.html and an email from Vladimir: "I think that we should give up, for the time being, trying to deploy Infinispan in GAE/j. After I have encountered the below mentioned blocker with our regular marshaling I have gone in direction recommended by Galder. I replaced river marshalling with java serialization. Although, java serialization does not really work, as Galder pointed, I wanted to jump over the first hurdle and see how far I can get with deployment. Didn't get very far. After I used java serialization instead of river I got this exception: java.security.AccessControlException: access denied (java.lang.RuntimePermission accessClassInPackage.sun.reflect) at java.security.AccessControlContext.checkPermission(AccessControlContext.java:323) at java.security.AccessController.checkPermission(AccessController.java:546) at java.lang.SecurityManager.checkPermission(SecurityManager.java:532) at com.google.appengine.tools.development.DevAppServerFactory$CustomSecurityManager.checkPermission(DevAppServerFactory.java:151) at java.lang.SecurityManager.checkPackageAccess(SecurityManager.java:1512) at java.lang.ClassLoader$3.run(ClassLoader.java:410) at java.security.AccessController.doPrivileged(Native Method) at java.lang.ClassLoader.checkPackageAccess(ClassLoader.java:408) at org.jboss.marshalling.reflect.SunReflectiveCreator$1.run(SunReflectiveCreator.java:40) at org.jboss.marshalling.reflect.SunReflectiveCreator$1.run(SunReflectiveCreator.java:38) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.marshalling.reflect.SunReflectiveCreator.(SunReflectiveCreator.java:38) at org.infinispan.marshall.jboss.JBossMarshaller.start(JBossMarshaller.java:107) at org.infinispan.marshall.VersionAwareMarshaller.start(VersionAwareMarshaller.java:75) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.google.appengine.tools.development.agent.runtime.Runtime.invoke(Runtime.java:100) at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:170) at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:846) at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:666) at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:572) at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:130) at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:134) at org.infinispan.CacheDelegate.start(CacheDelegate.java:303) at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:394) at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:358) at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:333) at guestbook.SignGuestbookServlet.doPost(SignGuestbookServlet.java:63) " > Support Google App Engine > ------------------------- > > Key: ISPN-57 > URL: https://jira.jboss.org/jira/browse/ISPN-57 > Project: Infinispan > Issue Type: Feature Request > Components: Core API > Reporter: Adrian Cole > Assignee: Manik Surtani > Fix For: 5.1.0.BETA1, 5.1.0.Final > > > Google App Engine for Java is a restricted JVM. It prevents such things as file access and thread creation. Currently, Infinispan requires at least thread creation and depending on the cachestore mechanism, potentially file as well. > This is a container to investigate other related issues that may prevent Infinispan from running on GAE. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2010