May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-1026) Harden merge

by Bela Ban (JIRA)

Harden merge ------------ Key: JGRP-1026 URL: https://jira.jboss.org/jira/browse/JGRP-1026 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.9 Make sure that no merge is ever left hanging, e.g. due to the crash of the merge coordinator after the initial phase. This could prevent furthur merges. Analyze the code and make sure that eventually merges are always completed or aborted. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
4
0 / 0

[JBoss JIRA] Deleted: (JGRP-837) Add failure simulation capabilities to Simulator

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-837?page=com.atlassian.jira.plugin.s... ] Bela Ban deleted JGRP-837: -------------------------- > Add failure simulation capabilities to Simulator > ------------------------------------------------- > > Key: JGRP-837 > URL: https://issues.jboss.org/browse/JGRP-837 > Project: JGroups > Issue Type: Feature Request > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Priority: Minor > > The Simulator can be used to test protocol layers in isolation. Multiple Simulator instances can be configured so that they model a multicast group. > In its present state, messages are transported from one Simulator instance to another by the send_thread, which moves messages from send_queue to recv_queue in a reliable fashion. Futhermore, all Simulators perform at the same speed. I'd like to use the Simulator to additionally simulate failures, in order to check the robustness of the protocols. In particular, i'd like to model: > * dropped, reordered, corrupted messages > * failed processors ('crash' failure) > * network partitions > * slow processes > This JIRA issue will track progress on this and allow for discussion. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-3049) Improve @typesafe

by Mark Proctor (JIRA)

Improve @typesafe ----------------- Key: JBRULES-3049 URL: https://issues.jboss.org/browse/JBRULES-3049 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor @typesafe wasn't workign too well. So decided to simplify things. Now it'll only apply to the pattern that matches the object type from the type declaration. Also need to refactor things so that the MVELClassReader can take imports, for things like enums on Map keys - without having to fall back to Predicate. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Assigned: (JBRULES-2824) update structure of documentation project

by David Le Sage (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2824?page=com.atlassian.jira.plug... ] David Le Sage reassigned JBRULES-2824: -------------------------------------- Assignee: Lee Carlon (was: David Le Sage) > update structure of documentation project > ----------------------------------------- > > Key: JBRULES-2824 > URL: https://issues.jboss.org/browse/JBRULES-2824 > Project: Drools > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: David Le Sage > Assignee: Lee Carlon > > We need to update the structure of the JBoss Rules docs so the docbook is consumable in both jDocBook and Publican. (Liaising with Edson Tirelli.) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (AS7-845) Problems with WARs that change name and/or runtime name

by Stan Silvert (JIRA)

Problems with WARs that change name and/or runtime name ------------------------------------------------------- Key: AS7-845 URL: https://issues.jboss.org/browse/AS7-845 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.0.0.CR1 Reporter: Stan Silvert Assignee: Remy Maucherat Various problems happen at deploy time if you deploy a file and change the name or runtime-name arguments. (Note: in the CLI, the argument to change the runtime-name is "runtime-name" rather than "runtime_name" as described in the help. See AS7-785) If I deploy foo.war and I only change the runtime-name=bar.war, it will deploy normally, but the context will be set to /foo instead of /bar. If I deploy stuff.war and change both names with name=hello and runtime-name=hello.war, the context is set to /h and I will get a 404 when I try to hit my page: [standalone@localhost:9999 /] deploy /projects/foo.war/stuff.war --name=hello --runtime-name=hello.war 'hello' deployed successfully. 16:46:15,916 INFO [org.jboss.as.server.deployment] (ManagementCommunication-threads - 10) Content added at location C:\as7trunk\jboss-as\build\target\jboss-7.0.0.Beta4-S NAPSHOT\standalone\data\content\91\b040bbc10337f5150474ee417f8aaeb005896d\content 16:46:26,096 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) Starting deployment of "hello" 16:46:26,133 INFO [org.jboss.web] (MSC service thread 1-5) registering web context: /h -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (AS7-852) No component found for type 'javax.xml.ws.WebServiceContext'

by Alessio Soldano (JIRA)

