December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-933) IronJacamarResourceCreator Throws ConcurrentModificationException

by jim_b_o (JIRA)

jim_b_o created JBJCA-933: ----------------------------- Summary: IronJacamarResourceCreator Throws ConcurrentModificationException Key: JBJCA-933 URL: https://issues.jboss.org/browse/JBJCA-933 Project: IronJacamar Issue Type: Bug Affects Versions: 1.0.12.Final Reporter: jim_b_o Assignee: Jesper Pedersen I am deploying three RARs in the same EAR and regularly get the exception shown below. 14:56:41,913 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register module: Module "deployment.EAR:main" from Service Module Loader 14:56:42,018 INFO [org.jboss.as.osgi] (MSC service thread 1-8) JBAS011907: Register module: Module "deployment.EAR.XXX.rar:main" from Service Module Loader 14:56:42,037 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-7) JBAS010406: Registered connection factory java:/eis/XXX 14:56:42,045 INFO [com.xxx.XXXResourceAdapter] (MSC service thread 1-7) #start 14:56:42,047 INFO [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-7) IJ020002: Deployed: XXX 14:56:42,055 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/eis/XXX] 14:56:42,057 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register module: Module "deployment.EAR.YYY.rar:main" from Service Module Loader 14:56:42,071 INFO [org.jboss.as.osgi] (MSC service thread 1-5) JBAS011907: Register module: Module "deployment.EAR.ZZZ.rar:main" from Service Module Loader 14:56:42,148 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-8) JBAS010406: Registered connection factory java:/eis/ZZZ 14:56:42,150 INFO [com.yyy.YYYResourceAdapter] (MSC service thread 1-8) #start 14:56:42,161 INFO [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-8) IJ020002: Deployed: ZZZ 14:56:42,167 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/eis/ZZZ] 14:56:42,173 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-6) JBAS010406: Registered connection factory java:/eis/YYY 14:56:42,176 INFO [com.zzz.ZZZResourceAdapter] (MSC service thread 1-6) #start 14:56:42,177 ERROR [org.jboss.msc.service] (MSC service thread 1-7) MSC00002: Invocation of listener "org.jboss.as.connector.deployers.ra.processors.ParsedRaDeploymentProcessor$1@21641d7d" failed: java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:894) [rt.jar:1.7.0_09] at java.util.HashMap$KeyIterator.next(HashMap.java:928) [rt.jar:1.7.0_09] at org.jboss.as.connector.subsystems.resourceadapters.IronJacamarResourceCreator.getIronJacamarResource(IronJacamarResourceCreator.java:268) [jboss-as-connector-7.1.3.Final.jar:7.1.3.Final] at org.jboss.as.connector.subsystems.resourceadapters.IronJacamarResourceCreator.execute(IronJacamarResourceCreator.java:283) [jboss-as-connector-7.1.3.Final.jar:7.1.3.Final] at org.jboss.as.connector.deployers.ra.processors.ParsedRaDeploymentProcessor$1.registerIronjacamar(ParsedRaDeploymentProcessor.java:160) [jboss-as-connector-7.1.3.Final.jar:7.1.3.Final] at org.jboss.as.connector.deployers.ra.processors.AbstractResourceAdapterDeploymentServiceListener.transition(AbstractResourceAdapterDeploymentServiceListener.java:153) [jboss-as-connector-7.1.3.Final.jar:7.1.3.Final] at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1416) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl.access$2700(ServiceControllerImpl.java:49) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1954) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09] 14:56:42,182 INFO [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-6) IJ020002: Deployed: YYY 14:56:42,190 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/eis/YYY] I've replaced the real names of my components with XXX, YYY and ZZZ in a consistent way above. The problem seems to be during the interleaving of YYY and ZZZ. -- 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

2
1
0 / 0

