August 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (EJBTHREE-2275) PreDestroy lifecycle callback not called when Activated EJB3 SFSB removal timeout is reached

by Brad Maxwell (JIRA)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-879) use-strict-min should trigger prefill of pools

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-879: ------------------------------------- Summary: use-strict-min should trigger prefill of pools Key: JBJCA-879 URL: https://issues.jboss.org/browse/JBJCA-879 Project: IronJacamar Issue Type: Bug Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen -- 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

11 years, 9 months

1
2
0 / 0

[JBoss JIRA] (REMJMX-12) Allow for protocol versions to be excluded client and server side

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-12?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated REMJMX-12: ----------------------------------- Fix Version/s: 1.0.5.CR1 (was: 1.0.4.Final) > Allow for protocol versions to be excluded client and server side > ----------------------------------------------------------------- > > Key: REMJMX-12 > URL: https://issues.jboss.org/browse/REMJMX-12 > Project: Remoting JMX > Issue Type: Task > Components: Connection > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.0.5.CR1 > > > Once we start supporting multiple versions of the protocols we should also allow version to be excluded client and server side. > This will mean if a version is identified as being problematic is can be excluded to force the use of a previous version. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-48) Release Remoting JMX 1.0.4

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-48: -------------------------------------- Summary: Release Remoting JMX 1.0.4 Key: REMJMX-48 URL: https://issues.jboss.org/browse/REMJMX-48 Project: Remoting JMX Issue Type: Task Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.4.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

11 years, 9 months

1
1
0 / 0

[JBoss JIRA] (JBRULES-3331) For generic moves, provide option to disable them under certain conditions

by Lukáš Petrovický (Created) (JIRA)

For generic moves, provide option to disable them under certain conditions -------------------------------------------------------------------------- Key: JBRULES-3331 URL: https://issues.jboss.org/browse/JBRULES-3331 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Affects Versions: 5.4.0.Beta1 Reporter: Lukáš Petrovický Assignee: Mark Proctor This feature would be done for the same purpose as JBRULES-3330 and also implemented in very much the same way - the Move.isMoveDoable() checks for the existence of any filters and runs all of them. If any of them returns false, the move is not doable. Perhaps JBRULES-3330 and this one could even share the interface - MoveFilter.filter(Solution s, Move m) and newly added MoveFilter.isMoveDoable(Move m). -- 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

11 years, 9 months

2
3
0 / 0

[JBoss JIRA] (JBRULES-3371) Generic move factories should be able to scale to more moves than the memory can accomodate and still support random selection

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created JBRULES-3371: ----------------------------------------- Summary: Generic move factories should be able to scale to more moves than the memory can accomodate and still support random selection Key: JBRULES-3371 URL: https://issues.jboss.org/browse/JBRULES-3371 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Components: drools-planner Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet -- 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

11 years, 9 months

1
4
0 / 0

[JBoss JIRA] (JBLOGGING-82) Relicense logging code base to ASL2.0

by Thomas Diesler (JIRA)

Thomas Diesler created JBLOGGING-82: --------------------------------------- Summary: Relicense logging code base to ASL2.0 Key: JBLOGGING-82 URL: https://issues.jboss.org/browse/JBLOGGING-82 Project: JBoss Logging Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: David Lloyd The OSGi Repository RI (jbosgi-repository) must be licensed ASL2.0 in order to get accepted by the Alliance. With it all its dependencies need to be available under this license too. -- 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

11 years, 9 months

2
3
0 / 0

[JBoss JIRA] (AS7-5298) Provide an expression manager within console

by Heiko Braun (JIRA)

Heiko Braun created AS7-5298: -------------------------------- Summary: Provide an expression manager within console Key: AS7-5298 URL: https://issues.jboss.org/browse/AS7-5298 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.Alpha1 Based on AS7-2139 to resolve expression values -- 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

11 years, 9 months

1
3
0 / 0

[JBoss JIRA] (AS7-5282) Allow multiple module dirs: -Dmodule.path=/foo/modules:/bar/modules

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-5282: --------------------------------- Summary: Allow multiple module dirs: -Dmodule.path=/foo/modules:/bar/modules Key: AS7-5282 URL: https://issues.jboss.org/browse/AS7-5282 Project: Application Server 7 Issue Type: Enhancement Components: Class Loading Affects Versions: 7.1.2.Final (EAP) Reporter: Ondrej Zizka Assignee: David Lloyd There are use cases when possibility to load modules from multiple root dirs would be handy. For one, the testsuite uses ${jboss.dist}/modules; but some tests add modules, which changes the referred AS directory's content. -- 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

11 years, 9 months

3
4
0 / 0

[JBoss JIRA] (AS7-5305) CLONE - Default value of id-cache-size attribute is potencially dangerous when very small messages are used

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-5305: -------------------------------- Summary: CLONE - Default value of id-cache-size attribute is potencially dangerous when very small messages are used Key: AS7-5305 URL: https://issues.jboss.org/browse/AS7-5305 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.1.2.Final (EAP) Reporter: Jeff Mesnil Assignee: Clebert Suconic Fix For: 7.1.3.Final (EAP) Hi, I hit an issue with HornetQ core bridges. I tried test scenario with 4 nodes where: 1) there are two clusters A and B (each contains two nodes) 2) there is hornetq core bridge configured from cluster A to cluster B (A1 -> B1, A2 -> B2) During sending messages (30KB ByteMessages) to A1 and reading them from B2, node A2 was killed and started a few times. In the end there were duplicated messages. Problem was in low value of id-cache-size attribute which is 2000 by default and confirmation-window-size which is for bridges (1024 * 1024) bytes. Can be default value of id-cache-size increased so we can avoid this situation? This is potentially dangerous and hard for admins to realize before the problem occurs. -- 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

11 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2012