Configuration visitor - Re: [JBoss JIRA] Commented: (ISPN-145) No transport and singleton store enabled should not be allowed
                                
                                
                                
                                    
                                        by Vladimir Blagojevic
                                    
                                
                                
                                        Hi,
Galder and I talked about this offline. Time to involve you guys!
I just completed visitor pattern for our configuration objects. Visitor 
is passed from root of configuration - InfinispanConfiguration object. 
InfinispanConfiguration class has a new method:
public void accept(ConfigurationBeanVisitor v)
How do we want to integrate this visitor into existing structure?
1) We add a new factory method to InfinispanConfiguration with 
additional ConfigurationBeanVisitor parameter
2) We leave everything as is and if there is a need to pass some visitor 
we pass it to InfinispanConfiguration instance directly (from 
DefaultCacheManager)
DefaultCacheManager will pass ValidationVisitor to 
InfinispanConfiguration that will verify configuration semantically.
Regards,
Vladimir
On 09-09-09 10:19 AM, Galder Zamarreno wrote:
> Good idea :)
>
> On 09/09/2009 04:13 PM, Vladimir Blagojevic wrote:
>> Yeah,
>>
>> I was thinking that we can make a visitor for configuration tree and
>> then you can do verification of any node and other things as well. Use
>> cases will come up in the future for sure.
>>
>> Cheers
>>
>>
>>
>> On 09-09-09 3:29 AM, Galder Zamarreno (JIRA) wrote:
>>> [
>>> https://jira.jboss.org/jira/browse/ISPN-145?page=com.atlassian.jira.plugi... 
>>>
>>> ]
>>>
>>> Galder Zamarreno commented on ISPN-145:
>>> ---------------------------------------
>>>
>>> Not sure I understand what you mean by generic though. You mean any
>>> component to have a validation step of some sort?
>>>
>>> Thanks for taking this on :)
>>>
>>>> No transport and singleton store enabled should not be allowed
>>>> --------------------------------------------------------------
>>>>
>>>> Key: ISPN-145
>>>> URL: https://jira.jboss.org/jira/browse/ISPN-145
>>>> Project: Infinispan
>>>> Issue Type: Bug
>>>> Components: Loaders and Stores
>>>> Affects Versions: 4.0.0.ALPHA6
>>>> Reporter: Galder Zamarreno
>>>> Assignee: Vladimir Blagojevic
>>>> Priority: Minor
>>>> Fix For: 4.0.0.CR1
>>>>
>>>>
>>>> Throw configuration exception if singleton store configured without
>>>> transport having been configured.
>>>> It makes no sense to have singleton store enabled when there's no
>>>> transport.
>>
>
                                
                         
                        
                                
                                14 years, 1 month
                        
                        
                 
         
 
        
            
        
        
        
                
                        
                        
                                
                                
                                        
                                                
                                        
                                        
                                        Using Coverity scan?
                                
                                
                                
                                    
                                        by Sanne Grinovero
                                    
                                
                                
                                        Hello,
Did you consider enabling Infinispan to be monitored by coverity's
code analysis services? They are free for OSS projects, I saw a demo
recently and was quite amazed. It's similar to FindBugs, but not only
about static code checks. They checkout your code from trunk and then
run several analysis on it periodically, one of them is about dynamic
thread behavior to predict deadlocks or missing fences instrumenting
the code, and produce nice public reports; AFAIK you don't need to
setup anything yourself, besides getting in touch to ask for it.
It's only available for C and Java code, and they have an impressive
list of OSS projects in the C world (linux kernel, httpd server,
samba, gnome, GCC, PostgreSQL, ...) but not much on Java.
http://scan.coverity.com/
No, I'm not affiliated :-) Just thinking that it might be useful to
have if it's not too hard to setup.
Cheers,
Sanne
                                
                         
                        
                                
                                14 years, 10 months
                        
                        
                 
         
 
        
            
        
        
        
                
                        
                        
                                
                                
                                        
                                                
                                        
                                        
                                        Re: [infinispan-dev] Codename for 5.0
                                
                                
                                
                                    
                                        by galder@jboss.org
                                    
                                
                                
                                        My nomination: Pagoa
