February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3578) Errors in data source subsystem checking

by Vladimir Rastseluev (JIRA)

Vladimir Rastseluev created AS7-3578: ---------------------------------------- Summary: Errors in data source subsystem checking Key: AS7-3578 URL: https://issues.jboss.org/browse/AS7-3578 Project: Application Server 7 Issue Type: Bug Components: JCA Reporter: Vladimir Rastseluev Assignee: Stefano Maestri Fix For: 7.1.0.Final 1) it's possible to add <flush-strategy> element with any value (not only listed in xsd schema) 2) it's possible to add <xa-data-source> element without any <xa-datasource-property>(in xsd schema minOccurs=1) 3) it's possible to add 2 or more <security-domain> elements without error(in xsd schema maxOccurs=1) -- 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

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] (AS7-3380) Changing MDB configuration in jboss-ejb3.xml causes ClassCastException

by Ondřej Chaloupka (JIRA)

Ondřej Chaloupka created AS7-3380: ------------------------------------- Summary: Changing MDB configuration in jboss-ejb3.xml causes ClassCastException Key: AS7-3380 URL: https://issues.jboss.org/browse/AS7-3380 Project: Application Server 7 Issue Type: Bug Reporter: Ondřej Chaloupka Assignee: jaikiran pai I did change of destination of mdb queue in jboss-ejb3.xml file in following way: https://github.com/ochaloup/jboss-as/commit/5a0501387821994b6a94ddb508f6f... But during deployment I get exception: java.lang.ClassCastException: org.jboss.metadata.ejb.spec.MessageDrivenBean31MetaData cannot be cast to org.jboss.metadata.ejb.jboss.ejb3.JBossGenericBeanMetaData {code} ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."mdb.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."mdb.jar".PARSE: Failed to process phase PARSE of deployment "mdb.jar" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_23] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_23] at java.lang.Thread.run(Thread.java:662) [:1.6.0_23] Caused by: java.lang.ClassCastException: org.jboss.metadata.ejb.spec.MessageDrivenBean31MetaData cannot be cast to org.jboss.metadata.ejb.jboss.ejb3.JBossGenericBeanMetaData at org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.merge(MessageDrivenBeanMetaData.java:353) at org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.createMerged(MessageDrivenBeanMetaData.java:85) at org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.createMerged(MessageDrivenBeanMetaData.java:36) at org.jboss.metadata.ejb.spec.EnterpriseBeansMetaData.merge(EnterpriseBeansMetaData.java:73) at org.jboss.metadata.ejb.spec.EnterpriseBeansMetaData.createMerged(EnterpriseBeansMetaData.java:52) at org.jboss.metadata.ejb.spec.EjbJarMetaData.merge(EjbJarMetaData.java:175) at org.jboss.metadata.ejb.spec.EjbJarMetaData.createMerged(EjbJarMetaData.java:668) at org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.deploy(EjbJarParsingDeploymentUnitProcessor.java:125) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] ... 5 more {code} -- 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

14 years, 2 months

3
5
0 / 0

[JBoss JIRA] (AS7-3599) Inconsistent Jacorb configuration

by Heiko Braun (JIRA)

Heiko Braun created AS7-3599: -------------------------------- Summary: Inconsistent Jacorb configuration Key: AS7-3599 URL: https://issues.jboss.org/browse/AS7-3599 Project: Application Server 7 Issue Type: Bug Components: IIOP Reporter: Heiko Braun Assignee: Stefan Guilhen {noformat} this config: <subsystem xmlns="urn:jboss:domain:jacorb:1.1"> <orb> <initializers security="on"/> </orb> <poa> <request-processors pool-size="2"/> </poa> <naming export-corbaloc="off"/> </subsystem> <subsystem xmlns="urn:jboss:domain:jaxrs:1.0"/> <subsystem xmlns="urn:jboss:domain:jca:1.1"> <archive-validation enabled="true"/> <bean-validation enabled="true"/> <default-workmanager> <short-running-threads> <core-threads count="50"/> <queue-length count="50"/> <max-threads count="50"/> <keepalive-time time="10" unit="seconds"/> </short-running-threads> <long-running-threads> <core-threads count="50"/> <queue-length count="50"/> <max-threads count="50"/> <keepalive-time time="10" unit="seconds"/> </long-running-threads> </default-workmanager> </subsystem> leads to : [Host Controller] Message: JBAS014724: Missing required attribute(s): POA_REQUEST_PROC_MAX_THREADS [Host Controller] at org.jboss.as.controller.parsing.ParseUtils.missingRequired(ParseUtils.java:134) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Host Controller] at org.jboss.as.jacorb.JacORBSubsystemParser.parseAttributes(JacORBSubsystemParser.java:683) [Host Controller] at org.jboss.as.jacorb.JacORBSubsystemParser.parsePOAConfig(JacORBSubsystemParser.java:399) [Host Controller] at org.jboss.as.jacorb.JacORBSubsystemParser.readElement_1_1(JacORBSubsystemParser.java:185) [Host Controller] at org.jboss.as.jacorb.JacORBSubsystemParser.readElement(JacORBSubsystemParser.java:91) [Host Controller] at org.jboss.as.jacorb.JacORBSubsystemParser.readElement(JacORBSubsystemParser.java:62) [Host Controller] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100) [staxmapper-1.0.0.Final.jar:1.0.0.Final] {noformat} -- 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

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1701) Add a --help command line switch to jboss-admin

