March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6549) Remote JNDI is not working with a HornetQ-only JMS bridge

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6549?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6549: ---------------------------------------------- nziakova <nziakova(a)redhat.com> changed the Status of [bug 912653|https://bugzilla.redhat.com/show_bug.cgi?id=912653] from ON_QA to ASSIGNED > Remote JNDI is not working with a HornetQ-only JMS bridge > --------------------------------------------------------- > > Key: AS7-6549 > URL: https://issues.jboss.org/browse/AS7-6549 > Project: Application Server 7 > Issue Type: Feature Request > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > The jms-bridge can be used to bridge a hornetq server to another and should work by specifying to use the org.hornetq.module to load the JMS implementation classes. > However, this fails because this module does not have access to the JBoss remote-naming module that is required to connect to remote JBoss JNDI server. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6549) Remote JNDI is not working with a HornetQ-only JMS bridge

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6549?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6549: ---------------------------------------------- nziakova <nziakova(a)redhat.com> made a comment on [bug 912653|https://bugzilla.redhat.com/show_bug.cgi?id=912653] JMS bridge still could not be started. See configuration and log of both source and target servers in attachment. > Remote JNDI is not working with a HornetQ-only JMS bridge > --------------------------------------------------------- > > Key: AS7-6549 > URL: https://issues.jboss.org/browse/AS7-6549 > Project: Application Server 7 > Issue Type: Feature Request > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > The jms-bridge can be used to bridge a hornetq server to another and should work by specifying to use the org.hornetq.module to load the JMS implementation classes. > However, this fails because this module does not have access to the JBoss remote-naming module that is required to connect to remote JBoss JNDI server. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6615) Invalid definition for HC root resource remote domain controller

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/AS7-6615?page=com.atlassian.jira.plugin.s... ] Kabir Khan edited comment on AS7-6615 at 3/28/13 8:44 AM: ---------------------------------------------------------- I have done the definition part as part of my work on "better ignoring of non-affected slave data" AS7-6808 was (Author: kabirkhan): I have done the definition part as part of my work on "better ignoring of non-affected slave data" > Invalid definition for HC root resource remote domain controller > ---------------------------------------------------------------- > > Key: AS7-6615 > URL: https://issues.jboss.org/browse/AS7-6615 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Brian Stansberry > Assignee: Kabir Khan > Fix For: 8.0.0.Alpha1 > > > HostResourceDefinition.DC_REMOTE does not include the security-realm and username fields. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1018) code generation for eclipse plugin about JCA 1.7

by Jeff Zhang (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1018?page=com.atlassian.jira.plugin... ] Jeff Zhang reassigned JBJCA-1018: --------------------------------- Assignee: Lin Gao (was: Jeff Zhang) > code generation for eclipse plugin about JCA 1.7 > ------------------------------------------------ > > Key: JBJCA-1018 > URL: https://issues.jboss.org/browse/JBJCA-1018 > Project: IronJacamar > Issue Type: Task > Components: Eclipse > Affects Versions: 1.1.0.Beta4 > Reporter: Jeff Zhang > Assignee: Lin Gao > Fix For: 1.1.0.Beta5 > > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1943) HeuristicMixedException gets thrown if the destination has reached its maxsize

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1943?page=com.atlassian.jira.... ] Yong Hao Gao closed JBMESSAGING-1943. ------------------------------------- Resolution: Done > HeuristicMixedException gets thrown if the destination has reached its maxsize > ------------------------------------------------------------------------------ > > Key: JBMESSAGING-1943 > URL: https://issues.jboss.org/browse/JBMESSAGING-1943 > Project: JBoss Messaging > Issue Type: Bug > Components: Messaging Core > Affects Versions: 1.4.8.SP5 > Environment: JBoss-EAP-5.1.2, JBossMessaging-1.4.8-SP5, JBossTS-4.6.1GA-CP11 +JBTM-842 &J BTM-924 > Reporter: Tyronne Wickramarathne > Assignee: Yong Hao Gao > Labels: JMS, Transactions > Fix For: 1.4.8.SP10 > > > The message producer throws a HeuristicMixedException when trying to send messages to a destination which has reached its maxsize. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1943) HeuristicMixedException gets thrown if the destination has reached its maxsize

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1943?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1943: -------------------------------------- Fix Version/s: 1.4.8.SP10 > HeuristicMixedException gets thrown if the destination has reached its maxsize > ------------------------------------------------------------------------------ > > Key: JBMESSAGING-1943 > URL: https://issues.jboss.org/browse/JBMESSAGING-1943 > Project: JBoss Messaging > Issue Type: Bug > Components: Messaging Core > Affects Versions: 1.4.8.SP5 > Environment: JBoss-EAP-5.1.2, JBossMessaging-1.4.8-SP5, JBossTS-4.6.1GA-CP11 +JBTM-842 &J BTM-924 > Reporter: Tyronne Wickramarathne > Assignee: Yong Hao Gao > Labels: JMS, Transactions > Fix For: 1.4.8.SP10 > > > The message producer throws a HeuristicMixedException when trying to send messages to a destination which has reached its maxsize. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6665) Update modules for Hibernate Validator and Bean Validation API