[JBoss JIRA] (AS7-6060) naming's :jndi-view operation failing with standalone-full.xml configuration

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-6060: -------------------------------- Summary: naming's :jndi-view operation failing with standalone-full.xml configuration Key: AS7-6060 URL: https://issues.jboss.org/browse/AS7-6060 Project: Application Server 7 Issue Type: Feature Request Components: Naming Reporter: Jeff Mesnil Assignee: Eduardo Martins I noticed this on AS7 master branch. If I run the server with the standalone.xml configuration, the /subsystem=naming:jndi-view runs fine. However with standalone-full.xml or standalone-full-ha.xml, the operation fails: {noformat} [standalone@localhost:9999 /] /subsystem=naming:jndi-view { "outcome" => "failed", "result" => {"java: contexts" => {"java:" => { "ConnectionFactory" => { "class-name" => "org.hornetq.jms.client.HornetQJMSConnectionFactory", "value" => "HornetQConnectionFactory [serverLocator=ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=in-vm, factory=org-hornetq-core-remoting-impl-invm-InVMConnectorFactory) ?server-id=0], discoveryGroupConfiguration=null], clientID=null, dupsOKBatchSize=1048576, transactionBatchSize=1048576, readOnly=false]" }, "JmsXA" => { "class-name" => "java.lang.Object", "value" => "?" }, "TransactionManager" => { "class-name" => "com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate", "value" => "com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate@36bbb8c4" }, "ejb" => { "class-name" => "javax.naming.Context", "children" => {"mgmt" => { "class-name" => "javax.naming.Context", "children" => {"MEJB" => {"class-name" => "javax.management.j2ee.ManagementHome"}} }} } }}}, "failure-description" => "JBAS014749: Operation handler failed: JBAS014487: Could not load view class for ejb EJB", "rolled-back" => true } {noformat} with the stack trace on the server-side: {noformat} 18:16:17,682 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("jndi-view") failed - address: ([("subsystem" => "naming")]): java.lang.RuntimeException: JBAS014487: Could not load view class for ejb EJB at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:90) at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getJndiViewInstanceValue(RemoteViewManagedReferenceFactory.java:79) at org.jboss.as.naming.management.JndiViewOperation.addEntries(JndiViewOperation.java:144) at org.jboss.as.naming.management.JndiViewOperation.addEntries(JndiViewOperation.java:138) at org.jboss.as.naming.management.JndiViewOperation.addEntries(JndiViewOperation.java:138) at org.jboss.as.naming.management.JndiViewOperation.access$000(JndiViewOperation.java:48) at org.jboss.as.naming.management.JndiViewOperation$1.execute(JndiViewOperation.java:65) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:439) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:321) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:228) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:223) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:135) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:111) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09-icedtea] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09-icedtea] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA] Caused by: java.lang.ClassNotFoundException: javax.management.j2ee.ManagementHome from [Module "org.jboss.as.naming:main" from local module loader @5cbe930a (roots: /home/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules)] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.3.GA] at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_09-icedtea] at java.lang.Class.forName(Class.java:264) [rt.jar:1.7.0_09-icedtea] at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:87) ... 20 more {noformat} -- 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

3
3
0 / 0

[JBoss JIRA] (AS7-6068) jar file system is broken again (regression)

by Alvin Thompson (JIRA)

Alvin Thompson created AS7-6068: ----------------------------------- Summary: jar file system is broken again (regression) Key: AS7-6068 URL: https://issues.jboss.org/browse/AS7-6068 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Reporter: Alvin Thompson -- 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
4
0 / 0

[JBoss JIRA] (AS7-5940) Support configuring the transaction subsystem JDBC ObjectStore

by Tom Jenkinson (JIRA)

Tom Jenkinson created AS7-5940: ---------------------------------- Summary: Support configuring the transaction subsystem JDBC ObjectStore Key: AS7-5940 URL: https://issues.jboss.org/browse/AS7-5940 Project: Application Server 7 Issue Type: Task Reporter: Tom Jenkinson Assignee: Stefano Maestri The JDBC ObjectStore has been added back into AS7 as part of JBTM-1230. The transaction subsystem needs to support configuring the store. To configure the store, take a look at: ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/objectstore/JDBCStoreTest.java Note, this work is dependent on the AS consuming a version of JBTM with JBTM-1230 completed - this is scheduled for 4.17.3 of JBTM. -- 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

2
2
0 / 0

[JBoss JIRA] (JBRULES-3456) Eclipse drools plugin - drools jars dissappear from drools library when internal classes are switched from Discouraged to Accesible

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3456: ------------------------------------ Summary: Eclipse drools plugin - drools jars dissappear from drools library when internal classes are switched from Discouraged to Accesible Key: JBRULES-3456 URL: https://issues.jboss.org/browse/JBRULES-3456 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco When I set Drools internal classes from Discouraged to Accessible in Eclipse, then the jars dissapear from Drools library in Library screen of project. I have thought that setting internal classes to Accesible would remove several warnings from our test suite, but actual result is that there is just Drools library which is without jars. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
15
0 / 0

[JBoss JIRA] (AS7-6067) Upgrade JGroups to 3.2.4.Final

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-6067: ----------------------------------- Summary: Upgrade JGroups to 3.2.4.Final Key: AS7-6067 URL: https://issues.jboss.org/browse/AS7-6067 Project: Application Server 7 Issue Type: Feature Request Components: Clustering Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 7.2.0.Alpha1 To sync with Ispn, https://issues.jboss.org/browse/AS7-6066 Changes: https://github.com/belaban/JGroups/commits/JGroups_3_2_4_Final -- 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-6066) Upgrade Infinispan to 5.2.0.Beta5

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-6066: ----------------------------------- Summary: Upgrade Infinispan to 5.2.0.Beta5 Key: AS7-6066 URL: https://issues.jboss.org/browse/AS7-6066 Project: Application Server 7 Issue Type: Feature Request Components: Clustering Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 7.2.0.Alpha1 http://infinispan.blogspot.it/2012/12/infinispan-520beta5.html -- 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-5449) when defining custom executor for connector thread priority is not optional

by Mathieu Lachance (JIRA)