- Type of tree in Basque
- Name of a Basque beer
----- "Manik Surtani" <manik(a)jboss.org> wrote:
> As we march on with Infinispan releases, we need a new codename for
> 5.0.  The big new features in 5.0 include a JPA-like API and natural
> language querying.
> 
> Infinispan 4.0 was codenamed "Starobrno" and 4.1 is "Radegast" ...
> what will 5.0 be?
> 
> Some suggestions from the last round of naming are:
> 
> * Macunaima
> * Drak
> 
> Any others?  Once we have a list of nominations I'll set up a poll for
> people to vote.  :)
> 
> Cheers
> Manik
> --
> Manik Surtani
> manik(a)jboss.org
> Lead, Infinispan
> Lead, JBoss Cache
> http://www.infinispan.org
> http://www.jbosscache.org
> 
> 
> 
> 
> 
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
                                
                         
                        
                                
                                15 years, 4 months
                        
                        
                 
         
 
        
            
        
        
        
                
                        
                        
                                
                                
                                        
                                                
                                        
                                        
                                        CR1, BETA2 and Branching trunk
                                
                                
                                
                                    
                                        by Manik Surtani
                                    
                                
                                
                                        Guys, 
So we've decided to release Radegast BETA2 tomorrow rather than CR1, as it gives folks more time to feed back stuff.  Hopefully there won't be any work done on Radegast between BETA2 and CR1 except fixing issues people may report.
And for this purpose, I propose branching trunk to a 4.1 branch, after we tag BETA2:
	http://anonsvn.jboss.org/repos/infinispan/branches/4.1.x
This way trunk can contain the 5.0 codebase, and people can start working on 5.0 features.
Thoughts, opinions?
Cheers,
Manik
--
Manik Surtani
manik(a)jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org
                                
                         
                        
                                
                                15 years, 5 months
                        
                        
                 
         
 
        
            
        
        
        
                
                        
                        
                                
                                
                                        
                                                
                                        
                                        
                                        Rehashing on leave
                                
                                
                                
                                    
                                        by Vladimir Blagojevic
                                    
                                
                                
                                        Hey,
