April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2971) update "swipes" fact from entry-point

by Wolfgang Laun (JIRA)

update "swipes" fact from entry-point ------------------------------------- Key: JBRULES-2971 URL: https://issues.jboss.org/browse/JBRULES-2971 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.2.0.M2 Reporter: Wolfgang Laun Assignee: Mark Proctor After this code, the inserted Sale fact does not match Sale() from entry-point "cash" as it does when line x is removed. , StatefulKnowledgeSession kSession = this.getSession(); WorkingMemoryEntryPoint wmeep = kSession.getWorkingMemoryEntryPoint( "cash" ); FactHandle fh; Sale s = new Sale(...); fh = wmeep.insert( s ); kSession.update( fh, s ); // x - this swipes the fact from entry-point "cash" If this is the intended behaviour (which would be very strange) it isn't documented. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (JBREM-1283) CLONE [JBREM-1281] - Support setting executor in CoyoteInvoker

by Ron Sigal (JIRA)

CLONE [JBREM-1281] - Support setting executor in CoyoteInvoker -------------------------------------------------------------- Key: JBREM-1283 URL: https://issues.jboss.org/browse/JBREM-1283 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.4 Reporter: Justin Bertram Assignee: Ron Sigal Fix For: 2.2.4.SP1 In Tomcat 5.5 org.apache.coyote.http11.Http11Protocol [1] inherited its getters and setters from org.apache.coyote.http11.Http11BaseProtocol [2] and one could set "minSpareThreads" and "maxSpareThreads" directly. However, in Tomcat 6.0 [3] there is a new setExecutor method which takes a java.util.concurrent.Executor (i.e. not a String or a primitive like the other setters). The org.jboss.remoting.transport.coyote.CoyoteInvoker.setProperty(..) method doesn't support this. [1] http://tomcat.apache.org/tomcat-5.5-doc/catalina/docs/api/org/apache/coyo... [2] http://tomcat.apache.org/tomcat-5.5-doc/catalina/docs/api/org/apache/coyo... [3] http://tomcat.apache.org/tomcat-6.0-doc/api/org/apache/coyote/http11/Http... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (JBBUILD-665) The nexus repository sometimes starts serving 404s for existing poms

by Hardy Ferentschik (JIRA)

The nexus repository sometimes starts serving 404s for existing poms -------------------------------------------------------------------- Key: JBBUILD-665 URL: https://jira.jboss.org/browse/JBBUILD-665 Project: JBoss Build System Issue Type: Bug Components: Maven Builds Environment: Apache Maven 3.0.1 (r1038046; 2010-11-23 11:58:32+0100) Java version: 1.6.0_22 Reporter: Hardy Ferentschik Priority: Critical It seems sometimes the nexus repository starts serving 404s for dependencies. today I tried to rebuild Hibernate Validator from scratch and I kept getting: {noformat} [ERROR] Failed to execute goal on project hibernate-validator: Could not resolve dependencies for project org.hibernate:hibernate-validator:jar:4.2.0-SNAPSHOT: Could not find artifact org.hibernate:hibernate-entitymanager:jar:3.6.0.Final in jboss (http://repository.jboss.com/maven2) -> [Help 1] {noformat} Turned out that trying to access the URL https://repository.jboss.org/nexus/content/repositories/public/org/hibern... returns a 404 which explains at least why the build fails. This is not the first time I see this problem. A little while ago I deployed a SNAPSHOT of org.hibernate:hibernate-jpamodelgen. Even though I could see the SNAPSHOT in the directory listing I was not able to use the SNAPSHOT, because trying to access the pom would again return 404s. In the case of jpamodelgen disappeared then a day later (not sure exactly when. I just remember trying again some time a day later and it worked) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
9
0 / 0

[JBoss JIRA] Created: (JBBUILD-597) Synchronize JBoss artifacts from the JBoss repository to the Maven central repository

by Emmanuel Bernard (JIRA)

Synchronize JBoss artifacts from the JBoss repository to the Maven central repository ------------------------------------------------------------------------------------- Key: JBBUILD-597 URL: https://jira.jboss.org/jira/browse/JBBUILD-597 Project: JBoss Build System Issue Type: Feature Request Components: Artifact Repositories Reporter: Emmanuel Bernard -- 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, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-9156) read server-groups->jvm options form domain model

by Heiko Braun (JIRA)