Mathieu Lachance created AS7-5449: ------------------------------------- Summary: when defining custom executor for connector thread priority is not optional Key: AS7-5449 URL: https://issues.jboss.org/browse/AS7-5449 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.2.Final (EAP) Reporter: Mathieu Lachance when defining a custom executor in the threads subsystem for the connector defined in the web subsystem like : {code:xml} <subsystem xmlns="urn:jboss:domain:threads:1.1"> <thread-factory name="ConnectorThreadFactory" group-name="ConnectorThreadPool"/> <unbounded-queue-thread-pool name="ConnectorThreadPool"> <max-threads count="500"/> <keepalive-time time="60" unit="seconds"/> <thread-factory name="ConnectorThreadFactory"/> </unbounded-queue-thread-pool> </subsystem> <subsystem xmlns="urn:jboss:domain:web:1.1" default-virtual-server="default-host" native="false"> <connector name="ajp" protocol="AJP/1.3" scheme="http" socket-binding="ajp" redirect-port="8443" executor="ConnectorThreadPool"/> </subsystem> {code} it will fail with : {quote} 17:19:06,508 ERROR [org.apache.tomcat.util.net.JIoEndpoint] (http-/0.0.0.0:8443-Acceptor-0) Error allocating socket processor: java.lang.IllegalArgumentException at java.lang.Thread.setPriority(Thread.java:1058) [rt.jar:1.6.0_31] at org.jboss.threads.JBossThreadFactory.createThread(JBossThreadFactory.java:127) [jboss-threads-2.0.0.GA.jar:2.0.0.GA] at org.jboss.threads.JBossThreadFactory.newThread(JBossThreadFactory.java:101) [jboss-threads-2.0.0.GA.jar:2.0.0.GA] at java.util.concurrent.ThreadPoolExecutor.addThread(ThreadPoolExecutor.java:672) [rt.jar:1.6.0_31] at java.util.concurrent.ThreadPoolExecutor.addIfUnderCorePoolSize(ThreadPoolExecutor.java:697) [rt.jar:1.6.0_31] at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:652) [rt.jar:1.6.0_31] at org.jboss.threads.JBossThreadPoolExecutor.execute(JBossThreadPoolExecutor.java:63) [jboss-threads-2.0.0.GA.jar:2.0.0.GA] at org.jboss.threads.DelegatingBlockingExecutorService.execute(DelegatingBlockingExecutorService.java:42) [jboss-threads-2.0.0.GA.jar:2.0.0.GA] at org.jboss.as.threads.ManagedExecutorService.execute(ManagedExecutorService.java:64) [jboss-as-threads-7.1.2.Final.jar:7.1.2.Final] at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:1237) [jbossweb-7.0.16.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:325) [jbossweb-7.0.16.Final.jar:] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_31] {quote} even though if documentation state that thread priority is optional : {code:xml} <xs:complexType name="thread-factory"> <xs:annotation> <xs:documentation> <![CDATA[ A thread factory (implementing java.util.concurrent.ThreadFactory). The "name" attribute is the bean name of the created thread factory. The optional "priority" attribute may be used to specify the thread priority of created threads. The optional "group-name" attribute specifies the name of a the thread group to create for this thread factory. The "thread-name-pattern" is the template used to create names for threads. The following patterns may be used: %% - emit a percent sign %t - emit the per-factory thread sequence number %g - emit the global thread sequence number %f - emit the factory sequence number %i - emit the thread ID %G - emit the thread group name ]]> </xs:documentation> </xs:annotation> <xs:attribute name="name" type="xs:string" use="required"/> <xs:attribute name="group-name" type="xs:string" use="optional"/> <xs:attribute name="thread-name-pattern" type="xs:string" use="optional"/> <xs:attribute name="priority" type="priority" use="optional"/> </xs:complexType> {code} -- 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

3
9
0 / 0

[JBoss JIRA] (AS7-6064) Datasource pool parameters cannot be edited in the admin console without disabling the datasource first

by Tom Fonteyne (JIRA)

Tom Fonteyne created AS7-6064: --------------------------------- Summary: Datasource pool parameters cannot be edited in the admin console without disabling the datasource first Key: AS7-6064 URL: https://issues.jboss.org/browse/AS7-6064 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.2.Final (EAP) Reporter: Tom Fonteyne Assignee: Heiko Braun Priority: Minor Datasource pool parameters cannot be edited in the admin console without disabling the datasource first -- 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-6065) CLONE - Datasource pool parameters cannot be edited in the admin console without disabling the datasource first

by Tom Fonteyne (JIRA)

Tom Fonteyne created AS7-6065: --------------------------------- Summary: CLONE - Datasource pool parameters cannot be edited in the admin console without disabling the datasource first Key: AS7-6065 URL: https://issues.jboss.org/browse/AS7-6065 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.2.Final (EAP) Reporter: Tom Fonteyne Assignee: Heiko Braun Priority: Minor Datasource pool parameters cannot be edited in the admin console without disabling the datasource first -- 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