August 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2962) Knowledge Agent rebuilding KnowledgeBase with scanner/notifier does not work with declared facts

by Ross Hall (JIRA)

Knowledge Agent rebuilding KnowledgeBase with scanner/notifier does not work with declared facts ------------------------------------------------------------------------------------------------ Key: JBRULES-2962 URL: https://issues.jboss.org/browse/JBRULES-2962 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.2.0.M1, 5.1.1.FINAL Reporter: Ross Hall Assignee: Mark Proctor When reloading rules in a KnowledgeAgent declared facts will cause ClassCastExceptions when new-instance is set to false. When new-instance is set to true, the KnowledgeBase is rebuilt, however declared facts are not recognized and associated rules will not fire. Rules not using declared facts will fire normally. Using POJOs works fine. In both cases the KnowledgeAgent will build the rule base the first time, the issue only seems to occur when the changeset resources are modified and are detected by the resource notifier and scanner. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

8
15
0 / 0

[JBoss JIRA] (JBRULES-3597) KnowledgeAgent can't incrementally load resources with equivalent declared types

by Davide Sottara (JIRA)

Davide Sottara created JBRULES-3597: --------------------------------------- Summary: KnowledgeAgent can't incrementally load resources with equivalent declared types Key: JBRULES-3597 URL: https://issues.jboss.org/browse/JBRULES-3597 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.4.0.Final Reporter: Davide Sottara Assignee: Davide Sottara Priority: Blocker Fix For: 5.5.0.Beta1 Assume a KA is created and configured to load its KB incrementally. Assume the KA will load two resources in two different steps. If the two DRL resources contain the same type definition, two typeDeclarations will be created. The first will be "novel" and used to compile the first DRL. The second will simply refer the already loaded class. (Notice that the PackageBuilder will not allow the two definitions to be different) The rulebase, however, can't merge the two compiled packages because the "novel" attribute is different and apparently incompatible. -- 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, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1613) NPE in TranslatingSuspendableChannel.scheduleReadTask

by Ondrej Zizka (JIRA)

NPE in TranslatingSuspendableChannel.scheduleReadTask ----------------------------------------------------- Key: AS7-1613 URL: https://issues.jboss.org/browse/AS7-1613 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.0.1.Final Reporter: Ondrej Zizka Assignee: Alexey Loubyansky Happened after a while of inactivity (if that matters). [standalone@localhost:9999 interface=public] cd .. [standalone@localhost:9999 /] cd .. [standalone@localhost:9999 /] ls extension core-service path subsystem system-property deployment interface socket-binding-group [standalone@localhost:9999 /] Exception in thread "pool-1-thread-21" java.lang.NullPointerException at org.xnio.channels.TranslatingSuspendableChannel.scheduleReadTask(TranslatingSuspendableChannel.java:253) at org.xnio.channels.TranslatingSuspendableChannel.resumeReads(TranslatingSuspendableChannel.java:233) at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication$2.run(ClientConnectionOpenListener.java:498) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
4
0 / 0

[JBoss JIRA] (JBRULES-3594) Unable to extend a declared class if that class has a parent and is declared in another package

by Davide Sottara (JIRA)

Davide Sottara created JBRULES-3594: --------------------------------------- Summary: Unable to extend a declared class if that class has a parent and is declared in another package Key: JBRULES-3594 URL: https://issues.jboss.org/browse/JBRULES-3594 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.4.0.Final Reporter: Davide Sottara Assignee: Davide Sottara Priority: Minor Fix For: 5.5.0.Beta1 -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] (AS7-5308) InfinispanBackingCacheEntryStore triggers cache configuration adaptation per invocation

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-5308: --------------------------------- Summary: InfinispanBackingCacheEntryStore triggers cache configuration adaptation per invocation Key: AS7-5308 URL: https://issues.jboss.org/browse/AS7-5308 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.2.Final (EAP) Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Critical Fix For: 7.1.3.Final (EAP) InfinispanBackingCacheEntryStore.acquireSessionOwnership(...) includes a call to Cache.getCacheConfiguration(...). In Infinispan 5.1.x, this triggers a call to LegacyConfigurationAdaptor.adapt(...) which not only adds an unnecessary performance hit, but adds INFO logging noise. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBBUILD-721) Thirdparty Rebuild of JAXB 2.2.5

by Paul Gier (JIRA)

Paul Gier created JBBUILD-721: --------------------------------- Summary: Thirdparty Rebuild of JAXB 2.2.5 Key: JBBUILD-721 URL: https://issues.jboss.org/browse/JBBUILD-721 Project: JBoss Build System Issue Type: Task Components: Thirdparty Builds Reporter: Paul Gier Assignee: Paul Gier Fix For: Thirdparty Builds 2012 -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] (AS7-2022) TS: Coverage reports

by Ondrej Zizka (Created) (JIRA)

TS: Coverage reports -------------------- Key: AS7-2022 URL: https://issues.jboss.org/browse/AS7-2022 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Affects Versions: 7.1.0.Alpha1 Reporter: Ondrej Zizka Assignee: Ondrej Zizka There are some coverage jobs in Hudson: * Aggregated: https://hudson.qa.jboss.com/hudson//view/JBoss%20AS/job/jboss-as7-code-co... * Per module: https://hudson.qa.jboss.com/hudson/view/JBoss AS/job/JBoss-AS-7.0.x-unit-coverage/ -- 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, 11 months

9
42
0 / 0

[JBoss JIRA] (AS7-4704) Cannot deploy exploded .jar inside exploded .war

by Adrian Mitev (JIRA)

