[JBoss JIRA] Created: (JBBUILD-352) VFS tests fail under mvn
by Scott M Stark (JIRA)
VFS tests fail under mvn
------------------------
Key: JBBUILD-352
URL: http://jira.jboss.com/jira/browse/JBBUILD-352
Project: JBoss Build System
Issue Type: Bug
Components: Maven
Reporter: Scott M Stark
Assigned To: Paul Gier
When doing the vfs project build, many tests are failing because the java.protocol.handler.pkgs is not seeing the org.jboss.virtual.protocol package. This is present in the project pom.xml maven-surefire-plugin section though:
<systemProperties>
<property>
<name>java.protocol.handler.pkgs</name>
<value>org.jboss.virtual.protocol</value>
</property>
</systemProperties>
These tests run fine without any system property settings under eclipse.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Commented: (JBCACHE-562) Disable cache loader when no cacheloader class is specified
by Manik Surtani (JIRA)
[ http://jira.jboss.com/jira/browse/JBCACHE-562?page=comments#action_12357643 ]
Manik Surtani commented on JBCACHE-562:
---------------------------------------
Is this still important? I vote that we don't attempt to inject behaviour based on an empty class name. If you want to disable cache loaders, simply comment out the relevant block in XML or don't set a CacheLoaderConfig in the Configuration object.
> Disable cache loader when no cacheloader class is specified
> -----------------------------------------------------------
>
> Key: JBCACHE-562
> URL: http://jira.jboss.com/jira/browse/JBCACHE-562
> Project: JBoss Cache
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Ben Wang
> Assigned To: Manik Surtani
> Priority: Minor
> Fix For: 2.0.0.GA
>
>
> In 1.3, we support a new form of cacheloader config. However, it is incovenient to disable the cache loader (previously all we need is to specify cacheloaderclass to empty). We should also support this kind of semantics so we can disable it easily. I propose when do createcacheloader, we also check whether the class name is there or not to decide whether to go ahead. If not, we simply log an info message.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Closed: (JBCACHE-131) Cache Loaders (when unshared, and not used with eviction) Should Persist Transient State Upon Startup
by Manik Surtani (JIRA)
[ http://jira.jboss.com/jira/browse/JBCACHE-131?page=all ]
Manik Surtani closed JBCACHE-131.
---------------------------------
Resolution: Rejected
> Cache Loaders (when unshared, and not used with eviction) Should Persist Transient State Upon Startup
> -----------------------------------------------------------------------------------------------------
>
> Key: JBCACHE-131
> URL: http://jira.jboss.com/jira/browse/JBCACHE-131
> Project: JBoss Cache
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 1.2.2
> Reporter: James Wilson
> Assigned To: Manik Surtani
> Priority: Minor
> Fix For: 2.0.0.GA
>
> Attachments: TreeCache.zip
>
>
> Given the following single, unshared cache loader use case in the TreeCache documentation:
> "This is a similar case as the previous one, but here only one node in the cluster interacts with a backend store via its CacheLoader. All other nodes perform in-memory replication. A use case for this is HTTP session replication, where all nodes replicate sessions in-memory, and - in addition - one node saves the sessions to a persistent backend store"
> A cache with attached cache loader should persist the transient state of the cache to disk upon startup in order to maintain cache recoverability.
> I have modified TreeCache to handle this situation, and I will attach the modified code to this issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Closed: (JBCACHE-250) Hierarchical caches not working when using JBoss service
by Manik Surtani (JIRA)
[ http://jira.jboss.com/jira/browse/JBCACHE-250?page=all ]
Manik Surtani closed JBCACHE-250.
---------------------------------
Resolution: Out of Date
could you pls try with a more recent version.
> Hierarchical caches not working when using JBoss service
> --------------------------------------------------------
>
> Key: JBCACHE-250
> URL: http://jira.jboss.com/jira/browse/JBCACHE-250
> Project: JBoss Cache
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.2.3
> Reporter: Nimrod Rivier
> Assigned To: Manik Surtani
> Priority: Minor
> Fix For: 2.0.0.GA
>
>
>
> I tried to configure a hierarchical cache, composed of a first-level memory-only cache,
> and a second-level file-only cache. It seems not to work when I the caches are jboss services,
> but works when I use plain classes.
> Details:
> The caches are created as follows:
> TreeCacheMBean sCacheSecondLevel = (TreeCacheMBean)MBeanProxyExt.create(TreeCacheMBean.class, serviceName1, server);
> TreeCacheMBean sCacheFirstLevel = (TreeCacheMBean)MBeanProxyExt.create(TreeCacheMBean.class, serviceName2, server);
> LocalDelegatingCacheLoader sCacheLoader = new LocalDelegatingCacheLoader(sCacheSecondLevel.getInstance());
> sCacheFirstLevel.setCacheLoader(sCacheLoader);
> I then insert elements into sCacheFirstLevel, and it seems they are not delegated into sCacheSecondLevel .
> Adding the following did not help
> sCacheFirstLevel.stopService();
> sCacheFirstLevel.startService();
> sCacheSecondLevel.stopService();
> sCacheSecondLevel.startService();
> When I use the following code to create the caches, everything seems to work fine:
> sCacheSecondLevel = new TreeCache();
> sCacheSecondLevel.setCacheLoaderClass"org.jboss.cache.loader.FileCacheLoader");
> Properties filecacheLoaderProperties = new Properties();
> filecacheLoaderProperties.put("location","c:\\temp\\cache\\requests");
> sCacheSecondLevel.setCacheLoaderConfig(filecacheLoaderProperties);
> sCacheFirstLevel = new TreeCache();
> CacheLoader cacheLoader = new LocalDelegatingCacheLoader (sCacheSecondLevel);
> sCacheFirstLevel.setCacheLoader(cacheLoader);
> /* Configure the caches (removed) */
> sCacheSecondLevel.createService();
> sCacheSecondLevel.startService();
> sCacheFirstLevel.createService();
> sCacheFirstLevel.startService();
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Commented: (JBCACHE-131) Cache Loaders (when unshared, and not used with eviction) Should Persist Transient State Upon Startup
by Manik Surtani (JIRA)
[ http://jira.jboss.com/jira/browse/JBCACHE-131?page=comments#action_12357641 ]
Manik Surtani commented on JBCACHE-131:
---------------------------------------
The new SingletonCacheLoader delegate should take care of this now.
> Cache Loaders (when unshared, and not used with eviction) Should Persist Transient State Upon Startup
> -----------------------------------------------------------------------------------------------------
>
> Key: JBCACHE-131
> URL: http://jira.jboss.com/jira/browse/JBCACHE-131
> Project: JBoss Cache
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 1.2.2
> Reporter: James Wilson
> Assigned To: Manik Surtani
> Priority: Minor
> Fix For: 2.0.0.GA
>
> Attachments: TreeCache.zip
>
>
> Given the following single, unshared cache loader use case in the TreeCache documentation:
> "This is a similar case as the previous one, but here only one node in the cluster interacts with a backend store via its CacheLoader. All other nodes perform in-memory replication. A use case for this is HTTP session replication, where all nodes replicate sessions in-memory, and - in addition - one node saves the sessions to a persistent backend store"
> A cache with attached cache loader should persist the transient state of the cache to disk upon startup in order to maintain cache recoverability.
> I have modified TreeCache to handle this situation, and I will attach the modified code to this issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Closed: (JBCACHE-469) JGroups Channel reference to be obtained from a factory
by Manik Surtani (JIRA)
[ http://jira.jboss.com/jira/browse/JBCACHE-469?page=all ]
Manik Surtani closed JBCACHE-469.
---------------------------------
Resolution: Won't Fix
Another factory is overkill here. We already have a code block that looks for a MUX factory and attempts to do that; failing which it creates a channel directly.
> JGroups Channel reference to be obtained from a factory
> -------------------------------------------------------
>
> Key: JBCACHE-469
> URL: http://jira.jboss.com/jira/browse/JBCACHE-469
> Project: JBoss Cache
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 1.2.4
> Reporter: Manik Surtani
> Assigned To: Manik Surtani
> Fix For: 2.0.0.GA
>
>
> The JChannelFactory (will be available in JGroups 2.3 - see JGRP-112) should be used to get a channel instance.
> The JChannelFactory could be obtained by:
> 1) MBeanServer lookup (look up a JChannelFactoryMBean instance)
> JBossCache config will need:
> + JChannelFactoryMBean name
> + JGroups configured stack name
> JBossCache config will not need:
> - Cluster name
> - JGroups settings
> 2) JChannelFactory instantiation
> JBossCache config will need:
> + Cluster name
> + JGroups settings
> JBossCache config will not need:
> - JChannelFactoryMBean name
> - JGroups configured stack name
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months