by Gunnar Morling (JIRA)

[ https://issues.jboss.org/browse/AS7-6665?page=com.atlassian.jira.plugin.s... ] Gunnar Morling updated AS7-6665: -------------------------------- Summary: Update modules for Hibernate Validator and Bean Validation API (was: Avoid creation of ConstraintMapping in LazyValidatorFactory) > Update modules for Hibernate Validator and Bean Validation API > -------------------------------------------------------------- > > Key: AS7-6665 > URL: https://issues.jboss.org/browse/AS7-6665 > Project: Application Server 7 > Issue Type: Task > Components: JPA / Hibernate > Affects Versions: 7.1.3.Final (EAP) > Reporter: Gunnar Morling > Assignee: Scott Marlow > Fix For: 8.0.0.Alpha1 > > > As discussed with @smarlow, the call to {{new ConstraintMapping()}} in [LazyValidatorFactory|https://github.com/jbossas/jboss-as/blob/master/ee/s...] needs to be removed as it makes it impossible to use Hibernate Validator 5 with AS. > I'm going to create a pull request for this. -- 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, 1 month

1
0
0 / 0

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

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/AS7-6778?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on AS7-6778: ----------------------------------- By the way, if there's a specific example/usecase you are stuck with or are having problems trying to improve performance with, I would like to understand that and see if adding this feature will help solve it. I don't mind adding this feature if it's going to solve those requirements. > 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

13 years, 1 month

1
0
0 / 0

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

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/AS7-6778?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on AS7-6778: ----------------------------------- I'm sorry, I'm still not sure what's being asked for here. >> Furthermore, the thread pools could be assigned to specific components, otherwise they will use the default one. I don't understand this. Local invocations will keep using the originating thread. Assigning a thread pool to a component wouldn't have any affect on that. >> We are having some bottleneck when increasing the threads for each components. I think we should start looking at what those problems are and then figure out if adding some new feature is relevant. > 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-72) Potential memory leak in StatelessKnowledgeSessionImpl#execute when fireAllRules throwing RuntimeException

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-72?page=com.atlassian.jira.plugin.... ] Mario Fusco resolved DROOLS-72. ------------------------------- Fix Version/s: 5.6 6.0.0.Alpha1 Resolution: Done > Potential memory leak in StatelessKnowledgeSessionImpl#execute when fireAllRules throwing RuntimeException > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-72 > URL: https://issues.jboss.org/browse/DROOLS-72 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5 > Reporter: Trung Nguyen > Assignee: Mario Fusco > Fix For: 5.6, 6.0.0.Alpha1 > > > when {{ksession.fireAllRules()}} throws RuntimeException, it cause {{ksession}} never gets released. > {code:lang=java} > public void execute(Object object) { > StatefulKnowledgeSession ksession = newWorkingMemory(); > ksession.insert( object ); > ksession.fireAllRules( ); > ksession.dispose(); > } > public void execute(Iterable objects) { > StatefulKnowledgeSession ksession = newWorkingMemory(); > for ( Object object : objects ) { > ksession.insert( object ); > } > ksession.fireAllRules( ); > ksession.dispose(); > } > {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, 1 month

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 March 2013