Our rehashing tasks assume that only one member at the time can leave (DistributionManagerImpl#rehash) between the subsequent views. JGroups does not enforce this model - i.e multiple members can leave/crash between subsequent views. Unless there is some disconnect that I am not aware of we have to handle multiple leaves/crashes in rehash.
Vladimir
                                
                         
                        
                                
                                15 years, 5 months
                        
                        
                 
         
 
        
            
        
        
        
                
                        
                        
                                
                                
                                        
                                                
                                        
                                        
                                        Infinispan 4.1Beta2 released
                                
                                
                                
                                    
                                        by Mircea Markus
                                    
                                
                                
                                        Hi,
4.1Beta2 has been released. It contains several fixes[1] and new features:
- an key affinity service that generates keys to be distributed to specific nodes
- RemoteCacheStore that allow an Infinspan cluster to be used as an remote data store
Enjoy!
Mircea
[1] http://tinyurl.com/34p5brd
                                
                         
                        
                                
                                15 years, 5 months
                        
                        
                 
         
 
        
            
        
        
        
                
                        
                        
                                
                                
                                        
                                                
                                        
                                        
                                        Codename for 5.0
                                
                                
                                
                                    
                                        by Manik Surtani
                                    
                                
                                
                                        As we march on with Infinispan releases, we need a new codename for 5.0.  The big new features in 5.0 include a JPA-like API and natural language querying.
Infinispan 4.0 was codenamed "Starobrno" and 4.1 is "Radegast" ... what will 5.0 be?
Some suggestions from the last round of naming are:
* Macunaima
* Drak
Any others?  Once we have a list of nominations I'll set up a poll for people to vote.  :)
Cheers
Manik
--
Manik Surtani
manik(a)jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org
                                
                         
                        
                                
                                15 years, 5 months
                        
                        
                 
         
 
        
            
        
        
        
                
                        
                                
                                
                                        
                                
                         
                        
                                
                                
                                        
                                                
                                        
                                        
                                        mvn -X deploy -Pdistribution -Dmaven.test.skip.exec=true
                                
                                
                                
                                    
                                        by Mircea Markus
                                    
                                
                                
                                        While running the above, I constantly get this error above at various upload steps. 
Whenever I run it again it starts from scratch with all the uploads, as checksums do not match:
<logs>
[INFO] [deploy:deploy {execution: default-deploy}]
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
[DEBUG] not adding permissions to wagon connection
Uploading: https://repository.jboss.org/nexus/service/local/staging/deploy/maven2//o...
[DEBUG] https://repository.jboss.org/nexus/service/local/staging/deploy/maven2//o... - Status code: 201
12K uploaded  (infinispan-4.1.0.BETA2.pom)
[INFO] Retrieving previous metadata from jboss-releases
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
[DEBUG] Connecting to repository: 'jboss-releases' with url: 'https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/'.
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'f426d1b75e0827700f5bd57c5072228cba2c6579'; remote = '5dcb83759097da44e543d72192e183796027d1fb' - RETRYING
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'f426d1b75e0827700f5bd57c5072228cba2c6579'; remote = '5dcb83759097da44e543d72192e183796027d1fb' - IGNORING
</logs>
are there any way in which I can resume the process form where it failed, perhaps by skipping checksum check?
It's the 4th time I'm trying this an it gets really annoying.
Cheers,
Mircea
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
[DEBUG] not adding permissions to wagon connection
Uploading: https://repository.jboss.org/nexus/service/local/staging/deploy/maven2//o...
[DEBUG] https://repository.jboss.org/nexus/service/local/staging/deploy/maven2//o... - Status code: 502
[DEBUG] Failed to transfer file: https://repository.jboss.org/nexus/service/local/staging/deploy/maven2//o.... Return code is: 502
org.apache.maven.wagon.TransferFailedException: Failed to transfer file: https://repository.jboss.org/nexus/service/local/staging/deploy/maven2//o.... Return code is: 502
	at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:368)
	at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:280)
	at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:262)
	at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:172)
	at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107)
	at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:190)
	at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
	at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
	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 org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
	at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
	at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
	at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error deploying artifact: Failed to transfer file: https://repository.jboss.org/nexus/service/local/staging/deploy/maven2//o.... Return code is: 502
                                
                         
                        
                                
                                15 years, 5 months
                        
                        
                 
         
 
        
            
        
        
        
                
                        
                        
                                
                                
                                        
                                                
                                        
                                        
                                        Wicket & Jetty Clustering
                                
                                
                                
                                    
                                        by Philippe Van Dyck
                                    
                                
                                
                                        Hi all,
I have written a couple of infinispan clustering helpers for Jetty (a
session manager) and Wicket (a page store).
If you want it, where am I supposed to commit them ? (As usual, it is crude
undocumented code )
Also, any idea about the schedule of the next alpha release ?
Cheers,
phil
                                
                         
                        
                                
                                15 years, 5 months
                        
                        
                 
         
 
        
            
        
        
        
                
                        
                        
                                
                                
                                        
                                                
                                        
                                        
                                        Handling Application specific objects
                                
                                
                                
                                    
                                        by kapil nayar
                                    
                                
                                
                                        Hi
In JBossCache APIs, there is a requirement to register the application
classloader with the cache in order for the applications at the two ends of
replication to identify the application specific objects.
Do we have a similar requirement when using Infinispan?
I didn't see any specific APIs which would do this.
Thanks,
Kapil
                                
                         
                        
                                
                                15 years, 5 months