December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6184) CLONE - ConcurrentModificationException in org.jboss.as.cmp.TransactionEntityMap$GlobalTxSynchronization instances

by Brad Maxwell (JIRA)

Brad Maxwell created AS7-6184: --------------------------------- Summary: CLONE - ConcurrentModificationException in org.jboss.as.cmp.TransactionEntityMap$GlobalTxSynchronization instances Key: AS7-6184 URL: https://issues.jboss.org/browse/AS7-6184 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.2.Final (EAP) Reporter: Brad Maxwell Assignee: Brad Maxwell Fix For: 7.1.4.Final (EAP) ConcurrentModificationException Caused by: javax.ejb.EJBException: JBAS018688: Exception in store of entity: 710304 at org.jboss.as.cmp.TransactionEntityMap$GlobalTxSynchronization.synchronize(TransactionEntityMap.java:317) [jboss-as-cmp-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.as.cmp.TransactionEntityMap.synchronizeEntities(TransactionEntityMap.java:214) [jboss-as-cmp-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.as.cmp.component.CmpEntityBeanComponent.synchronizeEntitiesWithinTransaction(CmpEntityBeanComponent.java:104) [jboss-as-cmp-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.as.cmp.component.interceptors.CmpEntityBeanHomeFinderInterceptorFactory.invokeFind(CmpEntityBeanHomeFinderInterceptorFactory.java:69) [jboss-as-cmp-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.as.ejb3.component.entity.interceptors.EntityBeanHomeFinderInterceptorFactory$1.processInvocation(EntityBeanHomeFinderInterceptorFactory.java:92) [jboss-as-ejb3-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-1.jar:1.1.1.Final-redhat-1] at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:201) [jboss-as-ejb3-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] ... 90 more Caused by: java.util.ConcurrentModificationException at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:819) [rt.jar:1.7.0_09] at java.util.ArrayList$Itr.next(ArrayList.java:791) [rt.jar:1.7.0_09] at org.jboss.as.cmp.TransactionEntityMap$GlobalTxSynchronization.synchronize(TransactionEntityMap.java:278) [jboss-as-cmp-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] ... 96 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6183) ConcurrentModificationException in org.jboss.as.cmp.TransactionEntityMap$GlobalTxSynchronization instances

by Brad Maxwell (JIRA)

Brad Maxwell created AS7-6183: --------------------------------- Summary: ConcurrentModificationException in org.jboss.as.cmp.TransactionEntityMap$GlobalTxSynchronization instances Key: AS7-6183 URL: https://issues.jboss.org/browse/AS7-6183 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.2.Final (EAP) Reporter: Brad Maxwell Assignee: Brad Maxwell Fix For: 7.1.4.Final (EAP) ConcurrentModificationException Caused by: javax.ejb.EJBException: JBAS018688: Exception in store of entity: 710304 at org.jboss.as.cmp.TransactionEntityMap$GlobalTxSynchronization.synchronize(TransactionEntityMap.java:317) [jboss-as-cmp-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.as.cmp.TransactionEntityMap.synchronizeEntities(TransactionEntityMap.java:214) [jboss-as-cmp-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.as.cmp.component.CmpEntityBeanComponent.synchronizeEntitiesWithinTransaction(CmpEntityBeanComponent.java:104) [jboss-as-cmp-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.as.cmp.component.interceptors.CmpEntityBeanHomeFinderInterceptorFactory.invokeFind(CmpEntityBeanHomeFinderInterceptorFactory.java:69) [jboss-as-cmp-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.as.ejb3.component.entity.interceptors.EntityBeanHomeFinderInterceptorFactory$1.processInvocation(EntityBeanHomeFinderInterceptorFactory.java:92) [jboss-as-ejb3-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-1.jar:1.1.1.Final-redhat-1] at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:201) [jboss-as-ejb3-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] ... 90 more Caused by: java.util.ConcurrentModificationException at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:819) [rt.jar:1.7.0_09] at java.util.ArrayList$Itr.next(ArrayList.java:791) [rt.jar:1.7.0_09] at org.jboss.as.cmp.TransactionEntityMap$GlobalTxSynchronization.synchronize(TransactionEntityMap.java:278) [jboss-as-cmp-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] ... 96 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6176) Setup TCK job for Enterprise OSGi WebApp

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6176?page=com.atlassian.jira.plugin.s... ] Thomas Diesler resolved AS7-6176. --------------------------------- Resolution: Done Done https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossOSGi/job/osgi.... > Setup TCK job for Enterprise OSGi WebApp > ---------------------------------------- > > Key: AS7-6176 > URL: https://issues.jboss.org/browse/AS7-6176 > Project: Application Server 7 > Issue Type: Task > Components: OSGi > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 7.2.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6179) Upgrade Hibernate Validator to 4.3.1.Final

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-6179?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on AS7-6179: ----------------------------------- {quote} <hardy> also here https://github.com/jbossas/jboss-as/blob/master/jpa/core/src/main/java/or... <hardy> the other thing I am wondering is whether it is correct to always initialise Hibernate Validator <smarlow> hardy: should I do that as part of the upgrade? removing the config.addMapping(new ConstraintMapping()); <hardy> this one you can do as part of the upgrade for sure <hardy> this line is no good for anything really {quote} > Upgrade Hibernate Validator to 4.3.1.Final > ------------------------------------------ > > Key: AS7-6179 > URL: https://issues.jboss.org/browse/AS7-6179 > Project: Application Server 7 > Issue Type: Component Upgrade > Components: JPA / Hibernate > Affects Versions: 7.1.3.Final (EAP), 7.2.0.Alpha1 > Reporter: Juergen Zimmermann > Assignee: Scott Marlow > > JBossAS currently contains 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6182) Upgrade logging components