Adrian Mitev created AS7-4704: --------------------------------- Summary: Cannot deploy exploded .jar inside exploded .war Key: AS7-4704 URL: https://issues.jboss.org/browse/AS7-4704 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Reporter: Adrian Mitev Hi all! I deploy my app as an exploded war there in WEB-INF/lib there is a jar deployed as exploded folder. However when the server starts I get the following exception: 17:59:15,423 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."MyApp.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."MyApp.war".STRUCTURE: Failed to process phase STRUCTURE of deployment "MyApp.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] 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] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_24] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_24] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018037: Failed to process WEB-INF/lib: "/C:/Users/amitev/Desktop/mse2012/jboss-as-7.1.1.Final/standalone/deployments/MyApp.war/WEB-INF/lib/Module1.jar" at org.jboss.as.web.deployment.WarStructureDeploymentProcessor.deploy(WarStructureDeploymentProcessor.java:120) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] ... 5 more Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018037: Failed to process WEB-INF/lib: "/C:/Users/amitev/Desktop/mse2012/jboss-as-7.1.1.Final/standalone/deployments/MyApp.war/WEB-INF/lib/Module1.jar" at org.jboss.as.web.deployment.WarStructureDeploymentProcessor.createWebInfLibResources(WarStructureDeploymentProcessor.java:175) at org.jboss.as.web.deployment.WarStructureDeploymentProcessor.createResourceRoots(WarStructureDeploymentProcessor.java:153) at org.jboss.as.web.deployment.WarStructureDeploymentProcessor.deploy(WarStructureDeploymentProcessor.java:114) ... 6 more Caused by: java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) [rt.jar:1.6.0_24] at java.util.zip.ZipFile.<init>(ZipFile.java:127) [rt.jar:1.6.0_24] at java.util.jar.JarFile.<init>(JarFile.java:135) [rt.jar:1.6.0_24] at java.util.jar.JarFile.<init>(JarFile.java:99) [rt.jar:1.6.0_24] at org.jboss.vfs.spi.JavaZipFileSystem.<init>(JavaZipFileSystem.java:97) at org.jboss.vfs.spi.JavaZipFileSystem.<init>(JavaZipFileSystem.java:83) at org.jboss.vfs.VFS.mountZip(VFS.java:408) at org.jboss.vfs.VFS.mountZip(VFS.java:434) at org.jboss.as.web.deployment.WarStructureDeploymentProcessor.createWebInfLibResources(WarStructureDeploymentProcessor.java:170) ... 8 more -- 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, 11 months

4
11
0 / 0

[JBoss JIRA] (AS7-5304) NPE in org.jboss.as.weld.deployment.processors.BeanArchiveProcessor.createBeanDeploymentArchive deploying war with WEB-INF/beans.xml but no WEB-INF/classes

by Marek Schmidt (JIRA)

Marek Schmidt created AS7-5304: ---------------------------------- Summary: NPE in org.jboss.as.weld.deployment.processors.BeanArchiveProcessor.createBeanDeploymentArchive deploying war with WEB-INF/beans.xml but no WEB-INF/classes Key: AS7-5304 URL: https://issues.jboss.org/browse/AS7-5304 Project: Application Server 7 Issue Type: Bug Components: CDI / Weld Environment: AS 7.2.0.Alpha1-SNAPSHOT 2012-08-03 a97a04dbc9b57a18e4baf6bcc32ba1c4f589c974 Reporter: Marek Schmidt Assignee: Stuart Douglas Fix For: 7.2.0.Alpha1 Attempting to deploy a WAR with only WEB-INF/beans.xml fails, if WEB-INF/classes directory not present in the WAR. {noformat} 13:38:34,534 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" started in 3686ms - Started 135 of 211 services (75 services are passive or on-demand) 13:42:03,156 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "test.war" 13:42:03,339 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment test.war 13:42:03,341 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."test.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."test.war".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "test.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] 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] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.6.0_24] at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24] Caused by: java.lang.NullPointerException at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor.createBeanDeploymentArchive(BeanArchiveProcessor.java:168) at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor.deploy(BeanArchiveProcessor.java:97) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] ... 5 more 13:42:03,356 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS015870: Deploy of deployment "test.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"test.war\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"test.war\".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment \"test.war\" Caused by: java.lang.NullPointerException"}} 13:42:03,371 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment test.war in 14ms {noformat} -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2791) Spring's JpaTransactionManager should be used instead of both: DroolsSpringTransactionManager and DroolsSpringJpaManager

by Anatoly Polinsky (JIRA)

Spring's JpaTransactionManager should be used instead of both: DroolsSpringTransactionManager and DroolsSpringJpaManager ------------------------------------------------------------------------------------------------------------------------ Key: JBRULES-2791 URL: https://jira.jboss.org/browse/JBRULES-2791 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.1.1.FINAL, FUTURE Environment: Spring Based Applications Reporter: Anatoly Polinsky Assignee: Mark Proctor Instead of having two different components: "DroolsSpringTransactionManager" and "DroolsSpringJpaManager" that aim to do the work of "org.springframework.orm.jpa.JpaTransactionManager", and trying to fit a JTA model into it, the Spring's "JpaTransactionManager" itself should be used. And instead of manually managing and constantly getting references to a "proper entity manager" from JpaManger within a SingleSessionCommandService, a @PersistenceContext should be injected. This will decouple SingleSessionCommandService from JpaManager interface, and will allow _any_ JPA provider to inject an entity manager. It has more benefits, such as trust in underline JPA providers ( e.g. Hibernate ) and Spring Transaction Management capabilities to manage the process that they are actually excellent at. /Anatoly -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
2
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