by Thomas Diesler (JIRA)

Add a --help command line switch to jboss-admin ----------------------------------------------- Key: AS7-1701 URL: https://issues.jboss.org/browse/AS7-1701 Project: Application Server 7 Issue Type: Feature Request Components: CLI Reporter: Thomas Diesler Assignee: Alexey Loubyansky $ bin/jboss-admin.sh --help '--help' is not a valid operation name. I would have like to see that $ bin/jboss-admin.sh --connect is valid. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-9072) High level commands for common standalone mode tasks

by Brian Stansberry (JIRA)

High level commands for common standalone mode tasks ---------------------------------------------------- Key: JBAS-9072 URL: https://issues.jboss.org/browse/JBAS-9072 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assignee: Alexey Loubyansky Fix For: 7.0.0.Beta3 Identify and implement the high level commands we want to support for a standalone mode server. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
10
0 / 0

[JBoss JIRA] (AS7-3593) allow -ds.xml inside archives

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created AS7-3593: ---------------------------------------- Summary: allow -ds.xml inside archives Key: AS7-3593 URL: https://issues.jboss.org/browse/AS7-3593 Project: Application Server 7 Issue Type: Feature Request Reporter: Max Rydahl Andersen -- 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

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] (AS7-3588) Jboss can't inject a EJB reference

by Denis Kostousov (JIRA)

Denis Kostousov created AS7-3588: ------------------------------------ Summary: Jboss can't inject a EJB reference Key: AS7-3588 URL: https://issues.jboss.org/browse/AS7-3588 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.0.CR1b Environment: Fedora 16, % java -version java version "1.6.0_30" Java(TM) SE Runtime Environment (build 1.6.0_30-b12) Java HotSpot(TM) Client VM (build 20.5-b03, mixed mode, sharing) Reporter: Denis Kostousov Assignee: jaikiran pai I created a simple ear with ejb and war. The ejb module contains hello-world ejb (ejb "A"). The war module contains a REST-enabled ejb (ejb "B"). The ejb "B" has one @EJB-annotated field referring to EJB "A" and one REST-enabled method. This method proxies an invocation to ejb "B" method. I use utility "curl" for testing the application. Jboss reports an exception when I try to invoke the REST-enabled method. -- 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

14 years, 2 months

2
7
0 / 0

[JBoss JIRA] Created: (AS7-1034) ignore persistence unit definitions that have PersistenceUnitTransactionType = RESOURCE_LOCAL

by Scott Marlow (JIRA)

ignore persistence unit definitions that have PersistenceUnitTransactionType = RESOURCE_LOCAL --------------------------------------------------------------------------------------------- Key: AS7-1034 URL: https://issues.jboss.org/browse/AS7-1034 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate Affects Versions: 7.0.0.Beta3 Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
3
0 / 0

[JBoss JIRA] (AS7-3388) remove references to extended persistence context when passivating

by Scott Marlow (JIRA)

Scott Marlow created AS7-3388: --------------------------------- Summary: remove references to extended persistence context when passivating Key: AS7-3388 URL: https://issues.jboss.org/browse/AS7-3388 Project: Application Server 7 Issue Type: Task Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.1.0.Final -- 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

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] (AS7-3387) separation of passivation/replication operations for extended persistence context

by Scott Marlow (JIRA)

Scott Marlow created AS7-3387: --------------------------------- Summary: separation of passivation/replication operations for extended persistence context Key: AS7-3387 URL: https://issues.jboss.org/browse/AS7-3387 Project: Application Server 7 Issue Type: Task Components: Clustering, EJB Reporter: Scott Marlow Assignee: Paul Ferraro Fix For: 7.1.0.Final Currently, when the JPA extended persistence context is serializing, it is not known if passivation or cluster replication is occurring. This means that the extended persistence context will stay in memory. When ExtendedEntityManager.writeObject() is invoked, I would like a way to tell that the current thread is passivating versus cluster replicating. If this isn't going to happen, I'll look at alternatives. A quick rejection or response that this makes sense, would be welcome. -- 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

14 years, 2 months

1
2
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 February 2012