by James Perkins (JIRA)

James Perkins created AS7-6182: ---------------------------------- Summary: Upgrade logging components Key: AS7-6182 URL: https://issues.jboss.org/browse/AS7-6182 Project: Application Server 7 Issue Type: Enhancement Reporter: James Perkins Assignee: David Lloyd Priority: Blocker Fix For: 7.2.0.Alpha1 Components needing upgrade: * slf4j-jboss-logmanager * jboss-logmanager * log4j-jboss-logmanager -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6168) component upgrade to Hibernate 4.1.9.Final

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-6168?page=com.atlassian.jira.plugin.s... ] Scott Marlow resolved AS7-6168. ------------------------------- Fix Version/s: (was: 7.2.0.Alpha1) Resolution: Rejected rejecting due to regression in StatefulWithXPCFailoverTestCase (see http://hudson.jboss.org/hudson/job/as7-param-pull/5123/) > component upgrade to Hibernate 4.1.9.Final > ------------------------------------------ > > Key: AS7-6168 > URL: https://issues.jboss.org/browse/AS7-6168 > Project: Application Server 7 > Issue Type: Feature Request > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6181) Add @ValidIdRange annotation to message loggers and message bundles

by James Perkins (JIRA)

James Perkins created AS7-6181: ---------------------------------- Summary: Add @ValidIdRange annotation to message loggers and message bundles Key: AS7-6181 URL: https://issues.jboss.org/browse/AS7-6181 Project: Application Server 7 Issue Type: Enhancement Reporter: James Perkins Assignee: James Perkins Fix For: 7.3.0.Alpha1 A new release of the logging tooling will include a {{@ValidIdRange}} annotation. This will help document which id ranges allowed as well as provide compile time validation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3705) Same criteria across multiple rules cancels activation with Property Reactive Facts

by manoj chanian (JIRA)

manoj chanian created JBRULES-3705: -------------------------------------- Summary: Same criteria across multiple rules cancels activation with Property Reactive Facts Key: JBRULES-3705 URL: https://issues.jboss.org/browse/JBRULES-3705 Project: JBRULES Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.5.0.Final Reporter: manoj chanian Assignee: Mark Proctor Priority: Critical When using property reactive facts, if 2 or more rules have the same criteria this causes an unexpected cancel of the rule activation. As objects are inserted into the engine, the activations are created as expected but after an activation is fired on a rule, any other rules that have the same criteria get their activation cancelled. If all the rules have a different criteria then all works fine. If you switch off property reactive mode then all works fine. I cant seem to add attachments to this jira but i have added all the attachments and unit tests to the following forum post: http://drools.46999.n3.nabble.com/same-criteria-across-multiple-rules-can... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6180) allow expressions in the remoting subsystem

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-6180: -------------------------------- Summary: allow expressions in the remoting subsystem Key: AS7-6180 URL: https://issues.jboss.org/browse/AS7-6180 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management, Remoting Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 7.2.0.Alpha1, 7.2.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6177) Failed to execute goal on project jboss-as-clustering-jgroups

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/AS7-6177?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson commented on AS7-6177: ------------------------------------ Sure, I was getting permgen errors on windows during the building of the tests hence why I went this route. I guess not supporting it is fine, but I think you can use some plugin to fail the build if the user does add it if it really won't work, I can't remember the name of the plugin, is it called "enforcer" or something maybe? thanks for looking into this! > Failed to execute goal on project jboss-as-clustering-jgroups > ------------------------------------------------------------- > > Key: AS7-6177 > URL: https://issues.jboss.org/browse/AS7-6177 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 7.2.0.Alpha1 > Reporter: Tom Jenkinson > Assignee: Radoslav Husar > Priority: Minor > Fix For: 7.2.0.Alpha1 > > Attachments: AS7-build-failed.txt > > > Failed to execute goal on project jboss-as-clustering-jgroups: Could not resolve dependencies for project org.jboss.as:jboss-as-clustering-jgroups:jar:7.2.0.Alpha1-SNAPSHOT: Failure to find org.jboss.as:jboss-as-clustering-common:jar:tests:7.2.0.Alpha1-SNAPSHOT -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2012