March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6778) Configure EJB3/MDB with an individual thread pool for each EJB.

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/AS7-6778?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on AS7-6778: ---------------------------------- The reason you see 90% of CPU cycles being spent in JBossThread.run() is that nearly all of our threads are JBossThreads, thus all work that the server does will ultimately show up as being in this method one way or another. It is not indicative of a problem - indeed if you saw 0% usage in JBossThread.run(), it would mean that the server isn't doing anything at all. > Configure EJB3/MDB with an individual thread pool for each EJB. > --------------------------------------------------------------- > > Key: AS7-6778 > URL: https://issues.jboss.org/browse/AS7-6778 > Project: Application Server 7 > Issue Type: Feature Request > Components: EJB > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Jeremy Whiting > Assignee: jaikiran pai > > For performance of an application to be scalable I need to configure sometimes a thread pool to an EJB. The pool is not shared with other EJB in the deployed application. > For example > PoolA - EJB Dog > PoolB - EJB Cat > To configure this the ability no define the thread pool name for an EJB. Rather than an EJB to the shared thread pool as it currently works. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-5884) CLONE - Deployment in a domain will be destroyed if there are multiple deplyments with the same content SHA1

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-5884?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-5884: ---------------------------------------------- Martin Simka <msimka(a)redhat.com> changed the Status of [bug 901159|https://bugzilla.redhat.com/show_bug.cgi?id=901159] from ON_QA to VERIFIED > CLONE - Deployment in a domain will be destroyed if there are multiple deplyments with the same content SHA1 > ------------------------------------------------------------------------------------------------------------ > > Key: AS7-5884 > URL: https://issues.jboss.org/browse/AS7-5884 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.3.Final (EAP) > Reporter: Wolf-Dieter Fink > Assignee: Kabir Khan > Priority: Critical > Labels: deployers, domain, eap, jboss > Fix For: EAP 6.1.0.Alpha (7.2.0.Final), 7.1.4.Final (EAP) > > > If a deployment in a domain is the same file, deployed with different names to different server-groups, it become the same SHA1. > In that case the stored content will not be updated and the <deployments> section become a new entry which is used by the second server group. > But if one of the deployments will be undeployed or updated the content is complete removed but the second deployment entry is still available. > The second deployment can be used as long as there is a action to it (e.g. restart). > In that case a FATAL error is thrown: > [Host Controller] 11:43:36,493 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("deployment" => "prod.ear")]) - failure description: "JBAS010876: No deployment content with hash 0807c2c28e5feebb8dfb905788e53b104ecb89fc is available in the deployment content repository for deployment 'prod.ear'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuraiton file and restart." > [Host Controller] 11:43:36,496 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010933: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-5884) CLONE - Deployment in a domain will be destroyed if there are multiple deplyments with the same content SHA1

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-5884?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-5884: ---------------------------------------------- Martin Simka <msimka(a)redhat.com> made a comment on [bug 901159|https://bugzilla.redhat.com/show_bug.cgi?id=901159] verified 6.1.0.ER3 > CLONE - Deployment in a domain will be destroyed if there are multiple deplyments with the same content SHA1 > ------------------------------------------------------------------------------------------------------------ > > Key: AS7-5884 > URL: https://issues.jboss.org/browse/AS7-5884 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.3.Final (EAP) > Reporter: Wolf-Dieter Fink > Assignee: Kabir Khan > Priority: Critical > Labels: deployers, domain, eap, jboss > Fix For: EAP 6.1.0.Alpha (7.2.0.Final), 7.1.4.Final (EAP) > > > If a deployment in a domain is the same file, deployed with different names to different server-groups, it become the same SHA1. > In that case the stored content will not be updated and the <deployments> section become a new entry which is used by the second server group. > But if one of the deployments will be undeployed or updated the content is complete removed but the second deployment entry is still available. > The second deployment can be used as long as there is a action to it (e.g. restart). > In that case a FATAL error is thrown: > [Host Controller] 11:43:36,493 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("deployment" => "prod.ear")]) - failure description: "JBAS010876: No deployment content with hash 0807c2c28e5feebb8dfb905788e53b104ecb89fc is available in the deployment content repository for deployment 'prod.ear'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuraiton file and restart." > [Host Controller] 11:43:36,496 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010933: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-5976) The command :reload does not check the new configuration, and will cause server crashes if that config is broken

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-5976?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-5976: ---------------------------------------------- Jakub Cechacek <jcechace(a)redhat.com> changed the Status of [bug 901192|https://bugzilla.redhat.com/show_bug.cgi?id=901192] from ON_QA to ASSIGNED > The command :reload does not check the new configuration, and will cause server crashes if that config is broken > ---------------------------------------------------------------------------------------------------------------- > > Key: AS7-5976 > URL: https://issues.jboss.org/browse/AS7-5976 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.2.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Brian Stansberry > Priority: Critical > Fix For: EAP 6.1.0.Alpha (7.2.0.Final) > > > The command :reload does not check the new configuration, and will cause server crashes if that config is broken -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-5976) The command :reload does not check the new configuration, and will cause server crashes if that config is broken

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-5976?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-5976: ---------------------------------------------- Jakub Cechacek <jcechace(a)redhat.com> made a comment on [bug 901192|https://bugzilla.redhat.com/show_bug.cgi?id=901192] Unless I'm doing something wrong the behavior in ER3 is exactly the same as described in bug report. After performing /host=master:reload with the corrupted host.xml server process will quit with ConfigurationPersistenceException. Changing status back to assigned > The command :reload does not check the new configuration, and will cause server crashes if that config is broken > ---------------------------------------------------------------------------------------------------------------- > > Key: AS7-5976 > URL: https://issues.jboss.org/browse/AS7-5976 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.2.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Brian Stansberry > Priority: Critical > Fix For: EAP 6.1.0.Alpha (7.2.0.Final) > > > The command :reload does not check the new configuration, and will cause server crashes if that config is broken -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6814) JBOSS 7.1.1 server /tmp/vfs folder gets full

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/AS7-6814?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on AS7-6814: ---------------------------------- Is this bug a duplicate of AS7-1805? > JBOSS 7.1.1 server /tmp/vfs folder gets full > -------------------------------------------- > > Key: AS7-6814 > URL: https://issues.jboss.org/browse/AS7-6814 > Project: Application Server 7 > Issue Type: Bug > Components: JPA / Hibernate, JSF > Affects Versions: 7.1.1.Final > Reporter: Mahesh Khatal > Assignee: David Lloyd > -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6814) JBOSS 7.1.1 server /tmp/vfs folder gets full

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/AS7-6814?page=com.atlassian.jira.plugin.s... ] David Lloyd updated AS7-6814: ----------------------------- Due Date: 5/Apr/13 Assignee: David Lloyd (was: Scott Marlow) Do you have more information? A reproducer? A patch? Any reason to assume that your problem is related to JPA/Hibernate or JSF? > JBOSS 7.1.1 server /tmp/vfs folder gets full > -------------------------------------------- > > Key: AS7-6814 > URL: https://issues.jboss.org/browse/AS7-6814 > Project: Application Server 7 > Issue Type: Bug > Components: JPA / Hibernate, JSF > Affects Versions: 7.1.1.Final > Reporter: Mahesh Khatal > Assignee: David Lloyd > -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6694) Add attributes to "RemoteConnectionFactory" to make it ready for failover in HA profiles

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6694?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6694: ---------------------------------------------- Miroslav Novak <mnovak(a)redhat.com> made a comment on [bug 919016|https://bugzilla.redhat.com/show_bug.cgi?id=919016] Verified in EAP 6.1.0.ER3. Thanks Jeff! > Add attributes to "RemoteConnectionFactory" to make it ready for failover in HA profiles > ---------------------------------------------------------------------------------------- > > Key: AS7-6694 > URL: https://issues.jboss.org/browse/AS7-6694 > Project: Application Server 7 > Issue Type: Feature Request > Components: JMS > Affects Versions: 7.1.3.Final (EAP) > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > At this moment "RemoteConnectionFactory" configured in messaging subsystem in standalone-full-ha.xml or domain.xml in "full-ha" profile is not ready to failover by default. Please change: > <connection-factory name="RemoteConnectionFactory"> > <connectors> > <connector-ref connector-name="netty"/> > </connectors> > <entries> > <entry name="java:jboss/exported/jms/RemoteConnectionFactory"/> > </entries> > </connection-factory> > to: > <connection-factory name="RemoteConnectionFactory"> > <connectors> > <connector-ref connector-name="netty"/> > </connectors> > <entries> > <entry name="java:jboss/exported/jms/RemoteConnectionFactory"/> > </entries> > <ha>true</ha> > <block-on-acknowledge>true</block-on-acknowledge> > <retry-interval>1000</retry-interval> > <retry-interval-multiplier>1.0</retry-interval-multiplier> > <reconnect-attempts>-1</reconnect-attempts> > </connection-factory> > This will guarantee that clients using this connection factory will failover to backup. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6694) Add attributes to "RemoteConnectionFactory" to make it ready for failover in HA profiles

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6694?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6694: ---------------------------------------------- Miroslav Novak <mnovak(a)redhat.com> changed the Status of [bug 919016|https://bugzilla.redhat.com/show_bug.cgi?id=919016] from ON_QA to VERIFIED > Add attributes to "RemoteConnectionFactory" to make it ready for failover in HA profiles > ---------------------------------------------------------------------------------------- > > Key: AS7-6694 > URL: https://issues.jboss.org/browse/AS7-6694 > Project: Application Server 7 > Issue Type: Feature Request > Components: JMS > Affects Versions: 7.1.3.Final (EAP) > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > At this moment "RemoteConnectionFactory" configured in messaging subsystem in standalone-full-ha.xml or domain.xml in "full-ha" profile is not ready to failover by default. Please change: > <connection-factory name="RemoteConnectionFactory"> > <connectors> > <connector-ref connector-name="netty"/> > </connectors> > <entries> > <entry name="java:jboss/exported/jms/RemoteConnectionFactory"/> > </entries> > </connection-factory> > to: > <connection-factory name="RemoteConnectionFactory"> > <connectors> > <connector-ref connector-name="netty"/> > </connectors> > <entries> > <entry name="java:jboss/exported/jms/RemoteConnectionFactory"/> > </entries> > <ha>true</ha> > <block-on-acknowledge>true</block-on-acknowledge> > <retry-interval>1000</retry-interval> > <retry-interval-multiplier>1.0</retry-interval-multiplier> > <reconnect-attempts>-1</reconnect-attempts> > </connection-factory> > This will guarantee that clients using this connection factory will failover to backup. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6619) Management API for Datasources subsystem is missing some properties

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6619?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6619: ---------------------------------------------- Zbyněk Roubalík <zroubali(a)redhat.com> changed the Status of [bug 915288|https://bugzilla.redhat.com/show_bug.cgi?id=915288] from ON_QA to VERIFIED > Management API for Datasources subsystem is missing some properties > ------------------------------------------------------------------- > > Key: AS7-6619 > URL: https://issues.jboss.org/browse/AS7-6619 > Project: Application Server 7 > Issue Type: Bug > Components: JCA > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Zbyněk Roubalík > Assignee: Stefano Maestri > > Some properties which were present in previous versions of AS7 are missing in current release: > Parameter driver-name for operation 'get-installed-driver' is no longer available. > These value-type for 'reply-properties' for operation 'get-installed-driver' are no longer available: [jdbc-compliant, module-slot, driver-class-name, driver-module-name] -- 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

12 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2013