August 2012 - jboss-jira - Jboss List Archives

[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

13 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

13 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

13 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

13 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

13 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

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5044) -Djboss.server.base.dir is ignored when set via -

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5044: ------------------------------------- Summary: -Djboss.server.base.dir is ignored when set via - Key: AS7-5044 URL: https://issues.jboss.org/browse/AS7-5044 Project: Application Server 7 Issue Type: Feature Request Reporter: Brian Stansberry -- 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

13 years, 9 months

2
4
0 / 0

[JBoss JIRA] (AS7-5297) IronJacamar 1.0.12.Final

by Jesper Pedersen (JIRA)

Jesper Pedersen created AS7-5297: ------------------------------------ Summary: IronJacamar 1.0.12.Final Key: AS7-5297 URL: https://issues.jboss.org/browse/AS7-5297 Project: Application Server 7 Issue Type: Component Upgrade Reporter: Jesper Pedersen Priority: Critical Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 -- 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

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] (HIBERNATE-134) Infinispan custom cache command factory not installed error during app deployment

by Dmitry Chuiko (JIRA)

Dmitry Chuiko created HIBERNATE-134: --------------------------------------- Summary: Infinispan custom cache command factory not installed error during app deployment Key: HIBERNATE-134 URL: https://issues.jboss.org/browse/HIBERNATE-134 Project: Hibernate Integration Issue Type: Bug Environment: Ubuntu 12.04, JBoss AS 7.1.2, Hibernate 4.1.2, Infinispan 5.1.4 Reporter: Dmitry Chuiko Assignee: Steve Ebersole We use Infinispan as 2LC for Hibernate in a clustered configuration under JBoss 7. So {{persistence.xml}} contains the following line: {code:xml}<property name="hibernate.cache.region.factory_class" value="org.hibernate.cache.infinispan.InfinispanRegionFactory"/>{code}. The following error occurs during app deployment: {noformat}12:04:52,859 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-14) MSC00001: Failed to start service jboss.persistenceunit."MOYsklad.ear/sklad-base.jar#MOYsklad": org.jboss.msc.service.StartException in service jboss.persistenceunit."MOYsklad.ear/sklad-base.jar#MOYsklad": Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05] Caused by: javax.persistence.PersistenceException: [PersistenceUnit: MOYsklad] Unable to build EntityManagerFactory at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:915) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:890) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:74) at org.hibernate.ejb.HibernatePersistenceLognex.createContainerEntityManagerFactory(HibernatePersistenceLognex.java:16) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] ... 3 more Caused by: org.hibernate.cache.CacheException: Infinispan custom cache command factory not installed (possibly because the classloader where Infinispan lives couldn't find the Hibernate Infinispan cache provider) at org.hibernate.cache.infinispan.InfinispanRegionFactory.getCacheCommandFactory(InfinispanRegionFactory.java:500) at org.hibernate.cache.infinispan.InfinispanRegionFactory.startRegion(InfinispanRegionFactory.java:379) at org.hibernate.cache.infinispan.InfinispanRegionFactory.buildEntityRegion(InfinispanRegionFactory.java:212) at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:347) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1741) at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:93) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:905) ... 10 more {noformat} This issue takes place because context {{ClassLoader}} is substituted in {{org.hibernate.ejb.Ejb3Configuration#configure}}. So Infinispan can not find {{org.infinispan.commands.module.ModuleCommandExtensions}} realization from {{hibernate-infinispan}} module in {{org.infinispan.util.ModuleProperties#loadModuleCommandHandlers}} 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

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] (JBEE-118) JSTL uses wrong version of xalan

by Rafael Benevides (JIRA)

Rafael Benevides created JBEE-118: ------------------------------------- Summary: JSTL uses wrong version of xalan Key: JBEE-118 URL: https://issues.jboss.org/browse/JBEE-118 Project: JBoss JavaEE Spec APIs Issue Type: Bug Reporter: Rafael Benevides Assignee: Paul Gier http://mvnrepository.com/artifact/org.jboss.spec.javax.servlet.jstl/jboss... shows a dependency to xalan:xalan:2.7.1.jbossorg-2 that is not on central repositories. It should be 2.7.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

13 years, 9 months

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