Tree cache listeners
by Galder Zamarreño
Hi all,
Re: https://issues.jboss.org/browse/ISPN-1935
I don't see an easy solution for this. See test in https://github.com/galderz/infinispan/blob/t_1935_m/tree/src/test/java/or...
The problem is the cache.put() from where the cache entry modified event is thrown comes from when the AtomicHashMap is created, which at that point is empty.
Once the AHM is created, we then modify the map which does not generate any events, it just generates the deltas.
Finally, when the operation is completed, a prepare replicates the actual deltas in the cluster (not in the test, but in a clustered test).
But a user can't listen for @TransactionCompleted and expect to see the list of modifications.
Any other ideas?
Cheers,
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
13 years, 6 months
Very confusing L1 cache configuration defaults
by Michal Linhard
Hi,
when I was trying to figure out what is the L1 default configuration
The JDG default: DISABLED
when there is no l1-lifespan attribute in the element <distributed-cache
/>, L1 is disabled.
The Infinispan default: DISABLED
when there is no <l1/> element under <clustering/> element, or the <l1/>
element is empty, L1 is disabled.
However the hardwired default in the code is different:
https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o...
the enabled field is set to true.
this also means that L1ConfigurationBuilder prints a debug message: " L1
is enabled and L1OnRehash was not defined, enabling it" even though L1
won't be enabled in the end.
The L1 is disabled because of the "activated" attribute.
All I need to change is one attribute of L1Configuration (even unrelated
to enablement) to "activate" it and it becomes enabled.
I don't know what is the purpose of the "activated" attribute, it seems
to be there for LegacyConfigurationAdaptor's purposes.
But when we get rid of it we might make L1 by default enabled (by mistake)
What's the desired default ?
IMO L1 should be disabled by default, because without proper eviction
settings, user can't very much control what's in each node's memory. And
in general the performance tests don't show it performs better.
Shouldn't we sync these ?
Either set enabled = false in L1ConfigurationBuilder or allow enablement
by default.
m.
--
Michal Linhard
Quality Assurance Engineer
JBoss Datagrid
Red Hat Czech s.r.o.
Purkynova 99 612 45 Brno, Czech Republic
phone: +420 532 294 320 ext. 62320
mobile: +420 728 626 363
13 years, 6 months
Query: inconsistencies with putAll
by Sanne Grinovero
Hi all,
I was adding some tests for Query as I just found many basic
operations are uncovered, and found an annoying issue.
When using
cache.putAll(values);
the Query interceptor will iterate on each entry, transform each entry
key and replace those entry keys in string form with the new indexed
values.
The problem is *which index* : the index mapping information is bound
to the indexed type. So the normal put/replace/remove operations
actually rely on the return value to know where to direct the proper
index operation (to which index) - if any.
With putAll() returning void, I don't have the return values.
I could hack this to "unroll" in several individual put() operations
but I don't think that should happen in an interceptor. Also this
would defeat the purpose of using putAll, killing it's efficiency over
using several put operations.
I would generally expect people to put objects of the same type when
replacing a key.. so this works fine usually looking at the runtime
type of the new value (as it's doing), but it's not correct generally.
Worse, I can't detect the mismatch and log some warning.
Any suggestion? I'm tempted to say I need to retrieve all previous
values. I actually need only the types :-/
A simple solution would be to disallow using multiple indexes for the
same cache, but that's not a welcome change. I'd prefer to throw an
exception on putAll : not supported when indexing is enabled.
Cheers,
Sanne
13 years, 6 months
Re: [infinispan-dev] Infinispan AS7 domain quickstart deployment "fun"
by Galder Zamarreño
Hmmmm, end of April would mean after AS 7.1.2 then? :(
If not fixed for AS 7.1.2, then we have 3 AS 7.1 releases where we cannot deploy Infinispan AS7 quickstart in domain mode which is not good :(
On Mar 26, 2012, at 6:55 PM, Jason Porter wrote:
> On Mon 26 Mar 2012 10:53:14 AM MDT, Pete Muir wrote:
>> I think some TCK checks this somewhere :-(
>>
>> On 26 Mar 2012, at 17:48, Jason Porter wrote:
>>
>>> This one is actually pretty interesting. I have declared that it throws
>>> Throwable instead of Exception, which is correct according to the
>>> compiler, but it looks like according to the spec, we need it to be
>>> exact. This is actually, *very easy* to fix :) but I am surprised it
>>> doesn't work according to the way Weld is handling it.
>>>
>>> On Mon 26 Mar 2012 10:46:24 AM MDT, Pete Muir wrote:
>>>> Or about the specific issue?
>>>>
>>>> On 26 Mar 2012, at 17:44, Jason Porter wrote:
>>>>
>>>>> We were only planning on doing a very small release with new examples,
>>>>> documentation improvements and minor bug fixes, but we don't have a
>>>>> date yet. The majority of our development time is going toward
>>>>> DeltaSpike
>>>>>
>>>>> On Thu 22 Mar 2012 10:04:03 AM MDT, Pete Muir wrote:
>>>>>> No, sorry.
>>>>>>
>>>>>> Jason P, any idea?
>>>>>>
>>>>>> On 22 Mar 2012, at 16:01, Galder Zamarreño wrote:
>>>>>>
>>>>>>> We're already using the latest which is 3.1.0.Final:
>>>>>>> https://repository.jboss.org/nexus/content/groups/public/org/jboss/solder...
>>>>>>> https://github.com/galderz/infinispan/blob/master/parent/pom.xml#L167
>>>>>>>
>>>>>>> Any idea when the next solder version is out?
>>>>>>>
>>>>>>> On Mar 22, 2012, at 1:35 PM, Pete Muir wrote:
>>>>>>>
>>>>>>>> This is a bug in Solder. I would try updating to the latest version of Solder.
>>>>>>>>
>>>>>>>> On 22 Mar 2012, at 08:49, Galder Zamarreño wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I've been having a bit of "fun" deploying Infinispan AS7 quickstarts in domain mode.
>>>>>>>>>
>>>>>>>>> 1. Trying to deploy Infinispan AS7 domain quickstart (https://github.com/galderz/infinispan-quickstart/tree/t_710final/jboss-as7) into AS 7.1.0.Final fails with:
>>>>>>>>> https://issues.jboss.org/browse/AS7-4048
>>>>>>>>>
>>>>>>>>> 2. This appears to be fixed in AS 7.1.1.Final but in this version, there's another error when you deploy the quickstart via the CLI:
>>>>>>>>> [Server:server-four] 08:53:47,370 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS015870: Deploy of deployment "infinispan-jboss-as7.war" was rolled back with failure message JBAS014750: Operation handler failed to complete
>>>>>>>>>
>>>>>>>>> I asked Emanuel about this and he's told me that this is fixed in master (??).
>>>>>>>>>
>>>>>>>>> 3. Right, so let's have a go at deploying the quickstart in master domain mode. Doesn't work:
>>>>>>>>> [Server:server-three] 09:26:02,823 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.deployment.unit."infinispan-jboss-as7.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."infinispan-jboss-as7.war".WeldService: org.jboss.weld.exceptions.DefinitionException: WELD-001450 Interceptor method public java.lang.Object org.jboss.solder.exception.control.ExceptionHandledInterceptor.passExceptionsToSolderCatch(javax.interceptor.InvocationContext) throws java.lang.Throwable does not declare that it throws Exception.
>>>>>>>>> [Server:server-three] at org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
>>>>>>>>> [Server:server-three] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>>>>>>>>> [Server:server-three] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>>>>>>>>> [Server:server-three] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_29]
>>>>>>>>> [Server:server-three] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_29]
>>>>>>>>> [Server:server-three] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29]
>>>>>>>>> [Server:server-three] Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-001450 Interceptor method public java.lang.Object org.jboss.solder.exception.control.ExceptionHandledInterceptor.passExceptionsToSolderCatch(javax.interceptor.InvocationContext) throws java.lang.Throwable does not declare that it throws Exception.
>>>>>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.InterceptorMetadataUtils.isValidBusinessMethodInterceptorMethod(InterceptorMetadataUtils.java:98)
>>>>>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.InterceptorMetadataUtils.isInterceptorMethod(InterceptorMetadataUtils.java:53)
>>>>>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.InterceptorMetadataUtils.buildMethodMap(InterceptorMetadataUtils.java:130)
>>>>>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.InterceptorMetadataUtils.readMetadataForInterceptorClass(InterceptorMetadataUtils.java:38)
>>>>>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.cache.DefaultMetadataCachingReader$1.apply(DefaultMetadataCachingReader.java:30)
>>>>>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.cache.DefaultMetadataCachingReader$1.apply(DefaultMetadataCachingReader.java:28)
>>>>>>>>> [Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355)
>>>>>>>>> [Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184)
>>>>>>>>> [Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153)
>>>>>>>>> [Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69)
>>>>>>>>> [Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393)
>>>>>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.cache.DefaultMetadataCachingReader.getInterceptorMetadata(DefaultMetadataCachingReader.java:54)
>>>>>>>>> [Server:server-three] at org.jboss.weld.bean.InterceptorImpl.<init>(InterceptorImpl.java:64)
>>>>>>>>> [Server:server-three] at org.jboss.weld.bean.InterceptorImpl.of(InterceptorImpl.java:59)
>>>>>>>>> [Server:server-three] at org.jboss.weld.bootstrap.AbstractBeanDeployer.createInterceptor(AbstractBeanDeployer.java:228)
>>>>>>>>> [Server:server-three] at org.jboss.weld.bootstrap.BeanDeployer.createBeans(BeanDeployer.java:137)
>>>>>>>>> [Server:server-three] at org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:204)
>>>>>>>>> [Server:server-three] at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:349)
>>>>>>>>> [Server:server-three] at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82)
>>>>>>>>> [Server:server-three] at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
>>>>>>>>> [Server:server-three] ... 5 more
>>>>>>>>>
>>>>>>>>> Kevin/Pete, any idea what's up this time?
>>>>>>>>>
>>>>>>>>> Please, let's try to get this fixed before 7.1.2.Final is out so that we can finally have the Infinispan quickstarts working again.
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> --
>>>>>>>>> Galder Zamarreño
>>>>>>>>> Sr. Software Engineer
>>>>>>>>> Infinispan, JBoss Cache
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Galder Zamarreño
>>>>>>> Sr. Software Engineer
>>>>>>> Infinispan, JBoss Cache
>>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> Member of JBoss Seam Team
>>>>> Author of Seam Catch
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Member of JBoss Seam Team
>>> Author of Seam Catch
>>>
>>
>
> Boo. Alright then. I can get this fixed. On my TODO is to dicuss with
> the community a date for Seam 3.1.1 or 3.2 whatever we call it (I'm
> leaning more towards 3.1.1 though). Right now I'm thinking end of April
> if things all fall on my sholders to fix and improve docs.
>
> --
> Member of JBoss Seam Team
> Author of Seam Catch
>
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
13 years, 6 months
Running the testsuite and being able to work with IDE
by Galder Zamarreño
Hi all,
Just wanted to share a tip that's helped me in the last few months get more productive
You might have seen that once you run the testsuite in the infinispan source code, IntelliJ kinda goes a bit mad re-indexing and the IDE becomes unusable.
Eventually I got fed up of this and what I do instead is rsync to a separate folder with:
rsync -av --exclude '.git' --exclude '*.class' --exclude 'target' --delete ~/Go/code/infinispan.git/ .
I do this from say: ~/Go/test/infinispan.git which crucially is not a git clone which avoids accidental commits from that folder.
Then, I always run the testsuite from that test folder after rsyncing. That way, I can carry on doing stuff in the IDE while the testsuite runs in the background.
Having SSD and 8gb ram help of course too :)
Cheers,
p.s. If you have any other tips that have helped you, please share.
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
13 years, 6 months
Re: [infinispan-dev] Infinispan AS7 domain quickstart deployment "fun"
by Pete Muir
Wrong thread, but +1 for 3.1.1
On 26 Mar 2012, at 17:55, Jason Porter wrote:
> On Mon 26 Mar 2012 10:53:14 AM MDT, Pete Muir wrote:
>> I think some TCK checks this somewhere :-(
>>
>> On 26 Mar 2012, at 17:48, Jason Porter wrote:
>>
>>> This one is actually pretty interesting. I have declared that it throws
>>> Throwable instead of Exception, which is correct according to the
>>> compiler, but it looks like according to the spec, we need it to be
>>> exact. This is actually, *very easy* to fix :) but I am surprised it
>>> doesn't work according to the way Weld is handling it.
>>>
>>> On Mon 26 Mar 2012 10:46:24 AM MDT, Pete Muir wrote:
>>>> Or about the specific issue?
>>>>
>>>> On 26 Mar 2012, at 17:44, Jason Porter wrote:
>>>>
>>>>> We were only planning on doing a very small release with new examples,
>>>>> documentation improvements and minor bug fixes, but we don't have a
>>>>> date yet. The majority of our development time is going toward
>>>>> DeltaSpike
>>>>>
>>>>> On Thu 22 Mar 2012 10:04:03 AM MDT, Pete Muir wrote:
>>>>>> No, sorry.
>>>>>>
>>>>>> Jason P, any idea?
>>>>>>
>>>>>> On 22 Mar 2012, at 16:01, Galder Zamarreño wrote:
>>>>>>
>>>>>>> We're already using the latest which is 3.1.0.Final:
>>>>>>> https://repository.jboss.org/nexus/content/groups/public/org/jboss/solder...
>>>>>>> https://github.com/galderz/infinispan/blob/master/parent/pom.xml#L167
>>>>>>>
>>>>>>> Any idea when the next solder version is out?
>>>>>>>
>>>>>>> On Mar 22, 2012, at 1:35 PM, Pete Muir wrote:
>>>>>>>
>>>>>>>> This is a bug in Solder. I would try updating to the latest version of Solder.
>>>>>>>>
>>>>>>>> On 22 Mar 2012, at 08:49, Galder Zamarreño wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I've been having a bit of "fun" deploying Infinispan AS7 quickstarts in domain mode.
>>>>>>>>>
>>>>>>>>> 1. Trying to deploy Infinispan AS7 domain quickstart (https://github.com/galderz/infinispan-quickstart/tree/t_710final/jboss-as7) into AS 7.1.0.Final fails with:
>>>>>>>>> https://issues.jboss.org/browse/AS7-4048
>>>>>>>>>
>>>>>>>>> 2. This appears to be fixed in AS 7.1.1.Final but in this version, there's another error when you deploy the quickstart via the CLI:
>>>>>>>>> [Server:server-four] 08:53:47,370 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS015870: Deploy of deployment "infinispan-jboss-as7.war" was rolled back with failure message JBAS014750: Operation handler failed to complete
>>>>>>>>>
>>>>>>>>> I asked Emanuel about this and he's told me that this is fixed in master (??).
>>>>>>>>>
>>>>>>>>> 3. Right, so let's have a go at deploying the quickstart in master domain mode. Doesn't work:
>>>>>>>>> [Server:server-three] 09:26:02,823 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.deployment.unit."infinispan-jboss-as7.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."infinispan-jboss-as7.war".WeldService: org.jboss.weld.exceptions.DefinitionException: WELD-001450 Interceptor method public java.lang.Object org.jboss.solder.exception.control.ExceptionHandledInterceptor.passExceptionsToSolderCatch(javax.interceptor.InvocationContext) throws java.lang.Throwable does not declare that it throws Exception.
>>>>>>>>> [Server:server-three] at org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
>>>>>>>>> [Server:server-three] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>>>>>>>>> [Server:server-three] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>>>>>>>>> [Server:server-three] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_29]
>>>>>>>>> [Server:server-three] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_29]
>>>>>>>>> [Server:server-three] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29]
>>>>>>>>> [Server:server-three] Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-001450 Interceptor method public java.lang.Object org.jboss.solder.exception.control.ExceptionHandledInterceptor.passExceptionsToSolderCatch(javax.interceptor.InvocationContext) throws java.lang.Throwable does not declare that it throws Exception.
>>>>>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.InterceptorMetadataUtils.isValidBusinessMethodInterceptorMethod(InterceptorMetadataUtils.java:98)
>>>>>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.InterceptorMetadataUtils.isInterceptorMethod(InterceptorMetadataUtils.java:53)
>>>>>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.InterceptorMetadataUtils.buildMethodMap(InterceptorMetadataUtils.java:130)
>>>>>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.InterceptorMetadataUtils.readMetadataForInterceptorClass(InterceptorMetadataUtils.java:38)
>>>>>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.cache.DefaultMetadataCachingReader$1.apply(DefaultMetadataCachingReader.java:30)
>>>>>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.cache.DefaultMetadataCachingReader$1.apply(DefaultMetadataCachingReader.java:28)
>>>>>>>>> [Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355)
>>>>>>>>> [Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184)
>>>>>>>>> [Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153)
>>>>>>>>> [Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69)
>>>>>>>>> [Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393)
>>>>>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.cache.DefaultMetadataCachingReader.getInterceptorMetadata(DefaultMetadataCachingReader.java:54)
>>>>>>>>> [Server:server-three] at org.jboss.weld.bean.InterceptorImpl.<init>(InterceptorImpl.java:64)
>>>>>>>>> [Server:server-three] at org.jboss.weld.bean.InterceptorImpl.of(InterceptorImpl.java:59)
>>>>>>>>> [Server:server-three] at org.jboss.weld.bootstrap.AbstractBeanDeployer.createInterceptor(AbstractBeanDeployer.java:228)
>>>>>>>>> [Server:server-three] at org.jboss.weld.bootstrap.BeanDeployer.createBeans(BeanDeployer.java:137)
>>>>>>>>> [Server:server-three] at org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:204)
>>>>>>>>> [Server:server-three] at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:349)
>>>>>>>>> [Server:server-three] at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82)
>>>>>>>>> [Server:server-three] at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
>>>>>>>>> [Server:server-three] ... 5 more
>>>>>>>>>
>>>>>>>>> Kevin/Pete, any idea what's up this time?
>>>>>>>>>
>>>>>>>>> Please, let's try to get this fixed before 7.1.2.Final is out so that we can finally have the Infinispan quickstarts working again.
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> --
>>>>>>>>> Galder Zamarreño
>>>>>>>>> Sr. Software Engineer
>>>>>>>>> Infinispan, JBoss Cache
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Galder Zamarreño
>>>>>>> Sr. Software Engineer
>>>>>>> Infinispan, JBoss Cache
>>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> Member of JBoss Seam Team
>>>>> Author of Seam Catch
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Member of JBoss Seam Team
>>> Author of Seam Catch
>>>
>>
>
> Boo. Alright then. I can get this fixed. On my TODO is to dicuss with
> the community a date for Seam 3.1.1 or 3.2 whatever we call it (I'm
> leaning more towards 3.1.1 though). Right now I'm thinking end of April
> if things all fall on my sholders to fix and improve docs.
>
> --
> Member of JBoss Seam Team
> Author of Seam Catch
>
13 years, 6 months
Re: [infinispan-dev] Infinispan AS7 domain quickstart deployment "fun"
by Pete Muir
I think some TCK checks this somewhere :-(
On 26 Mar 2012, at 17:48, Jason Porter wrote:
> This one is actually pretty interesting. I have declared that it throws
> Throwable instead of Exception, which is correct according to the
> compiler, but it looks like according to the spec, we need it to be
> exact. This is actually, *very easy* to fix :) but I am surprised it
> doesn't work according to the way Weld is handling it.
>
> On Mon 26 Mar 2012 10:46:24 AM MDT, Pete Muir wrote:
>> Or about the specific issue?
>>
>> On 26 Mar 2012, at 17:44, Jason Porter wrote:
>>
>>> We were only planning on doing a very small release with new examples,
>>> documentation improvements and minor bug fixes, but we don't have a
>>> date yet. The majority of our development time is going toward
>>> DeltaSpike
>>>
>>> On Thu 22 Mar 2012 10:04:03 AM MDT, Pete Muir wrote:
>>>> No, sorry.
>>>>
>>>> Jason P, any idea?
>>>>
>>>> On 22 Mar 2012, at 16:01, Galder Zamarreño wrote:
>>>>
>>>>> We're already using the latest which is 3.1.0.Final:
>>>>> https://repository.jboss.org/nexus/content/groups/public/org/jboss/solder...
>>>>> https://github.com/galderz/infinispan/blob/master/parent/pom.xml#L167
>>>>>
>>>>> Any idea when the next solder version is out?
>>>>>
>>>>> On Mar 22, 2012, at 1:35 PM, Pete Muir wrote:
>>>>>
>>>>>> This is a bug in Solder. I would try updating to the latest version of Solder.
>>>>>>
>>>>>> On 22 Mar 2012, at 08:49, Galder Zamarreño wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I've been having a bit of "fun" deploying Infinispan AS7 quickstarts in domain mode.
>>>>>>>
>>>>>>> 1. Trying to deploy Infinispan AS7 domain quickstart (https://github.com/galderz/infinispan-quickstart/tree/t_710final/jboss-as7) into AS 7.1.0.Final fails with:
>>>>>>> https://issues.jboss.org/browse/AS7-4048
>>>>>>>
>>>>>>> 2. This appears to be fixed in AS 7.1.1.Final but in this version, there's another error when you deploy the quickstart via the CLI:
>>>>>>> [Server:server-four] 08:53:47,370 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS015870: Deploy of deployment "infinispan-jboss-as7.war" was rolled back with failure message JBAS014750: Operation handler failed to complete
>>>>>>>
>>>>>>> I asked Emanuel about this and he's told me that this is fixed in master (??).
>>>>>>>
>>>>>>> 3. Right, so let's have a go at deploying the quickstart in master domain mode. Doesn't work:
>>>>>>> [Server:server-three] 09:26:02,823 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.deployment.unit."infinispan-jboss-as7.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."infinispan-jboss-as7.war".WeldService: org.jboss.weld.exceptions.DefinitionException: WELD-001450 Interceptor method public java.lang.Object org.jboss.solder.exception.control.ExceptionHandledInterceptor.passExceptionsToSolderCatch(javax.interceptor.InvocationContext) throws java.lang.Throwable does not declare that it throws Exception.
>>>>>>> [Server:server-three] at org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
>>>>>>> [Server:server-three] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>>>>>>> [Server:server-three] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>>>>>>> [Server:server-three] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_29]
>>>>>>> [Server:server-three] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_29]
>>>>>>> [Server:server-three] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29]
>>>>>>> [Server:server-three] Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-001450 Interceptor method public java.lang.Object org.jboss.solder.exception.control.ExceptionHandledInterceptor.passExceptionsToSolderCatch(javax.interceptor.InvocationContext) throws java.lang.Throwable does not declare that it throws Exception.
>>>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.InterceptorMetadataUtils.isValidBusinessMethodInterceptorMethod(InterceptorMetadataUtils.java:98)
>>>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.InterceptorMetadataUtils.isInterceptorMethod(InterceptorMetadataUtils.java:53)
>>>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.InterceptorMetadataUtils.buildMethodMap(InterceptorMetadataUtils.java:130)
>>>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.InterceptorMetadataUtils.readMetadataForInterceptorClass(InterceptorMetadataUtils.java:38)
>>>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.cache.DefaultMetadataCachingReader$1.apply(DefaultMetadataCachingReader.java:30)
>>>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.cache.DefaultMetadataCachingReader$1.apply(DefaultMetadataCachingReader.java:28)
>>>>>>> [Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355)
>>>>>>> [Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184)
>>>>>>> [Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153)
>>>>>>> [Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69)
>>>>>>> [Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393)
>>>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.cache.DefaultMetadataCachingReader.getInterceptorMetadata(DefaultMetadataCachingReader.java:54)
>>>>>>> [Server:server-three] at org.jboss.weld.bean.InterceptorImpl.<init>(InterceptorImpl.java:64)
>>>>>>> [Server:server-three] at org.jboss.weld.bean.InterceptorImpl.of(InterceptorImpl.java:59)
>>>>>>> [Server:server-three] at org.jboss.weld.bootstrap.AbstractBeanDeployer.createInterceptor(AbstractBeanDeployer.java:228)
>>>>>>> [Server:server-three] at org.jboss.weld.bootstrap.BeanDeployer.createBeans(BeanDeployer.java:137)
>>>>>>> [Server:server-three] at org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:204)
>>>>>>> [Server:server-three] at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:349)
>>>>>>> [Server:server-three] at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82)
>>>>>>> [Server:server-three] at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
>>>>>>> [Server:server-three] ... 5 more
>>>>>>>
>>>>>>> Kevin/Pete, any idea what's up this time?
>>>>>>>
>>>>>>> Please, let's try to get this fixed before 7.1.2.Final is out so that we can finally have the Infinispan quickstarts working again.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> --
>>>>>>> Galder Zamarreño
>>>>>>> Sr. Software Engineer
>>>>>>> Infinispan, JBoss Cache
>>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> Galder Zamarreño
>>>>> Sr. Software Engineer
>>>>> Infinispan, JBoss Cache
>>>>>
>>>>
>>>
>>> --
>>> Member of JBoss Seam Team
>>> Author of Seam Catch
>>>
>>
>
>
>
> --
> Member of JBoss Seam Team
> Author of Seam Catch
>
13 years, 6 months
Re: [infinispan-dev] Infinispan AS7 domain quickstart deployment "fun"
by Pete Muir
Or about the specific issue?
On 26 Mar 2012, at 17:44, Jason Porter wrote:
> We were only planning on doing a very small release with new examples,
> documentation improvements and minor bug fixes, but we don't have a
> date yet. The majority of our development time is going toward
> DeltaSpike
>
> On Thu 22 Mar 2012 10:04:03 AM MDT, Pete Muir wrote:
>> No, sorry.
>>
>> Jason P, any idea?
>>
>> On 22 Mar 2012, at 16:01, Galder Zamarreño wrote:
>>
>>> We're already using the latest which is 3.1.0.Final:
>>> https://repository.jboss.org/nexus/content/groups/public/org/jboss/solder...
>>> https://github.com/galderz/infinispan/blob/master/parent/pom.xml#L167
>>>
>>> Any idea when the next solder version is out?
>>>
>>> On Mar 22, 2012, at 1:35 PM, Pete Muir wrote:
>>>
>>>> This is a bug in Solder. I would try updating to the latest version of Solder.
>>>>
>>>> On 22 Mar 2012, at 08:49, Galder Zamarreño wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I've been having a bit of "fun" deploying Infinispan AS7 quickstarts in domain mode.
>>>>>
>>>>> 1. Trying to deploy Infinispan AS7 domain quickstart (https://github.com/galderz/infinispan-quickstart/tree/t_710final/jboss-as7) into AS 7.1.0.Final fails with:
>>>>> https://issues.jboss.org/browse/AS7-4048
>>>>>
>>>>> 2. This appears to be fixed in AS 7.1.1.Final but in this version, there's another error when you deploy the quickstart via the CLI:
>>>>> [Server:server-four] 08:53:47,370 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS015870: Deploy of deployment "infinispan-jboss-as7.war" was rolled back with failure message JBAS014750: Operation handler failed to complete
>>>>>
>>>>> I asked Emanuel about this and he's told me that this is fixed in master (??).
>>>>>
>>>>> 3. Right, so let's have a go at deploying the quickstart in master domain mode. Doesn't work:
>>>>> [Server:server-three] 09:26:02,823 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.deployment.unit."infinispan-jboss-as7.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."infinispan-jboss-as7.war".WeldService: org.jboss.weld.exceptions.DefinitionException: WELD-001450 Interceptor method public java.lang.Object org.jboss.solder.exception.control.ExceptionHandledInterceptor.passExceptionsToSolderCatch(javax.interceptor.InvocationContext) throws java.lang.Throwable does not declare that it throws Exception.
>>>>> [Server:server-three] at org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
>>>>> [Server:server-three] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>>>>> [Server:server-three] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>>>>> [Server:server-three] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_29]
>>>>> [Server:server-three] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_29]
>>>>> [Server:server-three] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29]
>>>>> [Server:server-three] Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-001450 Interceptor method public java.lang.Object org.jboss.solder.exception.control.ExceptionHandledInterceptor.passExceptionsToSolderCatch(javax.interceptor.InvocationContext) throws java.lang.Throwable does not declare that it throws Exception.
>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.InterceptorMetadataUtils.isValidBusinessMethodInterceptorMethod(InterceptorMetadataUtils.java:98)
>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.InterceptorMetadataUtils.isInterceptorMethod(InterceptorMetadataUtils.java:53)
>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.InterceptorMetadataUtils.buildMethodMap(InterceptorMetadataUtils.java:130)
>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.InterceptorMetadataUtils.readMetadataForInterceptorClass(InterceptorMetadataUtils.java:38)
>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.cache.DefaultMetadataCachingReader$1.apply(DefaultMetadataCachingReader.java:30)
>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.cache.DefaultMetadataCachingReader$1.apply(DefaultMetadataCachingReader.java:28)
>>>>> [Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355)
>>>>> [Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184)
>>>>> [Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153)
>>>>> [Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69)
>>>>> [Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393)
>>>>> [Server:server-three] at org.jboss.weld.interceptor.reader.cache.DefaultMetadataCachingReader.getInterceptorMetadata(DefaultMetadataCachingReader.java:54)
>>>>> [Server:server-three] at org.jboss.weld.bean.InterceptorImpl.<init>(InterceptorImpl.java:64)
>>>>> [Server:server-three] at org.jboss.weld.bean.InterceptorImpl.of(InterceptorImpl.java:59)
>>>>> [Server:server-three] at org.jboss.weld.bootstrap.AbstractBeanDeployer.createInterceptor(AbstractBeanDeployer.java:228)
>>>>> [Server:server-three] at org.jboss.weld.bootstrap.BeanDeployer.createBeans(BeanDeployer.java:137)
>>>>> [Server:server-three] at org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:204)
>>>>> [Server:server-three] at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:349)
>>>>> [Server:server-three] at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82)
>>>>> [Server:server-three] at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
>>>>> [Server:server-three] ... 5 more
>>>>>
>>>>> Kevin/Pete, any idea what's up this time?
>>>>>
>>>>> Please, let's try to get this fixed before 7.1.2.Final is out so that we can finally have the Infinispan quickstarts working again.
>>>>>
>>>>> Cheers,
>>>>> --
>>>>> Galder Zamarreño
>>>>> Sr. Software Engineer
>>>>> Infinispan, JBoss Cache
>>>>>
>>>>
>>>
>>> --
>>> Galder Zamarreño
>>> Sr. Software Engineer
>>> Infinispan, JBoss Cache
>>>
>>
>
> --
> Member of JBoss Seam Team
> Author of Seam Catch
>
13 years, 6 months
