September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2293) Graceful concurrent leaving of coordinator(s) leaves the cluster with stale views

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2293?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2293: -------------------------------- You're right, sir, I'll change that. First prio! > Graceful concurrent leaving of coordinator(s) leaves the cluster with stale views > --------------------------------------------------------------------------------- > > Key: JGRP-2293 > URL: https://issues.jboss.org/browse/JGRP-2293 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.14 > Reporter: Radoslav Husar > Assignee: Bela Ban > Priority: Critical > Fix For: 4.0.15 > > > JGroups does not handle concurrent leaving of nodes correctly. This is a typical use case in cloud environment when scaled down with an autoscaler/manually which we need to handle. > A simple test can be devised which fails first n (where n>1) nodes from a cluster, reproducer PR https://github.com/belaban/JGroups/pull/397 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2892) Session reset doesn't clear path memory

by Christian Liebhardt (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2892?page=com.atlassian.jira.plugi... ] Christian Liebhardt closed DROOLS-2892. --------------------------------------- We completed the tests on our side and everything works fine. Thanks a lot for the fix :)! > Session reset doesn't clear path memory > --------------------------------------- > > Key: DROOLS-2892 > URL: https://issues.jboss.org/browse/DROOLS-2892 > Project: Drools > Issue Type: Bug > Reporter: Christian Liebhardt > Assignee: Mario Fusco > > As discussed in https://groups.google.com/forum/#!topic/drools-usage/V8ypP1o5SwM : > In order to reduce memory allocations we are calling _StatefulKnowledgeSessionImpl.reset()_ to bring a disposed session back into life. From our understanding this is the same method which the Drools session cache would use. During our tests we found that some of our rules don't trigger if we use this approach. We also found that the reset method leaves _PathMemory_ instances behind in the memory. As soon as we cleared the memory explicitly by calling _session.getNodeMemories().clear()_ after every _session.reset()_ the rules fired again as usual. So we are wondering if the current implementation of _session.reset()_ is incomplete. > We are aware that _session.reset()_ is an internal method. However this issue should also affect the session cache feature of Drools. At the same time it would be nice to have a public interface to _session.reset()_ since in our application reusing a session is beneficial but we don't need the session cache as we can easily remember the last session which we used for processing and it seems more straightforward to just bring that one back to life instead of storing and retrieving it from a cache. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1679) (7.1.z) SASL property com.sun.security.sasl.digest.utf8 does not behave as default when its default value is explicitely configured

by Jiri Ondrusek (JIRA)