No component found for type 'javax.xml.ws.WebServiceContext' ------------------------------------------------------------ Key: AS7-852 URL: https://issues.jboss.org/browse/AS7-852 Project: Application Server 7 Issue Type: Bug Components: Web Services Reporter: Alessio Soldano Assignee: jaikiran pai Fix For: 7.0.0.CR1 When deploying and invoking an endpoint whose implementation has a @Resource WebServiceContext ctx member, we get: 16:36:07,424 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.deployment.unit."jaxws-binding.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jaxws-binding.war".INSTALL: Failed to process phase INSTALL of deployment "jaxws-binding.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21] at java.lang.Thread.run(Thread.java:619) [:1.6.0_21] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: No component found for type 'javax.xml.ws.WebServiceContext' at org.jboss.as.ee.component.ComponentTypeInjectionSource.getResourceValue(ComponentTypeInjectionSource.java:55) at org.jboss.as.ee.component.ModuleJndiBindingProcessor.addJndiBinding(ModuleJndiBindingProcessor.java:177) at org.jboss.as.ee.component.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:145) at org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:52) at org.jboss.as.ee.component.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:117) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) ... 4 more 16:36:07,434 INFO [org.jboss.as.server] (MSC service thread 1-3) Service status report New missing/unsatisfied dependencies: service jboss.naming.context.java.module.jaxws-binding.jaxws-binding (missing) required by [service jboss.naming.context.java.comp.jaxws-binding.jaxws-binding.jaxws-binding.Validator, service jboss.naming.context.java.comp.jaxws-binding.jaxws-binding.jaxws-binding.ValidatorFactory] Services which failed to start: service jboss.deployment.unit."jaxws-binding.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jaxws-binding.war".INSTALL: Failed to process phase INSTALL of deployment "jaxws-binding.war" http://jbossws.jboss.org:8180/hudson/job/CXF-CORE-AS-7.0.0-SUN-JDK-6/179/... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2203) NullPointerException When Using Conditional Element "or" in LHS Together with a Return Value Restriction

by Christian Spurk (JIRA)

