Gunnar,
While WF doesn't include infinispan-cdi integration, you can inject
Infinispan caches defined within the Infinispan subsystem as standard
EE resources via the their JNDI bindings. This approach has the
advantage of container-managed lifecycle of the cache, even when
referenced by multiple
Excellent. Thanks a million.
On Tue, Feb 13, 2018 at 8:33 AM, Tristan Tarrant wrote:
> We can cut 9.1.6.Final today.
>
> --
> Tristan Tarrant
> Infinispan Lead & Data Grid Architect
> Red Hat
>
> On 13 Feb 2018 14:21, "Paul Ferraro" wrote:
>>
>
Can one of the devs please review this patch?
https://github.com/infinispan/infinispan/pull/5750
The limit of cache names sizes to 127 bytes is too limiting for
hibernate/JPA 2nd level cache deployments, which generate cache names
using fully qualified class names of entity classes, which are user
rt of a second Infinispan module in
>>> Hibernate 5.x branch.
>>>
>>> 3. Integrate 9.x provider as part of 'hibernate-infinispan' in Hibernate
>>> 5.x branch. This is problematic for since the provider is not backwards
>>> compatible.
>>&g
Thanks Galder. I read through the infinispan-dev thread on the
subject, but I'm not sure what was concluded regarding the eventual
home for this code.
Once the testsuite passes, is the plan to commit to hibernate master?
If so, I will likely fork these changes into a WF module (and adapt it
for Hi
Funny that you mention this, because I need to implement this for
WildFly.next to support Infinispan 9, where the binary key store is no
longer an option. We need to be able to map complex keys for storing
web sessions, Hibernate keys, and @Stateful EJBs to strings.
An auto-discovered mapper is si
Hi Galder,
Sorry for the delay. For server-mode, we'd need to set the
RouteStatusListener in the jgroups subsystem before the RELAY2
protocol is initialized.
e.g.
public class DefaultRouteStatusListener implements
RouteStatusListener, Supplier> {
private final Set view = new ConcurrentSkipLis
ake site-name optional, and default it to the resource name if
undefined.
I've opened https://issues.jboss.org/browse/WFLY-7871
Paul
> Thoughts?
>
> [1]
> https://github.com/galderz/js-client/blob/16c985e0957c10f332c0dc9b561997c3f88c1c24/spec/configs/domain.xml
> --
> Gal
Hi Galder,
The short answer: Attributes that are components of a resource path
address may not contain expressions.
What is the motivation behind ISPN-7326?
When the x-site domain model for Infinispan was originally designed,
the assumption was that a domain controller would never attempt to
man
On Wed, Nov 30, 2016 at 12:41 PM, Tristan Tarrant wrote:
> On 30/11/16 17:44, Paul Ferraro wrote:
>> On Wed, Nov 30, 2016 at 9:13 AM, Tristan Tarrant wrote:
>>> Some additional notes:
>>>
>>> - currently the XSD specifies the default-cache attribute on the
>
t allows switching to the
> old behaviour if needed.
>
> In any case I'd like to also introduce a JCache-like createCache() API
I think it would be best/cleanest if caches created via this API are
anonymous (i.e. not managed by the cache manager or made accessible
via getCache(Stri
+1000
This is precisely how we've setup cache manager semantics in WildFly
(since AS7):
https://github.com/wildfly/wildfly/blob/master/clustering/infinispan/spi/src/main/java/org/wildfly/clustering/infinispan/spi/CacheContainer.java
https://github.com/wildfly/wildfly/blob/master/clustering/infinis
ed directly!
>
> I assume you're upgrading JGroups only on a new major version of Wildfly,
> aren't you? Then, returning a JChannel instead of a Channel shouldn't be an
> issue, should it?
>
>
> On 23/08/16 16:01, Paul Ferraro wrote:
>>
>> Bela,
>>
Bela,
Are you sure you want to drop the Channel interface [1] without any
deprecation? WildFly references the Channel interface in public user
API [1]. I can certainly narrow the type for WF11, but this will
break user applications unexpectedly.
Paul
[1] https://issues.jboss.org/browse/JGRP-20
This also fits nicely with the JCache API, where a CacheProvider is
expected to express a connection to a CacheManager as a URI.
On Mon, May 30, 2016 at 3:46 AM, Tristan Tarrant wrote:
> In the past there has been talk of representing a connection to
> Infinispan using a URL, in particular for Ho
return new
> org.infinispan.jcache.JCacheManager(URI.create("app"), cacheManager,
> Caching.getCachingProvider());
> }
>
> public void dispose(@Disposes @ClusteredCache CacheManager
> jcacheManager) {
> jcacheManager.close();
> }
> }
>
> D
- Original Message -
> From: "Christian Beikov"
> To: infinispan-dev@lists.jboss.org
> Sent: Sunday, August 9, 2015 12:02:13 PM
> Subject: [infinispan-dev] JCache integration with Wildfly provided
> configuration
>
> Hello,
>
> I am using Infinispan 7.2.3.Final within Wildfly 9.0.1 a
- Original Message -
> From: "Sanne Grinovero"
> To: "infinispan -Dev List"
> Sent: Thursday, February 19, 2015 11:46:11 AM
> Subject: [infinispan-dev] Is it time to reduce the complexity of the
> CacheManager?
>
> All,
> at the beginning of time, the expectation was that an applicati
pan-core.jar, it would definitely not send "org.infinispan:main"
> as module:slot, which is what server needs instead.
>
> Tristan
>
>
> On 02/10/14 16:06, Paul Ferraro wrote:
> > The only other obvious alternative of which I can think is to actually
> &g
y importing the one
> > included in the WF's jgroups subsystem, but now he's using his local
> > copy), but now he has run into further problems and I believe what Paul
> > & Dennis have written might be correct.
> >
> > The code that configures this is in
>
r = this.getClass().getClassLoader();
if (loader instanceof ModuleClassLoader) {
Module module = ((ModuleClassLoader) loader).getModule();
builder.serialization().classResolver(ModularClassResolver.getInstance(module.getModuleLoader());
}
Paul
> Tristan
>
> On 29/09/14 18:57, Paul
es do not
use this and therefore cannot make sense of the message body.
Paul
- Original Message -
> From: "Kurt T Stam"
> To: "Stelios Koussouris" , "Radoslav Husar"
>
> Cc: "Galder Zamarreño" , "Paul Ferraro"
> , "
- Original Message -
> From: "Galder Zamarreño"
> To: "infinispan -Dev List" , "Paul Ferraro"
>
> Sent: Monday, September 1, 2014 11:08:45 AM
> Subject: Asynchronous cache's "void put()" call expectations changed from
It seems that the ability to associate a cache with a specific classloader has
been removed in 7.0 by this commit:
https://github.com/infinispan/infinispan/commit/39a21a025db2e0f85019b93d09052b4772abbaa8
I don't fully understand the reason for the removal. WildFly previously relied
on this mecha
As an EE7 application server, WF already requires Java SE 7.
On Wed, 2014-04-09 at 17:30 +0100, Mircea Markus wrote:
> Hi guys,
>
> Hibernate Search 5.0 is moving to Java 7 (besides others, because Lucene 4.8
> does it).
> For us it makes a lot of sense to bring in HSearch 5/Lucene 4 rather soon
Hey guys,
I have created a number of requests for features that I'd like to be
able to leverage for WildFly 9/10. Can the appropriate component owners
(which I think is Dan in all cases) comment on the following issues?
The following issues prevent WF from leveraging Infinispan expiration:
* Exp
On Wed, 2014-03-12 at 18:45 +0100, Galder Zamarreño wrote:
> On 05 Mar 2014, at 18:16, Mircea Markus wrote:
>
> > Sanne came with a good follow up to this email, just some small
> > clarifications:
> >
> > On Mar 4, 2014, at 6:02 PM, Emmanuel Bernard wrote:
> >
> If you have to do a map
What was the read/write ratio used for this test?
On Fri, 2014-01-17 at 14:06 +0100, Radim Vansa wrote:
> Hi Mircea,
>
> I've ran a simple stress test [1] in dist mode with store as binary (not
> enabled, enabled keys only, enabled values only, enabled both).
> The difference is < 2 % (with stor
FYI:
https://issues.jboss.org/browse/WFLY-2829
https://github.com/wildfly/wildfly/pull/5808
On Wed, 2014-01-29 at 08:42 -0500, Paul Ferraro wrote:
> Ooops. That's a bug - I'll submit a PR momentarily.
>
> On Wed, 2014-01-29 at 13:08 +0100, Ales Justin wrote:
> > I
Ooops. That's a bug - I'll submit a PR momentarily.
On Wed, 2014-01-29 at 13:08 +0100, Ales Justin wrote:
> I'm looking at current WildFly integration.
>
> In CacheAdd I see this code:
>
> if ((lockingMode == LockingMode.OPTIMISTIC) && (isolationLevel ==
> IsolationLevel.REPEATABLE_REA
Excellent.
I think this will do in the short term, but in the long term, I think we
need to revisit some of the finer points of the cache manager lifecycle,
especially within the context of Wildfly/EAP.
In Wildfly/EAP, 2 deployment thread can easily trigger a case where a
cache manager is restart
On Fri, 2013-11-08 at 15:28 +, Mircea Markus wrote:
> Hey guys,
>
> Several things were discussed lately([1],[2],[3],[4]) around our transaction
> support. Here's some some thoughts I have around re-modeling transactions for
> 7.0:
>
> 1. Async options for commit/rollback
> - they don't rea
I'm fine with removing this. Thanks for the heads up.
On Tue, 2013-09-17 at 17:53 +0200, Galder Zamarreño wrote:
> Hi,
>
> Cache.compact() method is being removed in Infinispan 6.0 [1].
>
> I've suggested deprecating but Mircea thinks it should be removed altogether.
> This might cause compil
On Wed, 2013-05-22 at 18:03 +0200, Galder Zamarreño wrote:
> On May 21, 2013, at 7:42 PM, Paul Ferraro wrote:
>
> > On Tue, 2013-05-21 at 17:07 +0200, Galder Zamarreño wrote:
> >> On May 6, 2013, at 2:20 PM, Mircea Markus wrote:
> >>
> >>>
> &g
On Tue, 2013-05-21 at 17:07 +0200, Galder Zamarreño wrote:
> On May 6, 2013, at 2:20 PM, Mircea Markus wrote:
>
> >
> > On 3 May 2013, at 20:15, Paul Ferraro wrote:
> >
> >> Is it essential? No - but it would simplify things on my end.
> >>
about 2x
> >> more writes as it is the lock owner for all locks in replicated mode)
> >> that makes
> >>
> >> Paul, how many operations within transaction do you use? The results above
> >> are from single operation (put/get) per transaction (we have i
Is it essential? No - but it would simplify things on my end.
If Infinispan can't implement expiration notifications, then I am forced
to use immortal cache entries and perform expiration myself. To do
this, I have to store meta information about the cache entry along with
my actual cache values,
Damn you, bugzilla!!!
Attached.
On Wed, 2013-05-01 at 11:05 -0400, Paul Ferraro wrote:
> FYI - here's a summary of EAP 6.0 vs 6.1 performance:
> https://bugzilla.redhat.com/attachment.cgi?id=741896
>
> and here's the relevant BZ:
> https://bugzilla.redhat.com/show_bug.
FYI - here's a summary of EAP 6.0 vs 6.1 performance:
https://bugzilla.redhat.com/attachment.cgi?id=741896
and here's the relevant BZ:
https://bugzilla.redhat.com/show_bug.cgi?id=956988
On Wed, 2013-05-01 at 15:55 +0100, Mircea Markus wrote:
> Hi Martin,
>
> Paul mentioned a severe degradation i
I haven't looked into this yet - still focused on EAP 6.0.1 issues.
I'll create a branch for the 5.2 upgrade today.
On Wed, 2012-07-25 at 13:42 +0200, Ales Justin wrote:
> Paul / Richard, any update?
>
> As I need this in, in order to finally release first version of CapeDwarf.
>
> -Ales
>
> >
On Fri, 2012-05-11 at 10:24 +0200, Ales Justin wrote:
> > The details of the query module are a little out of my realm of
> > experience. I'm CC'ing infinispan-dev, to open up the larger discussion
> > to classloading and compatibility with modular environments.
> >
> > Off the top of my head, it
The details of the query module are a little out of my realm of
experience. I'm CC'ing infinispan-dev, to open up the larger discussion
to classloading and compatibility with modular environments.
Off the top of my head, it seems like you need a custom
KeyTransformationHandler that can resolve cl
gt; Re: https://issues.jboss.org/browse/ISPN-2029
>
> Just a heads up as a result of an interesting discussion with Paul Ferraro
> last night:
>
> So far Externalizer interface has extended Serializable and last night I was
> trying to wonder why that was.
>
> As you guys might reme
- Original Message -
> From: "David M. Lloyd"
> To: "infinispan -Dev List"
> Cc: hibernate-...@lists.jboss.org, "jboss-as7-...@lists.jboss.org
> Development" ,
> "Galder Zamarreño"
> Sent: Tuesday, March 6, 2012 2:55:18 PM
> Subject: Re: [infinispan-dev] [jboss-as7-dev] AS7-4007 missing
larClassResolver to marshal/unmarshal
session objects.
> >
> > On Mar 6, 2012, at 8:19 PM, Galder Zamarreño wrote:
> >
> >>
> >> On Mar 6, 2012, at 8:06 PM, David M. Lloyd wrote:
> >>
> >>> On 03/06/2012 01:02 PM, Galder Zamarreño wrote:
&
arreño wrote:
>
> >
> > On Mar 6, 2012, at 8:06 PM, David M. Lloyd wrote:
> >
> >> On 03/06/2012 01:02 PM, Galder Zamarreño wrote:
> >>> On Mar 6, 2012, at 6:31 PM, Paul Ferraro wrote:
> >>>
> >>>> To work around this,
- Original Message -
> From: "Galder Zamarreño"
> To: "Paul Ferraro"
> Cc: "Jason T. Greene" , "Bela Ban"
> , "infinispan -Dev List"
> , hibernate-...@lists.jboss.org,
> "jboss-as7-...@lists.jboss.org Dev
- Original Message -
> From: "Jason T. Greene"
> To: "David M. Lloyd"
> Cc: "Galder Zamarreño" , "Paul Ferraro"
> , "Bela Ban" ,
> "infinispan -Dev List" ,
> hibernate-...@lists.jboss.org,
> "
On Thu, 2012-02-09 at 15:52 +, Sanne Grinovero wrote:
> On 9 February 2012 15:37, Bela Ban wrote:
> >
> >
> > On 2/9/12 3:24 PM, Sanne Grinovero wrote:
> >> On 9 February 2012 14:09, Bela Ban wrote:
> >>>
> >>>
> >>> On 2/9/12 3:01 PM, Dan Berindei wrote:
> On Thu, Feb 9, 2012 at 2:45 PM
On Wed, 2012-02-08 at 14:14 +0100, Galder Zamarreño wrote:
> On Feb 8, 2012, at 11:27 AM, Sanne Grinovero wrote:
>
> > On 8 February 2012 04:14, Scott Marlow wrote:
> >> On 02/07/2012 10:25 AM, Sanne Grinovero wrote:
> >>>
> >>> On 7 February 2012 15:21, Scott Marlow wrote:
>
> On 02
2012, at 23:20, Manik Surtani wrote:
>
>
>
> >
> > On 28 Jan 2012, at 19:33, Paul Ferraro wrote:
> >
> > > It would be nice to see those few minor issues that I raised
> > > post-FINAL,
> > > specifically the xsd update and removing some o
On Thu, 2012-01-26 at 22:42 +, Manik Surtani wrote:
> I really didn't want to do this, but it looks like a 5.1.1 will be
> necessary. The biggest (critical, IMO, for 5.1.1) issues I see are:
>
>
> 1. https://issues.jboss.org/browse/ISPN-1786 - I presume this has to
> do with a bug Mircea spo
While migrating the Infinispan AS7 subsystem to use the new
configuration API, I've run into a couple of issues in the form of
feature requests for 5.1.0.CR3:
1. A method to retrieve the
org.infinispan.configuration.cache.Configuration from the cache manager
without starting it's respective cache.
>
> I'll try to run with REPL_ASYNC to see if it changes anything, but I
> don't think it should.
>
> Cheers
> Dan
>
>
> On Fri, Oct 14, 2011 at 1:27 AM, Paul Ferraro wrote:
> > Hey all,
> >
> > I'm a bit stuck with the Infinispan 5.1 u
Hey all,
I'm a bit stuck with the Infinispan 5.1 upgrade in AS 7.1.
I've tried both with BETA1 and a SNAPSHOT build from today.
When a deployment forces a cache to start, I see the following
stacktrace:
14:06:07,584 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8)
MSC1: Failed to
- Original Message -
> From: "Tristan Tarrant"
> To: infinispan-dev@lists.jboss.org
> Sent: Friday, September 16, 2011 4:07:23 AM
> Subject: Re: [infinispan-dev] Request for feedback on cache store support in
> AS7 Infinispan subsystem
> On 09/16/2011 09:56 AM, Sanne Grinovero wrote:
> >
- Original Message -
> From: "Galder Zamarreño"
> To: "infinispan -Dev List"
> Sent: Friday, September 16, 2011 3:49:32 AM
> Subject: Re: [infinispan-dev] Request for feedback on cache store support in
> AS7 Infinispan subsystem
> On Sep 15
- Original Message -
> From: "Tristan Tarrant"
> To: infinispan-dev@lists.jboss.org
> Sent: Thursday, September 15, 2011 12:18:59 PM
> Subject: Re: [infinispan-dev] Request for feedback on cache store support in
> AS7 Infinispan subsystem
> On 09/15/2011
Hi all,
In AS 7.0, only the those cache store implementations packaged in
infinispan-core were usable by default. While the Infinispan subsystem
schema allowed users to use any cache store implementation (via ), they need to manually add the relevant jars to the
org.infinispan module, and update
FYI:
https://issues.jboss.org/browse/AS7-1713
https://issues.jboss.org/browse/AS7-1714
I'll resolve AS7-1713 today.
On Fri, 2011-09-02 at 12:19 +0200, Galder Zamarreño wrote:
> On Sep 1, 2011, at 4:31 PM, Paul Ferraro wrote:
>
> > On Thu, 2011-09-01 at 13:12 +0200, Galde
On Fri, 2011-09-02 at 12:19 +0200, Galder Zamarreño wrote:
> On Sep 1, 2011, at 4:31 PM, Paul Ferraro wrote:
>
> > On Thu, 2011-09-01 at 13:12 +0200, Galder Zamarreño wrote:
> >> Hey Paul,
> >>
> >> As shown by Martin in https://issues.jboss.org/browse/JBPA
On Thu, 2011-09-01 at 13:12 +0200, Galder Zamarreño wrote:
> Hey Paul,
>
> As shown by Martin in https://issues.jboss.org/browse/JBPAPP-6718 , it's
> clear that the AS7 Infinispan subsystem is not yet ready to read
> configurations for stores other than the FileCacheStore, so I'd assume we'd
>
On Wed, 2011-06-01 at 16:46 +0200, Bela Ban wrote:
>
> On 6/1/11 4:21 PM, Sanne Grinovero wrote:
> > Hi Bela,
> >
> > 2011/6/1 Bela Ban:
> >> We currently use JGroups' partial state transfer to transfer individual
> >> caches from one Infinispan instance to another.
> >>
> >> Since I got rid of pa
was an
> > > > oversight and not intended to be removed.
> > > >
> > > > Erik
> > > >
> > > > -Original Message-
> > > > From: infinispan-dev-boun...@lists.jboss.org
> > > > [mailto:infinispan-dev-boun...@l
it was an oversight. I agree that it should have been deprecated and
> removed in Infinispan 6.0.
>
> I've created a JIRA to restore it and mark it as deprecated:
> https://issues.jboss.org/browse/ISPN-953
>
> On Feb 23, 2011, at 6:00 PM, Paul Ferraro wrote:
>
>
>
> On 11-02-23 11:18 AM, Paul Ferraro wrote:
> > After testing AS6 with Infinispan 4.2.1.CR3, I started seeing a slew of
> > testsuite failures all due to state transfer timeouts. These are
> > REPL_SYNC tests, with state transfer enab
In my course of upgrading AS6 from 4.2.0.Final to 4.2.1.CR3, I came
across a NoSuchMethodError. Specifically, a couple AS components
utilize DistributionManager.isLocal(String), which was dropped from the
public API sometime after 4.2.1.CR1.
While the fix is trivial enough (in the end I'll need t
After testing AS6 with Infinispan 4.2.1.CR3, I started seeing a slew of
testsuite failures all due to state transfer timeouts. These are
REPL_SYNC tests, with state transfer enabled:
e.g.
2011-02-23 10:59:46,771 DEBUG
[org.infinispan.statetransfer.StateTransferManagerImpl] Initiating state
tran
;: don't we support ATTRIBUTE granularity anymore ? And if
> so, why wouldn't we fall back to ATTRIBUTE granularity ?
>
>
>
>
>
> On 12/14/10 7:38 PM, Paul Ferraro wrote:
> > http://community.jboss.org/wiki/InfinispanIntegrationinAS6
> >
http://community.jboss.org/wiki/InfinispanIntegrationinAS6
Any feedback is appreciated.
Thanks,
Paul
___
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
70 matches
Mail list logo