[ https://issues.jboss.org/browse/ELY-1679?page=com.atlassian.jira.plugin.s... ] Jiri Ondrusek moved JBEAP-15515 to ELY-1679: -------------------------------------------- Project: WildFly Elytron (was: JBoss Enterprise Application Platform) Key: ELY-1679 (was: JBEAP-15515) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: (was: Security) Affects Version/s: 1.1.11.Final (was: 7.1.0.CR2) > (7.1.z) SASL property com.sun.security.sasl.digest.utf8 does not behave as default when its default value is explicitely configured > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: ELY-1679 > URL: https://issues.jboss.org/browse/ELY-1679 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.11.Final > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > > SASL property *com.sun.security.sasl.digest.utf8* does not behave as default when its default value is explicitely configured. > When we ommit this explicit property setting then everything is fine. > This property is described here [1] and *true* is default value. Property is defined in wildfly-core project org.wildfly.security.sasl.WildFlySasl.USE_UTF8. > Here is how to set it [2]. > Please check Steps to Reproduce, there is how to update test. > [1] https://doc-stage.usersys.redhat.com/documentation/en-us/red_hat_jboss_en... > [2] https://doc-stage.usersys.redhat.com/documentation/en-us/red_hat_jboss_en... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11065) Usage of static fields from java.lang classes as EL expressions in JSPs doesn't work for servlet 4.0

by Jan Stourac (JIRA)

[ https://issues.jboss.org/browse/WFLY-11065?page=com.atlassian.jira.plugin... ] Jan Stourac commented on WFLY-11065: ------------------------------------ Note that there is prepared commit with tests to cover this issue in WildFly TS, [see here|https://github.com/jstourac/wildfly/commit/528558db6d9f5e42d43b89f60...]. > Usage of static fields from java.lang classes as EL expressions in JSPs doesn't work for servlet 4.0 > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-11065 > URL: https://issues.jboss.org/browse/WFLY-11065 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 14.0.0.Beta2 > Reporter: Jan Stourac > Assignee: Stuart Douglas > > This seems to be back but this time with Servlet 4.0 only as 3.1 seems to work just fine. Current test is already in [Wildfly testsuite|https://github.com/wildfly/wildfly/blob/master/testsuite/integr...] but it does not cover Servlet 4.0. > Java EE7 (which supports EL 3.0 spec) allows JSPs to use EL expressions like: > {code} > <html> > <body> > foo: --- ${Boolean.TRUE} ---<br> > bar: --- ${Integer.MAX_VALUE} ---<br> > </body> > </html> > {code} > However, the {code}${Boolean.TRUE}{code} and {code}${Integer.MAX_VALUE}{code} in the above example aren't evaluated correctly and instead a blank string is rendered for them. > More details in the linked forum thread https://developer.jboss.org/thread/271825 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11065) Usage of static fields from java.lang classes as EL expressions in JSPs doesn't work for servlet 4.0

by Jan Stourac (JIRA)

[ https://issues.jboss.org/browse/WFLY-11065?page=com.atlassian.jira.plugin... ] Jan Stourac moved JBEAP-15514 to WFLY-11065: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-11065 (was: JBEAP-15514) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Web (Undertow) (was: Web (Undertow)) Affects Version/s: 14.0.0.Beta2 (was: 7.2.0.Beta) QE Test Coverage: (was: +) > Usage of static fields from java.lang classes as EL expressions in JSPs doesn't work for servlet 4.0 > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-11065 > URL: https://issues.jboss.org/browse/WFLY-11065 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 14.0.0.Beta2 > Reporter: Jan Stourac > Assignee: Stuart Douglas > > This seems to be back but this time with Servlet 4.0 only as 3.1 seems to work just fine. Current test is already in [Wildfly testsuite|https://github.com/wildfly/wildfly/blob/master/testsuite/integr...] but it does not cover Servlet 4.0. > Java EE7 (which supports EL 3.0 spec) allows JSPs to use EL expressions like: > {code} > <html> > <body> > foo: --- ${Boolean.TRUE} ---<br> > bar: --- ${Integer.MAX_VALUE} ---<br> > </body> > </html> > {code} > However, the {code}${Boolean.TRUE}{code} and {code}${Integer.MAX_VALUE}{code} in the above example aren't evaluated correctly and instead a blank string is rendered for them. > More details in the linked forum thread https://developer.jboss.org/thread/271825 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3033) Fix transitive dependencies declaration inside webapp pom

by Gabriele Cardosi (JIRA)

Gabriele Cardosi created DROOLS-3033: ---------------------------------------- Summary: Fix transitive dependencies declaration inside webapp pom Key: DROOLS-3033 URL: https://issues.jboss.org/browse/DROOLS-3033 Project: Drools Issue Type: Bug Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Priority: Blocker Some modules have been moved to a different position and now are found as "transitive dependency" by maven - the enforcer forbid this -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9447) NPE in ejb client and clean shutdown ERROR [org.jboss.ejb.client.invocation] (default task-8) EJBCLIENT000509: Unexpected exception processing EJB request: java.lang.NullPointerException

by tommaso borgato (JIRA)

[ https://issues.jboss.org/browse/WFLY-9447?page=com.atlassian.jira.plugin.... ] tommaso borgato commented on WFLY-9447: --------------------------------------- [~rhusar] you are right ... this is the wrong issue ... going to remove the note > NPE in ejb client and clean shutdown ERROR [org.jboss.ejb.client.invocation] (default task-8) EJBCLIENT000509: Unexpected exception processing EJB request: java.lang.NullPointerException > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-9447 > URL: https://issues.jboss.org/browse/WFLY-9447 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 14.0.1.Final, 11.0.0.CR1 > Reporter: Radoslav Husar > > {noformat} > ESC[0m13:59:55,004 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0211: Suspending server with 15000 ms timeout. > ESC[0mESC[0m13:59:55,006 INFO [org.jboss.as.ejb3] (management-handler-thread - 1) WFLYEJB0493: EJB subsystem suspension complete > ESC[0mESC[0m13:59:55,008 INFO [org.jboss.as.server] (Management Triggered Shutdown) WFLYSRV0241: Shutting down in response to management operation 'shutdown' > ESC[0mESC[0m13:59:55,027 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0019: Host default-host stopping > ESC[0mESC[0m13:59:55,028 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 72) MODCLUSTER000002: Initiating mod_cluster shutdown > ESC[0mESC[0m13:59:55,039 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000080: Disconnecting JGroups channel ejb > ESC[0mESC[0m13:59:55,039 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000080: Disconnecting JGroups channel ejb > ESC[0mESC[0m13:59:55,039 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000080: Disconnecting JGroups channel ejb > ESC[0mESC[0m13:59:55,040 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000082: Stopping the RpcDispatcher for channel ejb > ESC[0mESC[0m13:59:55,040 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000082: Stopping the RpcDispatcher for channel ejb > ESC[0mESC[0m13:59:55,040 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000082: Stopping the RpcDispatcher for channel ejb > ESC[0mESC[0m13:59:55,042 INFO [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 74) ISPN000029: Passivating all entries to disk > ESC[0mESC[0m13:59:55,046 INFO [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 74) ISPN000030: Passivated 2 entries in 3 milliseconds > ESC[0mESC[0m13:59:55,055 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS] > ESC[0mESC[0m13:59:55,055 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 74) WFLYCLINF0003: Stopped twocluster-terminus.jar cache from ejb container > ESC[0m13:59:55,057 DEBUG [org.jboss.ejb.client.invocation] (pool-1-thread-1) Calling invoke(module = /twocluster-forwarder-tx/ForwardingStatefulSBImpl, strong affinity = Cluster "ejb-forwarder", weak affinity = Node "clusterA-node0"): > ESC[0m13:59:55,059 INFO [org.jboss.as.test.clustering.twoclusters.bean.forwarding.AbstractForwardingStatefulSBImpl] (default task-124) getSerialAndIncrement() called on forwarding node clusterA-node0 > ESC[0mESC[31m13:59:55,062 ERROR [org.jboss.ejb.client.invocation] (default task-8) EJBCLIENT000509: Unexpected exception processing EJB request: java.lang.NullPointerException > at org.jboss.as.ejb3.deployment.DeploymentRepository.getStartedModules(DeploymentRepository.java:202) > at org.jboss.as.ejb3.remote.AssociationImpl.findEJB(AssociationImpl.java:382) > at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:115) > at org.jboss.ejb.protocol.remote.EJBServerChannel$ReceiverImpl.handleInvocationRequest(EJBServerChannel.java:450) > at org.jboss.ejb.protocol.remote.EJBServerChannel$ReceiverImpl.handleMessage(EJBServerChannel.java:188) > at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:926) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > {noformat} > Appears in https://github.com/jbossas/jboss-eap7/pull/2446 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9447) NPE in ejb client and clean shutdown ERROR [org.jboss.ejb.client.invocation] (default task-8) EJBCLIENT000509: Unexpected exception processing EJB request: java.lang.NullPointerException

by tommaso borgato (JIRA)

[ https://issues.jboss.org/browse/WFLY-9447?page=com.atlassian.jira.plugin.... ] tommaso borgato updated WFLY-9447: ---------------------------------- Comment: was deleted (was: A comment with security level 'Red Hat Employee' was removed.) > NPE in ejb client and clean shutdown ERROR [org.jboss.ejb.client.invocation] (default task-8) EJBCLIENT000509: Unexpected exception processing EJB request: java.lang.NullPointerException > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-9447 > URL: https://issues.jboss.org/browse/WFLY-9447 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 14.0.1.Final, 11.0.0.CR1 > Reporter: Radoslav Husar > > {noformat} > ESC[0m13:59:55,004 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0211: Suspending server with 15000 ms timeout. > ESC[0mESC[0m13:59:55,006 INFO [org.jboss.as.ejb3] (management-handler-thread - 1) WFLYEJB0493: EJB subsystem suspension complete > ESC[0mESC[0m13:59:55,008 INFO [org.jboss.as.server] (Management Triggered Shutdown) WFLYSRV0241: Shutting down in response to management operation 'shutdown' > ESC[0mESC[0m13:59:55,027 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0019: Host default-host stopping > ESC[0mESC[0m13:59:55,028 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 72) MODCLUSTER000002: Initiating mod_cluster shutdown > ESC[0mESC[0m13:59:55,039 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000080: Disconnecting JGroups channel ejb > ESC[0mESC[0m13:59:55,039 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000080: Disconnecting JGroups channel ejb > ESC[0mESC[0m13:59:55,039 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000080: Disconnecting JGroups channel ejb > ESC[0mESC[0m13:59:55,040 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000082: Stopping the RpcDispatcher for channel ejb > ESC[0mESC[0m13:59:55,040 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000082: Stopping the RpcDispatcher for channel ejb > ESC[0mESC[0m13:59:55,040 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000082: Stopping the RpcDispatcher for channel ejb > ESC[0mESC[0m13:59:55,042 INFO [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 74) ISPN000029: Passivating all entries to disk > ESC[0mESC[0m13:59:55,046 INFO [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 74) ISPN000030: Passivated 2 entries in 3 milliseconds > ESC[0mESC[0m13:59:55,055 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS] > ESC[0mESC[0m13:59:55,055 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 74) WFLYCLINF0003: Stopped twocluster-terminus.jar cache from ejb container > ESC[0m13:59:55,057 DEBUG [org.jboss.ejb.client.invocation] (pool-1-thread-1) Calling invoke(module = /twocluster-forwarder-tx/ForwardingStatefulSBImpl, strong affinity = Cluster "ejb-forwarder", weak affinity = Node "clusterA-node0"): > ESC[0m13:59:55,059 INFO [org.jboss.as.test.clustering.twoclusters.bean.forwarding.AbstractForwardingStatefulSBImpl] (default task-124) getSerialAndIncrement() called on forwarding node clusterA-node0 > ESC[0mESC[31m13:59:55,062 ERROR [org.jboss.ejb.client.invocation] (default task-8) EJBCLIENT000509: Unexpected exception processing EJB request: java.lang.NullPointerException > at org.jboss.as.ejb3.deployment.DeploymentRepository.getStartedModules(DeploymentRepository.java:202) > at org.jboss.as.ejb3.remote.AssociationImpl.findEJB(AssociationImpl.java:382) > at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:115) > at org.jboss.ejb.protocol.remote.EJBServerChannel$ReceiverImpl.handleInvocationRequest(EJBServerChannel.java:450) > at org.jboss.ejb.protocol.remote.EJBServerChannel$ReceiverImpl.handleMessage(EJBServerChannel.java:188) > at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:926) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > {noformat} > Appears in https://github.com/jbossas/jboss-eap7/pull/2446 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2950) [DMN Editor] Custom data-types - ItemDefinitionRecordEngine - The QName instance should lookup the real prefix from the URI

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2950?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2950: ------------------------------------- [~karreiro] Thanks for description, I increased slightly coverage [here|https://github.com/kiegroup/kie-wb-common/pull/2142]. > [DMN Editor] Custom data-types - ItemDefinitionRecordEngine - The QName instance should lookup the real prefix from the URI > --------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2950 > URL: https://issues.jboss.org/browse/DROOLS-2950 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.11.0.Final > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Labels: drools-tools > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2819) [DMN Designer] [IE11] Expression type change throws an Error

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2819?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2819: -------------------------------- Fix Version/s: 7.12.0.Final > [DMN Designer] [IE11] Expression type change throws an Error > ------------------------------------------------------------ > > Key: DROOLS-2819 > URL: https://issues.jboss.org/browse/DROOLS-2819 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.10.0.Final > Environment: IE11 > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Labels: drools-tools > Fix For: 7.12.0.Final > > > When user tries to change expression type the Unexpected error appears: *Uncaught exception: Exception caught: Exception caught: (TypeError) : Object doesn't support property or method 'startsWith' Caused by: Exception caught: (TypeError) : Object doesn't support property or method 'startsWith' Caused by: (TypeError) : Object doesn't support property or method 'startsWith'* > h2. Manual Acceptance Test > With DROOLS-2818 check steps to reproduce > - IE (/) > - Chrome (/) > - Firefox (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 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 September 2018