read server-groups->jvm options form domain model -------------------------------------------------- Key: JBAS-9156 URL: https://issues.jboss.org/browse/JBAS-9156 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Heiko Braun It's currently hard coded -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
6
0 / 0

[JBoss JIRA] Created: (AS7-691) Ability to modify server-config, subresource system properties

by Heiko Braun (JIRA)

Ability to modify server-config, subresource system properties -------------------------------------------------------------- Key: AS7-691 URL: https://issues.jboss.org/browse/AS7-691 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.Beta4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-1314) FD_SOCK port conflicts with concurrently connected channels

by Paul Ferraro (JIRA)

FD_SOCK port conflicts with concurrently connected channels ----------------------------------------------------------- Key: JGRP-1314 URL: https://issues.jboss.org/browse/JGRP-1314 Project: JGroups Issue Type: Bug Affects Versions: 2.12.1 Reporter: Paul Ferraro Assignee: Bela Ban Because of the high level of concurrency in AS7, I'm seeing occasional socket exceptions in FD_SOCK when trying to start multiple channels using a shared transport. It appears that there are some thread safety issues with the port increment logic within FD_SOCK. Until JGRP-790 is complete, measures need to be taken to ensure that multiple concurrently connected channels do not select the same port on which to open a server socket. Here's a sample stack trace: 10:01:26,716 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.infinispan.cluster: org.jboss.msc.service.StartException in service jboss.infinispan.cluster: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1696) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22] Caused by: org.infinispan.CacheException: Unable to invoke method public abstract void org.infinispan.remoting.transport.Transport.start() on object at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:174) at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:889) at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:687) at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:589) at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:137) at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:137) at org.infinispan.CacheDelegate.start(CacheDelegate.java:323) at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:516) at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:439) at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:77) at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:66) at org.jboss.as.clustering.infinispan.subsystem.EmbeddedCacheManagerService.start(EmbeddedCacheManagerService.java:171) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) ... 3 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [:1.6.0_22] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [:1.6.0_22] at java.lang.reflect.Method.invoke(Method.java:616) [:1.6.0_22] at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:171) ... 15 more Caused by: java.lang.IllegalArgumentException: failed to start server socket at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:295) at org.jgroups.protocols.FD.down(FD.java:310) at org.jgroups.protocols.VERIFY_SUSPECT.down(VERIFY_SUSPECT.java:70) at org.jgroups.protocols.BARRIER.down(BARRIER.java:90) at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:634) at org.jgroups.protocols.UNICAST.down(UNICAST.java:443) at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:330) at org.jgroups.protocols.VIEW_SYNC.down(VIEW_SYNC.java:186) at org.jgroups.protocols.pbcast.GMS.down(GMS.java:926) at org.jgroups.protocols.FlowControl.down(FlowControl.java:351) at org.jgroups.protocols.FlowControl.down(FlowControl.java:351) at org.jgroups.protocols.FRAG2.down(FRAG2.java:155) at org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.down(STREAMING_STATE_TRANSFER.java:324) at org.jgroups.protocols.pbcast.FLUSH.handleConnect(FLUSH.java:302) at org.jgroups.protocols.pbcast.FLUSH.down(FLUSH.java:263) at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:1081) at org.jgroups.JChannel.downcall(JChannel.java:1680) at org.jgroups.JChannel.connect(JChannel.java:425) at org.jgroups.JChannel.connect(JChannel.java:388) at org.infinispan.remoting.transport.jgroups.JGroupsTransport.startJGroupsChannelIfNeeded(JGroupsTransport.java:171) at org.infinispan.remoting.transport.jgroups.JGroupsTransport.start(JGroupsTransport.java:155) ... 20 more Caused by: java.net.SocketException: Address already in use at java.net.PlainSocketImpl.socketListen(Native Method) [:1.6.0_22] at java.net.AbstractPlainSocketImpl.listen(AbstractPlainSocketImpl.java:365) [:1.6.0_22] at java.net.ServerSocket.bind(ServerSocket.java:337) [:1.6.0_22] at java.net.ServerSocket.<init>(ServerSocket.java:202) [:1.6.0_22] at org.jgroups.util.DefaultSocketFactory.createServerSocket(DefaultSocketFactory.java:49) at org.jgroups.util.Util.createServerSocket(Util.java:3046) at org.jgroups.protocols.FD_SOCK.startServerSocket(FD_SOCK.java:561) at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:292) ... 40 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
4
0 / 0

[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, 2 months

1
4
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, 2 months

3
6
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, 2 months

1
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 April 2011