JBoss + Tibco
by Siamak Sadeghianfar
Hi,
In prior versions of JBoss it was possible to use an external messaging
server like Tibco through defining an ExternalContext, JMS Provider and
connection factory that creates connections to the external server [1].
Is there anyway to do a similar setup with AS7?
Thanks in advance.
Best Regards,
Siamak Sadeghianfar
[1] https://community.jboss.org/wiki/JBossEAP5IntegrationwithTibcoEMS
14 years
Hibernate/Infinispan Exception/Failure on redeployment
by Frank Langelage
After the current Hibernate upgrade from 4.0.1 to 4.1.1 in JBoss AS7 I
see such exception when redeploying my ear application.
This only happens, when I have deployed two ear and replace one of them.
When only one is deployed and I replace it with a new version this does
not happen.
Also not when deploying another ear additional to an existing one.
I have enabled cache in persistence.xml (see attached), did not define a
region prefix.
19:10:12,001 ERROR [org.jboss.msc.service.fail#startFailed] MSC00001:
Failed to start service
jboss.persistenceunit."dtz2e-langfr-sb2000-net.ear/ejb-entity.jar#dtz2e-langfr-sb2000-net":
org.jboss.msc.service.StartException in service
jboss.persistenceunit."dtz2e-langfr-sb2000-net.ear/ejb-entity.jar#dtz2e-langfr-sb2000-net":
Failed to start service
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[rt.jar:1.6.0_31]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[rt.jar:1.6.0_31]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_31]
Caused by: java.util.NoSuchElementException
at java.util.Collections$EmptySet$1.next(Collections.java:2912)
[rt.jar:1.6.0_31]
at
org.hibernate.cache.infinispan.InfinispanRegionFactory.getCacheCommandFactory(InfinispanRegionFactory.java:448)
at
org.hibernate.cache.infinispan.InfinispanRegionFactory.startRegion(InfinispanRegionFactory.java:337)
at
org.hibernate.cache.infinispan.InfinispanRegionFactory.buildEntityRegion(InfinispanRegionFactory.java:195)
at
org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:347)
at
org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1740)
at
org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:94)
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:904)
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:889)
at
org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73)
at
org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162)
at
org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
... 3 more
14 years
Re: [jboss-as7-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
14 years
jsp:forward problem
by Adrien RUFFIE
Hello all,
I have the following error :
2012-03-27 09:11:15,359 INFO [STDOUT] (http-127.0.0.1-8080-1) 2012-03-27 09:11:15,343 190351 [http-127.0.0.1-8080-1] ERROR com.myapplication.controller.ControllerServlet - Error in forwarding page [/index.jsp]
2012-03-27 09:11:15,360 INFO [STDOUT] (http-127.0.0.1-8080-1) org.apache.jasper.JasperException: An exception occurred processing JSP page /index.jsp at line 2
2012-03-27 09:11:15,360 INFO [STDOUT] (http-127.0.0.1-8080-1)
2012-03-27 09:11:15,360 INFO [STDOUT] (http-127.0.0.1-8080-1) 1: <%@ page language="java"%>
2012-03-27 09:11:15,360 INFO [STDOUT] (http-127.0.0.1-8080-1) 2: <jsp:forward page="/home.fl"/>
2012-03-27 09:11:15,360 INFO [STDOUT] (http-127.0.0.1-8080-1)
2012-03-27 09:11:15,361 INFO [STDOUT] (http-127.0.0.1-8080-1)
2012-03-27 09:11:15,361 INFO [STDOUT] (http-127.0.0.1-8080-1) Stacktrace:
2012-03-27 09:11:15,361 INFO [STDOUT] (http-127.0.0.1-8080-1) at org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:498)
2012-03-27 09:11:15,361 INFO [STDOUT] (http-127.0.0.1-8080-1) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393)
2012-03-27 09:11:15,361 INFO [STDOUT] (http-127.0.0.1-8080-1) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326)
2012-03-27 09:11:15,361 INFO [STDOUT] (http-127.0.0.1-8080-1) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253)
2012-03-27 09:11:15,361 INFO [STDOUT] (http-127.0.0.1-8080-1) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
My index.jsp is just following 2 code line:
<%@ page language="java"%>
<jsp:forward page="/home.fl"/>
Do you know if jsp :forward work fine with JBoss 6 AS ? Is there a workaround or procedure existe ?
Thank you very much
Best regards,
[cid:image006.png@01CD0C02.769E34C0]<http://e-deal.biz/kd/9eZ>
[cid:image003.png@01CD0C02.0E7D8F30]<http://e-deal.biz/kd/UOh>[cid:image004.png@01CD0C02.0E7D8F30]<http://e-deal.biz/kd/X9Q>[cid:image005.png@01CD0C02.0E7D8F30]<http://e-deal.biz/kd/bTG>
Adrien RUFFIE
Ingénieur R&D
40, rue du Village d'Entreprises
31670 Labège
www.e-deal.com<http://www.e-deal.com/>
LD : +33 1 73 03 29 XX
Std : +33 1 73 03 29 80
Fax : +33 1 73 01 69 77
a.ruffie(a)e-deal.com <mailto:a.ruffie@e-deal.com%20>
E-DEAL soutient le Pacte Mondial de l'ONU<http://e-deal.biz/kd/mPQ>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
14 years
Re: [jboss-as7-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
>
14 years
Re: [jboss-as7-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
>
14 years
Re: [jboss-as7-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
>
14 years
operation timeout
by Heiko Braun
we've got a problem with large file uploads:
https://issues.jboss.org/browse/AS7-4234
i am wondering if we have some kind of "operation timeout" that might be causing this.
maybe somebody with a good understanding of the management layer can take a quick look at at the attached host controller log.
regards, heiko
14 years
