May 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-987) Errors in Phreak under heavy and multi threaded load

by Jose Cavieres (JIRA)

[ https://issues.jboss.org/browse/DROOLS-987?page=com.atlassian.jira.plugin... ] Jose Cavieres updated DROOLS-987: --------------------------------- Affects Version/s: 6.4.0.Final > Errors in Phreak under heavy and multi threaded load > ----------------------------------------------------- > > Key: DROOLS-987 > URL: https://issues.jboss.org/browse/DROOLS-987 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.3.0.Final, 6.4.0.Final > Environment: linux > Java 7 > kernel 3.16 > Reporter: Jose Cavieres > Assignee: Marco Rietveld > Attachments: jbpm-bussinesruletask-concurrent-6-3-NEW.tgz, jbpm-bussinesruletask-concurrent-6-3.tgz > > > Several threads are started, each one starts 1 jbpm process containing rule(s) task(s). > If the threads are few, everything works fine. Under heavy load nullPointerExceptions are thown most of the time, less frequently fireAllRules never ends and CPU remains at 100%. > Aparently the setFocus method used by rule tasks is related to the problem. > The most comon error is: > Caused by: java.lang.NullPointerException > at org.drools.core.common.LeftTupleSetsImpl.removeInsert(LeftTupleSetsImpl.java:141) > at org.drools.core.common.LeftTupleSetsImpl.addDelete(LeftTupleSetsImpl.java:80) > at org.drools.core.reteoo.LeftInputAdapterNode.doDeleteSegmentMemory(LeftInputAdapterNode.java:295) > at org.drools.core.reteoo.LeftInputAdapterNode.doDeleteObject(LeftInputAdapterNode.java:266) > at org.drools.core.reteoo.LeftInputAdapterNode.retractLeftTuple(LeftInputAdapterNode.java:361) > at org.drools.core.reteoo.ObjectTypeNode.doRetractObject(ObjectTypeNode.java:334) > at org.drools.core.reteoo.ObjectTypeNode.retractObject(ObjectTypeNode.java:317) > at org.drools.core.reteoo.EntryPointNode.propagateRetract(EntryPointNode.java:358) > at org.drools.core.phreak.PropagationEntry$Delete.execute(PropagationEntry.java:172) > at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:96) > at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:69) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.flushPropagations(StatefulKnowledgeSessionImpl.java:1993) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1573) RemotingModelControllerClient can hang on close

by David Lloyd (JIRA)

David Lloyd created WFCORE-1573: ----------------------------------- Summary: RemotingModelControllerClient can hang on close Key: WFCORE-1573 URL: https://issues.jboss.org/browse/WFCORE-1573 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: David Lloyd Assignee: David Lloyd RemotingModelControllerClient closes its Remoting endpoint. While generally not correct, this can still be done if the close is performed asynchronously. We can revisit the relationship between the remote controller client and its connections and endpoints at a later time. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1570) Saved rollout-plan 'name' or 'id' attribute discrepancy

by Bartosz Spyrko-Śmietanko (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1570?page=com.atlassian.jira.plugi... ] Bartosz Spyrko-Śmietanko updated WFCORE-1570: --------------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/1583 > Saved rollout-plan 'name' or 'id' attribute discrepancy > ------------------------------------------------------- > > Key: WFCORE-1570 > URL: https://issues.jboss.org/browse/WFCORE-1570 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 3.0.0.Alpha1 > Reporter: Bartosz Spyrko-Śmietanko > Assignee: Bartosz Spyrko-Śmietanko > Priority: Minor > > When using rollout plans for EAP deployment scenarios I can create my own named rollout-plan for ease of use. I can then apply rollout command later on, referring with name of my own rollout plan that should be used. There is minor discrepancy in the way I create and use such rollout plan though. > When I create rollout-plan, I use command like: > {code} > rollout-plan add --name=my-rollout-plan --content={rollout main-server-group(rolling-to-servers=false,max-failed-servers=1),other-server-group(rolling-to-servers=true,max-failure-percentage=20) rollback-across-groups=true} > {code} > - see {{--name}} attribute given to name my rollout plan > When I then refer to it I use following command: > {code} > deploy /path/to/test-application.war --all-server-groups --headers={rollout id=my-rollout-plan} > {code} > - see {{id}} attribute given to {{rollout}} header operation > Yes, this is really minor issue, but I think that these two attributes used in aforementioned commands should be unified (preferably to {{name}} instead of {{id}}) as user might be confused when using it. > Note: examples are used from our documentation. > Note: I do not know whether I am missing something but I was not able to retrieve more info how to use {{rollout}} header operation in deploy command directly in CLI. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1572) Suggestion list for argument value is not generated if the value contains a whitespace

by Bartosz Spyrko-Śmietanko (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1572?page=com.atlassian.jira.plugi... ] Bartosz Spyrko-Śmietanko moved JBEAP-4751 to WFCORE-1572: --------------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-1572 (was: JBEAP-4751) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: CLI (was: CLI) Target Release: (was: 7.backlog.GA) Affects Version/s: 3.0.0.Alpha1 (was: 7.0.0.GA) > Suggestion list for argument value is not generated if the value contains a whitespace > -------------------------------------------------------------------------------------- > > Key: WFCORE-1572 > URL: https://issues.jboss.org/browse/WFCORE-1572 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 3.0.0.Alpha1 > Reporter: Bartosz Spyrko-Śmietanko > Assignee: Bartosz Spyrko-Śmietanko > > When an argument value contains a space (eg. {{deploy /path/to/test-application.war --all-server-groups --headers=\{rollout id=foo\}}}) and if user hits tab after the whitespace, suggestions are generated based on the command, rather than the current argument's name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1571) Do not wait indefinitely for a channel open to succeed

by David Lloyd (JIRA)

David Lloyd created WFCORE-1571: ----------------------------------- Summary: Do not wait indefinitely for a channel open to succeed Key: WFCORE-1571 URL: https://issues.jboss.org/browse/WFCORE-1571 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Reporter: David Lloyd Assignee: David Lloyd There is no need to wait forever for a management channel to open. If the open fails, we can just throw an exception and retry the connection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-538) Infinite loop in ElytronPermissionCollection.readResolve() method

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-538?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-538. ----------------------------- Resolution: Done > Infinite loop in ElytronPermissionCollection.readResolve() method > ----------------------------------------------------------------- > > Key: ELY-538 > URL: https://issues.jboss.org/browse/ELY-538 > Project: WildFly Elytron > Issue Type: Bug > Components: Security Manager > Affects Versions: 1.1.0.Beta5 > Reporter: Ondrej Lukas > Assignee: David Lloyd > Labels: static_analysis > Fix For: 1.1.0.Beta7 > > > There is infinite loop in ElytronPermissionCollection.readResolve() on line 61 [1]. Variable {{bits}} is never changed in {{while}} cycle. > [1] https://github.com/wildfly-security/wildfly-elytron/blob/ef67225884aa79b8... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1188) Move contents of kie-eap-modules repository directly into droolsjbpm-integration

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1188?page=com.atlassian.jira.plugi... ] Petr Široký resolved DROOLS-1188. --------------------------------- Fix Version/s: 7.0.0.Beta1 Resolution: Done The content of kie-eap-modules repository was successfully merged into the droolsjbpm-integration repository, under subdirectory kie-eap-integration. One repo removed, more to go. > Move contents of kie-eap-modules repository directly into droolsjbpm-integration > -------------------------------------------------------------------------------- > > Key: DROOLS-1188 > URL: https://issues.jboss.org/browse/DROOLS-1188 > Project: Drools > Issue Type: Enhancement > Components: build > Affects Versions: 6.4.0.Final > Reporter: Petr Široký > Assignee: Petr Široký > Fix For: 7.0.0.Beta1 > > > The KIE EAP integration now resides inside its own repository https://github.com/jboss-integration/kie-eap-modules. This is for some historical reasons which no longer seem to apply (e.g. we no longer build skinny WARs, we just bundle core engine jars as JBoss modules). > We should move the content directly into droolsjbpm-integration repository, under kie-eap-integration sub-directory. This would decrease the maintenance effort connected with having large number of source repositories. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6626) Add log message indicating disabled <distributable/> flag from web-fragments

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-6626?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-6626: ----------------------------------------------- Panagiotis Sotiropoulos <psotirop(a)redhat.com> changed the Status of [bug 1337858|https://bugzilla.redhat.com/show_bug.cgi?id=1337858] from ASSIGNED to POST > Add log message indicating disabled <distributable/> flag from web-fragments > ---------------------------------------------------------------------------- > > Key: WFLY-6626 > URL: https://issues.jboss.org/browse/WFLY-6626 > Project: WildFly > Issue Type: Enhancement > Components: Web (Undertow) > Affects Versions: 10.0.0.Final > Reporter: Aaron Ogburn > Assignee: Stuart Douglas > Attachments: undistributable.war > > > If a web-fragment doesn't have distributable set, then replication is not enabled. This happens silently so it may be confusing to some users that are expecting replication to be enabled when they have set <distributable/> in their WEB-INF/web.xml. > Other third party libraries they included may have web-fragments without distributable set so it'd be nice to log a notification when this happens so that users are easily informed why replication was not enabled as they may have expected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1498) Different shutdown messages depending on reason for shutdown

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1498?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated WFCORE-1498: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1328673 Bugzilla Update: Perform > Different shutdown messages depending on reason for shutdown > ------------------------------------------------------------ > > Key: WFCORE-1498 > URL: https://issues.jboss.org/browse/WFCORE-1498 > Project: WildFly Core > Issue Type: Feature Request > Components: Server > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Labels: 2.2 > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > Use different output for SIGTERM vs shutdown op vs abort vs various flavors of managed domain shutdown. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1125) Google App Engine support: ClassLoader.getSystemClassLoader() throws exception

by Vlastimil Eliáš (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1125?page=com.atlassian.jira.plugi... ] Vlastimil Eliáš updated DROOLS-1125: ------------------------------------ Comment: was deleted (was: Xiong Zhi Ming <zxiong(a)redhat.com> changed the Status of [bug 1329093|https://bugzilla-qe-05.host.stage.eng.rdu2.redhat.com/show_bug.cg...] from NEW to ASSIGNED) > Google App Engine support: ClassLoader.getSystemClassLoader() throws exception > ------------------------------------------------------------------------------ > > Key: DROOLS-1125 > URL: https://issues.jboss.org/browse/DROOLS-1125 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Fix For: 7.0.0.Beta1 > > > Class org.kie.internal.utils.ChainedProperties > Every call to get the System Class Loader > confClassLoader = ClassLoader.getSystemClassLoader(); (i.e. lines 133, 169) > raises an exception. > Todo: figure out which particular exception. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
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 2016