January 2012 - jboss-jira - Jboss List Archives

[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] 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] 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

[JBoss JIRA] Created: (JBAS-9049) Need way to override the boot.log in start scripts

by Scott Stark (JIRA)

Need way to override the boot.log in start scripts -------------------------------------------------- Key: JBAS-9049 URL: https://issues.jboss.org/browse/JBAS-9049 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Logging Affects Versions: 7.0.0.Beta1 Reporter: Scott Stark Assignee: David Lloyd We need the ability to specify the location of the boot.log. Right now the boot.log location is specified via the org.jboss.boot.log.file java system property, but this is always set to $JBOSS_HOME/standalone/log/boot.log in the server start scripts. This should either not be set and simply default to $JBOSS_HOME/standalone/log/boot.log when unset so that it may be passed into the jvm, or, we need a JBOSS_BOOT_LOG env property that can override this value along the line of: if [ "x$JBOSS_BOOT_LOG" = "x" ]; then JBOSS_BOOT_LOG="$JBOSS_HOME/standalone/log/boot.log" fi while true; do if [ "x$LAUNCH_JBOSS_IN_BACKGROUND" = "x" ]; then # Execute the JVM in the foreground eval \"$JAVA\" $JAVA_OPTS \ \"-Dorg.jboss.boot.log.file=$JBOSS_BOOT_LOG\" \ ... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
9
0 / 0

[JBoss JIRA] Created: (JBEE-22) Add jboss-jaxrs-api_1.1_spec

by Shelly McGowan (JIRA)

Add jboss-jaxrs-api_1.1_spec ---------------------------- Key: JBEE-22 URL: https://jira.jboss.org/jira/browse/JBEE-22 Project: JBoss JavaEE APIs Issue Type: Sub-task Reporter: Shelly McGowan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
9
0 / 0

[JBoss JIRA] (AS7-3291) EnversIntegrator is always detected by default while initializing Serviceregistry using Native Hibernate API causing a MappingException even when Envers is not used

by Madhumita Sadhukhan (JIRA)

Madhumita Sadhukhan created AS7-3291: ---------------------------------------- Summary: EnversIntegrator is always detected by default while initializing Serviceregistry using Native Hibernate API causing a MappingException even when Envers is not used Key: AS7-3291 URL: https://issues.jboss.org/browse/AS7-3291 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate, Test Suite Affects Versions: 7.1.0.CR1 Reporter: Madhumita Sadhukhan Assignee: Strong Liu Please find the hibernate native api tests located at : https://github.com/madhumita12/jboss-as/tree/master/testsuite/integration... The tests are working fine with a workaround I have applied to them,hence I would like to request you to run the HibernateNativeAPITransactionTestCase locally to see the issue I have been mentioning before. Also , please comment the workaround as follows before running the test in order to hit around the issue: In file SFSBHibernateTransaction please comment: // configuration.setProperty("hibernate.listeners.envers.autoRegister", "false"); I am simply initialising BootstrapServiceRegistryBuilder and then passing the configuration properties to it to initialize the ServiceRegistry. I am not using any AuditListner or @Audited anywhere in my configuration/code. However when I initialize ServiceRegistry it by default AUTORegisters/detects the EnversIntegrator which tries to initialise AuditListner via Auditconfiguration and crashes. The workaround to this is to set the AUTO_REGISTER in EnversIntegrator to false as above. Stacktrace: ... 139 more Caused by: org.hibernate.MappingException: Unable to create AuditStrategy[org.hibernate.envers.strategy.DefaultAuditStrategy] instance. at org.hibernate.envers.configuration.AuditConfiguration.initializeAuditStrategy(AuditConfiguration.java:114) at org.hibernate.envers.configuration.AuditConfiguration.<init>(AuditConfiguration.java:101) at org.hibernate.envers.configuration.AuditConfiguration.getFor(AuditConfiguration.java:135) at org.hibernate.envers.event.EnversIntegrator.integrate(EnversIntegrator.java:63) at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:295) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1737) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] at org.jboss.as.test.integration.hibernate.SFSBHibernateTransaction.setupConfig(SFSBHibernateTransaction.java:81) [beans.jar:] -- 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-2530) Arquillian in AS7 is missing support for byteman

by Miroslav Novak (Created) (JIRA)

Arquillian in AS7 is missing support for byteman ------------------------------------------------ Key: AS7-2530 URL: https://issues.jboss.org/browse/AS7-2530 Project: Application Server 7 Issue Type: Feature Request Components: Test Suite Affects Versions: 7.1.0.Alpha1 Reporter: Miroslav Novak Assignee: Andrew Rubinger Fix For: 7.1.0.Beta1 Hi, I tried to implement test case which is using byteman but without success. It seems that arquillian in AS7 doesn't have support for byteman. There are missing classes. Example test case: https://github.com/aslakknutsen/arquillian/blob/ARQ-348/frameworks/bytema... Missing classes: org.jboss.arquillian.framework.byteman.api.BMRule; org.jboss.arquillian.framework.byteman.api.BMRules; Do we have a way how to make it work? Thank you, Mirek -- 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

9
11
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 January 2012