NullPointerException When Using Conditional Element "or" in LHS Together with a Return Value Restriction -------------------------------------------------------------------------------------------------------- Key: JBRULES-2203 URL: https://jira.jboss.org/jira/browse/JBRULES-2203 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.0.1.FINAL Environment: Drools 5.0.1 used in an Eclipse Drools project under Windows XP with Java 1.6 Reporter: Christian Spurk Assignee: Mark Proctor When using the conditional element "or" on the left hand side of a rule together with a return value restriction somewhere in the same rule, I get the following exception: Exception in thread "main" java.lang.NullPointerException at org.drools.rule.ReturnValueRestriction.equals(ReturnValueRestriction.java:304) at org.drools.rule.ReturnValueConstraint.equals(ReturnValueConstraint.java:121) at org.drools.reteoo.AlphaNode.equals(AlphaNode.java:218) at org.drools.reteoo.SingleObjectSinkAdapter.getMatchingNode(SingleObjectSinkAdapter.java:48) at org.drools.reteoo.builder.BuildUtils.attachNode(BuildUtils.java:130) at org.drools.reteoo.builder.PatternBuilder.attachAlphaNodes(PatternBuilder.java:295) at org.drools.reteoo.builder.PatternBuilder.attachPattern(PatternBuilder.java:117) at org.drools.reteoo.builder.PatternBuilder.build(PatternBuilder.java:70) at org.drools.reteoo.builder.GroupElementBuilder$AndBuilder.build(GroupElementBuilder.java:126) at org.drools.reteoo.builder.GroupElementBuilder.build(GroupElementBuilder.java:73) at org.drools.reteoo.builder.ReteooRuleBuilder.addSubRule(ReteooRuleBuilder.java:153) at org.drools.reteoo.builder.ReteooRuleBuilder.addRule(ReteooRuleBuilder.java:126) at org.drools.reteoo.ReteooBuilder.addRule(ReteooBuilder.java:117) at org.drools.reteoo.ReteooRuleBase.addRule(ReteooRuleBase.java:362) at org.drools.common.AbstractRuleBase.addRule(AbstractRuleBase.java:618) at org.drools.common.AbstractRuleBase.addPackages(AbstractRuleBase.java:500) at org.drools.reteoo.ReteooRuleBase.addPackages(ReteooRuleBase.java:379) at org.drools.impl.KnowledgeBaseImpl.addKnowledgePackages(KnowledgeBaseImpl.java:121) at com.sample.DroolsTest.readKnowledgeBase(DroolsTest.java:48) at com.sample.DroolsTest.main(DroolsTest.java:26) Here is a simple test case which can be used to reproduce the issue: /* JAVA FILE TO LOAD THE RULE */ package com.sample; import org.drools.KnowledgeBase; import org.drools.KnowledgeBaseFactory; import org.drools.builder.KnowledgeBuilder; import org.drools.builder.KnowledgeBuilderError; import org.drools.builder.KnowledgeBuilderErrors; import org.drools.builder.KnowledgeBuilderFactory; import org.drools.builder.ResourceType; import org.drools.io.ResourceFactory; import org.drools.runtime.StatefulKnowledgeSession; public class DroolsTest { private int arg; public int getArg() { return this.arg; } public void setArg(int arg) { this.arg = arg; } public static final void main(String[] args) throws Exception { KnowledgeBase kbase = readKnowledgeBase(); StatefulKnowledgeSession ksession = kbase.newStatefulKnowledgeSession(); DroolsTest test = new DroolsTest(); test.setArg(2); ksession.insert(test); ksession.fireAllRules(); } /* taken verbatim from the Hello World sample */ private static KnowledgeBase readKnowledgeBase() throws Exception { KnowledgeBuilder kbuilder = KnowledgeBuilderFactory .newKnowledgeBuilder(); kbuilder.add(ResourceFactory.newClassPathResource("Sample.drl"), ResourceType.DRL); KnowledgeBuilderErrors errors = kbuilder.getErrors(); if (errors.size() > 0) { for (KnowledgeBuilderError error : errors) { System.err.println(error); } throw new IllegalArgumentException("Could not parse knowledge."); } KnowledgeBase kbase = KnowledgeBaseFactory.newKnowledgeBase(); kbase.addKnowledgePackages(kbuilder.getKnowledgePackages()); return kbase; } } /* PROBLEMATIC RULE FILE */ package com.sample import com.sample.DroolsTest; rule "test" when DroolsTest( arg == (1 + 1) ); // REMOVE THE COMMENTED PARTS BELOW TO GET THE EXCEPTION: //(or eval(true); eval(true); //) then System.out.println( "it works!" ); end When the above Java file is compiled and run in combination with the given rule file, everything works fine. However, if the marked parts of the rule are uncommented, then you get the exception. PS: It seems that the issue has been existing in previous Drools versions already, see https://jira.jboss.org/jira/browse/JBSEAM-3064 for example ("Drools 4.0.7 don't like 'action == (DocumentType.USER.extendedName())' and multiple OR's - weird!"). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (AS7-727) Improve DS configuration by providing a list a of available drivers

by Heiko Braun (JIRA)

Improve DS configuration by providing a list a of available drivers ------------------------------------------------------------------- Key: AS7-727 URL: https://issues.jboss.org/browse/AS7-727 Project: Application Server 7 Issue Type: Enhancement Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-9152) PersistenceUnitMetadata.getNewTempClassLoader() cannot load the entity classes

by Scott Marlow (JIRA)

PersistenceUnitMetadata.getNewTempClassLoader() cannot load the entity classes ------------------------------------------------------------------------------ Key: JBAS-9152 URL: https://issues.jboss.org/browse/JBAS-9152 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JPA / Hibernate Affects Versions: 7.0.0.Beta1 Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.0.0.Beta3 Tried to use getNewTempClassLoader in org.jboss.as.jpa.hibernate.AnnotationScanner.getClassesInJar but got CNFE. Workaround is to use PersistenceUnitMetadata.getClassLoader() -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-8959) JPA 2.0 implementation

by Scott Marlow (JIRA)

JPA 2.0 implementation ---------------------- Key: JBAS-8959 URL: https://issues.jboss.org/browse/JBAS-8959 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Scott Marlow Assignee: Scott Marlow -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
6
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 May 2011