[JBoss JIRA] (WFLY-9261) Cluster connection receives a "consumer created" message from the rebooting node but it has no corresponding binding for it locally
by Miroslav Novak (Jira)
[ https://issues.jboss.org/browse/WFLY-9261?page=com.atlassian.jira.plugin.... ]
Miroslav Novak updated WFLY-9261:
---------------------------------
Affects Version/s: 15.0.0.Final
14.0.0.Final
> Cluster connection receives a "consumer created" message from the rebooting node but it has no corresponding binding for it locally
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9261
> URL: https://issues.jboss.org/browse/WFLY-9261
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final, 15.0.0.Final
> Reporter: Flavia Rainone
> Assignee: Martyn Taylor
> Priority: Major
>
> When rebooting a cluster node that uses singleton cluster mdbs, we get this error message:
> {noformat}
> 2017-07-25 16:08:54,426 ERROR [org.apache.activemq.artemis.core.server] (Thread-3 (ActiveMQ-client-global-threads)) AMQ224037: cluster connection Failed to handle message: java.lang.IllegalStateException: Cannot find binding for jms.queue.HelloWorldMDBQueuedea3e995-713c-11e7-85f2-b8f6b112daf7 on ClusterConnectionImpl@1129705701[nodeUUID=dabaa1fa-713c-11e7-8f3a-b8f6b112daf7, connector=TransportConfiguration(name=http-connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEndpoint=http-acceptor&activemqServerName=default&httpUpgradeEnabled=true&port=9080&host=localhost, address=jms, server=ActiveMQServerImpl::serverUUID=dabaa1fa-713c-11e7-8f3a-b8f6b112daf7]
> at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.doConsumerCreated(ClusterConnectionImpl.java:1294)
> at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.handleNotificationMessage(ClusterConnectionImpl.java:1029)
> at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.onMessage(ClusterConnectionImpl.java:1004)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1001)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:49)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1124)
> at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:101)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3412) Performance degradation with session pools
by Christian Liebhardt (Jira)
[ https://issues.jboss.org/browse/DROOLS-3412?page=com.atlassian.jira.plugi... ]
Christian Liebhardt edited comment on DROOLS-3412 at 12/11/18 7:38 AM:
-----------------------------------------------------------------------
If I retest the latest 7.16-SNAPSHOT then the issue still seems to exist. Dispose alone doesn't seem to be sufficient as org.jbpm.process.instance.ProcessRuntimeImpl doesn't remove its listener on dispose. Is a change to JBPM planned or am I missing something here?
Test is done by running https://github.com/liebharc/JavaRules/blob/master/src/test/java/com/githu... .
was (Author: christianl):
If I retest the latest 7.16-SNAPSHOT then the issue still seems to exist. Dispose alone doesn't seem to be sufficient as org.jbpm.process.instance.ProcessRuntimeImpl doesn't remove its listener on dispose. Is a change to JBPM planned or am I missing something here?
Test is done by running by running https://github.com/liebharc/JavaRules/blob/master/src/test/java/com/githu... .
> Performance degradation with session pools
> ------------------------------------------
>
> Key: DROOLS-3412
> URL: https://issues.jboss.org/browse/DROOLS-3412
> Project: Drools
> Issue Type: Bug
> Reporter: Christian Liebhardt
> Assignee: Mario Fusco
> Priority: Major
> Attachments: gc.png
>
>
> Hello,
> We've today updates to Drools 7.15 and as discussed with DROOLS-3228 we changed our code from calling _StatefulKnowledgeSessionImpl.reset_ ourselves to _KieSessionsPool_. However we then recognized that our application quickly became slower and slower over time (roughly after a few minutes of uptime, or a couple of hundred session create/dispose cycles).
> I haven't yet found the reason what is causing the slow down. However I think there is a difference in how we reset our sessions before session pools and how session pools do it. Perhaps that is a lead.
> *What we did*
> # Create a session
> # Use the session
> # Dispose and reset the session and go back to 2 for the next facts
> *What happens with session pools*
> # Create a session
> # Use the session
> # Skip dispose (because of _pool != null_ in the dispose method), reset the session and go back to 2 for the next facts
> So the difference seems to be that with session pools the session doesn't get disposed before reset it called. If I do the same without session pools then I also see the same slow down. So it seems that something is left behind and causes a slow down. The results however seem to be correct, so the right consequences appear to be triggered.
> An example on how we use the session pool can be found here: https://github.com/liebharc/JavaRules/blob/master/src/main/java/com/githu...
> Thanks once more for your help.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3412) Performance degradation with session pools
by Christian Liebhardt (Jira)
[ https://issues.jboss.org/browse/DROOLS-3412?page=com.atlassian.jira.plugi... ]
Christian Liebhardt commented on DROOLS-3412:
---------------------------------------------
If I retest the latest 7.16-SNAPSHOT then the issue still seems to exist. Dispose alone doesn't seem to be sufficient as org.jbpm.process.instance.ProcessRuntimeImpl doesn't remove its listener on dispose. Is a change to JBPM planned or am I missing something here?
Test is done by running by running https://github.com/liebharc/JavaRules/blob/master/src/test/java/com/githu... .
> Performance degradation with session pools
> ------------------------------------------
>
> Key: DROOLS-3412
> URL: https://issues.jboss.org/browse/DROOLS-3412
> Project: Drools
> Issue Type: Bug
> Reporter: Christian Liebhardt
> Assignee: Mario Fusco
> Priority: Major
> Attachments: gc.png
>
>
> Hello,
> We've today updates to Drools 7.15 and as discussed with DROOLS-3228 we changed our code from calling _StatefulKnowledgeSessionImpl.reset_ ourselves to _KieSessionsPool_. However we then recognized that our application quickly became slower and slower over time (roughly after a few minutes of uptime, or a couple of hundred session create/dispose cycles).
> I haven't yet found the reason what is causing the slow down. However I think there is a difference in how we reset our sessions before session pools and how session pools do it. Perhaps that is a lead.
> *What we did*
> # Create a session
> # Use the session
> # Dispose and reset the session and go back to 2 for the next facts
> *What happens with session pools*
> # Create a session
> # Use the session
> # Skip dispose (because of _pool != null_ in the dispose method), reset the session and go back to 2 for the next facts
> So the difference seems to be that with session pools the session doesn't get disposed before reset it called. If I do the same without session pools then I also see the same slow down. So it seems that something is left behind and causes a slow down. The results however seem to be correct, so the right consequences appear to be triggered.
> An example on how we use the session pool can be found here: https://github.com/liebharc/JavaRules/blob/master/src/main/java/com/githu...
> Thanks once more for your help.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFLY-9305) ActiveMQ Resource Adapter can not lookup destination in app namespace
by Miroslav Novak (Jira)
[ https://issues.jboss.org/browse/WFLY-9305?page=com.atlassian.jira.plugin.... ]
Miroslav Novak updated WFLY-9305:
---------------------------------
Affects Version/s: 15.0.0.Final
14.0.0.Final
> ActiveMQ Resource Adapter can not lookup destination in app namespace
> ---------------------------------------------------------------------
>
> Key: WFLY-9305
> URL: https://issues.jboss.org/browse/WFLY-9305
> Project: WildFly
> Issue Type: Bug
> Components: JCA, JMS, Naming
> Affects Versions: 14.0.0.Final, 15.0.0.Final
> Reporter: Jeff Mesnil
> Assignee: ehsavoie Hugonnet
> Priority: Major
>
> When using JMSDefinition defining a non-global JNDI name, Queue/Topic isn't created and MDB listening to those won't read incoming messages.
> Example using non global JNDI (this doesn't work (x) ):
> {code:java}
> @JMSDestinationDefinition(
> name = "java:app/jms/queue",
> interfaceName = "javax.jms.Queue"
> )
> {code}
> Example using global JNDI (this works (/)):
> {code:java}
> @JMSDestinationDefinition(
> name = "java:/app/jms/queue",
> interfaceName = "javax.jms.Queue"
> )
> {code}
> When using the non-global JNDI and deploying, a message like this can be seen:
> {noformat}
> 13:20:15,542 INFO [org.apache.activemq.artemis.ra] (default-threads - 2) AMQ151001: Attempting to reconnect org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.apache.activemq.artemis.ra.ActiveMQResourceAdapter@78712571 destination=java:app/jms/queue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15)
> {noformat}
> and creating an MDB to listen sent messages won't receive any.
> Attached a reproducer WAR Maven project. Just deploy, access index.xhtml, click on "Test" button and check logs.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFLY-11116) Wildfly 12.0.0 Final Delay in Getting the Value Attributes of the Session Variables (Result in Null Pointer Exception)
by Ziad Saade (Jira)
[ https://issues.jboss.org/browse/WFLY-11116?page=com.atlassian.jira.plugin... ]
Ziad Saade commented on WFLY-11116:
-----------------------------------
Dear Paul
Since Wildfly 15.0.0.Finals is released; I will check if the bug is still reproduced and I will let you know
Best Regards
> Wildfly 12.0.0 Final Delay in Getting the Value Attributes of the Session Variables (Result in Null Pointer Exception)
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11116
> URL: https://issues.jboss.org/browse/WFLY-11116
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 14.0.1.Final, 12.0.0.Final, 13.0.0.Final
> Reporter: Ziad Saade
> Assignee: Paul Ferraro
> Priority: Critical
>
> I have two Servlets Book and BookPreview the attribute is set in Book Servlet as follow:
>
> Book.java
> TestBean testBean=null;
> if(session.getAttribute("testBean")!=null)
> testBean = (TestBean)session.getAttribute("testBean");
> else{
> testBean=new TestBean();
> session.setAttribute("testBean",testBean);
> }
> testBean.setAmount("10");
>
> response.sendRedirect("BookPreview");
>
>
> The session attribute can be retrieved and the page is loaded normally and the Amount value is displayed however when submitting the form (Post Action in BookPreview.java) Null Pointer exception is generated.
>
> BookPreview.java
>
> TestBean testBean = (TestBean)session.getAttribute("testBean");
> String amount = testBean.getAmount; //Null pointer exception when submitting the form
>
> <form method="Post" action="BookPreview">
>
> </form>
>
> TestBean.java
>
> public class TestBean implements java.io.Serializable {
>
> private static final long serialVersionUID = 1L;
> private String amount;
>
> public String getAmount() {
> return amount;
> }
>
> public void setAmount(String amount) {
> this.amount = amount;
> }
> }
>
> Kindly advice how to fix the problem at the level of the server configuration.
> PS: I am not getting the exception when deploying the same application under other J EE application servers (Tomcat....)
>
> Thanks and Best Regards
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JGRP-2288) S3_PING: Under certain conditions, subclusters fail to merge after network partition
by Bela Ban (Jira)
[ https://issues.jboss.org/browse/JGRP-2288?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2288:
--------------------------------
I was able to reproduce this; but the real cause is that the change from sync to async discovery in {{MERGE3}} [1] led to {{FILE_PING}} correctly finding the members but never invoking the async callback in {{MERGE3}}. Therefore, a merge is never even triggered.
{{TCPPING.findMembers()}} works correctly, but {{FILE_PING.findMembers()}} doesn't.
[1] https://issues.jboss.org/browse/JGRP-2281
> S3_PING: Under certain conditions, subclusters fail to merge after network partition
> ------------------------------------------------------------------------------------
>
> Key: JGRP-2288
> URL: https://issues.jboss.org/browse/JGRP-2288
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.15
> Reporter: Nick Sawadsky
> Assignee: Bela Ban
> Priority: Major
> Fix For: 4.0.17
>
>
> Repro steps:
> 1. Set up a cluster of four nodes, two on one machine (Host 1) and two on another (Host 2). Let's call the nodes A, B, C, and D.
> 2. Configure all 4 nodes with S3_PING as the discovery mechanism. Set remove_all_files_on_view_change to true.
> 3. Start up nodes in the order A, B, C, D.
> 4. In the S3 bucket, there should be a single file with all four nodes listed. Node A should be flagged as the coordinator. Ensure that the UUID for node B is larger than the UUID for node C, when compared as two's complement integers. If this is not the case, shut down all nodes and restart in order. Repeat until the desired relationship is achieved. Note that with two's complement, a UUID having a first hex digit of 8 or higher is treated as negative for comparison purposes. So, for example, a UUID starting with 'a' is less than a UUID starting with 'b' which is less than a UUID starting with '1'.
> 5. On Host 1, use iptables to block all traffic going to and coming from Host 2.
> sudo iptables -A INPUT -s <Host 2 IP addr> -j DROP
> sudo iptables -A OUTPUT -d <Host 2 IP addr> -j DROP
> 6. Allow a few minutes for the nodes to detect the network partition. Eventually you should see two files in the S3 bucket.
> 7. Using Ctrl-C, stop node A.
> 8. You should soon find only a single file in the bucket, containing a single entry for node B. This is a result of the remove_all_files_on_view_change setting on S3_PING, which we set to true to avoid accumulation of old files in the bucket.
> 9. Resolve the network partition:
> sudo iptables -F OUTPUT
> sudo iptables -F INPUT
> 10. You will find that, even after many minutes, the subclusters are not merged.
> I believe the reason why the subclusters are never merged is as follows:
> - MERGE3 on nodes B, C and D uses S3_PING to find members to send INFO messages to. Each one finds only node B in the discovery file. As a result, only node B's view consistency checker has anything to work with.
> - On node B, the consistency checker can see that there are two coordinators, B and C. However, node C has a lower UUID, so node B defers to it to perform the merge. Node C never performs the merge because, as mentioned above, it is not receiving any INFO messages.
> I this this problem would affect FILE_PING as well, and other protocols derived from FILE_PING. Looking at the latest 4.x code, it appears the problem still exists there.
> I think the crux of the issue is that the coordinator on Host 2 (node C) does not re-create its discovery file after it is deleted by node B. Would it be reasonable for FILE_PING.findMembers() to create the discovery file if the node is a coordinator and the file doesn't exist?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3425) Unexpected behavior of docks when multiple editors are opened
by Klara Kufova (Jira)
[ https://issues.jboss.org/browse/DROOLS-3425?page=com.atlassian.jira.plugi... ]
Klara Kufova updated DROOLS-3425:
---------------------------------
Priority: Critical (was: Major)
> Unexpected behavior of docks when multiple editors are opened
> -------------------------------------------------------------
>
> Key: DROOLS-3425
> URL: https://issues.jboss.org/browse/DROOLS-3425
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor, Scenario Simulation and Testing
> Reporter: Klara Kufova
> Assignee: Toni Rikkola
> Priority: Critical
> Labels: ScenarioSimulation
> Attachments: screencast-11-12-18.webm
>
>
> When multiple assets are opened in different editors, their docks incorrectly interfere. After opening two assets in a row, the Business Central freezes with an unexpected error. Closing one asset causes unexpected disappearance of the left panel.
> See the attached screencast for detailed information. After the assets are opened for the first time, everything seems correct. Once the {{.dmn}} file is opened for the second time, the issues start to occur.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3425) Unexpected behavior of docks when multiple editors are opened
by Klara Kufova (Jira)
Klara Kufova created DROOLS-3425:
------------------------------------
Summary: Unexpected behavior of docks when multiple editors are opened
Key: DROOLS-3425
URL: https://issues.jboss.org/browse/DROOLS-3425
Project: Drools
Issue Type: Bug
Components: DMN Editor, Scenario Simulation and Testing
Reporter: Klara Kufova
Assignee: Toni Rikkola
Attachments: screencast-11-12-18.webm
When multiple assets are opened in different editors, their docks incorrectly interfere. After opening two assets in a row, the Business Central freezes with an unexpected error. Closing one asset causes unexpected disappearance of the left panel.
See the attached screencast for detailed information. After the assets are opened for the first time, everything seems correct. Once the {{.dmn}} file is opened for the second time, the issues start to occur.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFLY-11492) Quickstart http-custom-mechanism: documentation step fails
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/WFLY-11492?page=com.atlassian.jira.plugin... ]
Darran Lofthouse reassigned WFLY-11492:
---------------------------------------
Assignee: Darran Lofthouse
> Quickstart http-custom-mechanism: documentation step fails
> ----------------------------------------------------------
>
> Key: WFLY-11492
> URL: https://issues.jboss.org/browse/WFLY-11492
> Project: WildFly
> Issue Type: Bug
> Components: Documentation
> Reporter: Alan Hantke
> Assignee: Darran Lofthouse
> Priority: Minor
> Fix For: 16.0.0.Beta1
>
>
> Step #3, entitled *Configure the Application Security Domain* has the developer executing the following CLI command:
> {code:java}
> $ {jbossHomeName}/bin/jboss-cli.sh --connect --file=configure-security-domain.cli
> {code}
> However, this results in the following error:
> {code:java}
> The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error):
> WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:
> Step: step-1
> Operation: /subsystem=undertow/application-security-domain=other:add(http-authentication-factory=application-http-authentication)
> Failure: WFLYCTL0369: Required capabilities are not available:
> org.wildfly.security.http-authentication-factory.application-http-authentication; Possible registration points for this capability:
> /subsystem=elytron/http-authentication-factory=*
> {code}
> I am by no means an expert on this, but in looking at the standalone.xml file, I think that there needs to be a mate for the inserted *application-http-authentication*. I have attempted to continue without this changes installed by the CLI, but I am unable to execute the webapp even after providing the correct user/pass in the BASIC AUTH.
> I have verified that the same problem-causing syntax exists on the quickstart 'master', although I have been using branch '14.x' because neither 15.x nor 'master' would build when I execute 'mvn clean build'. Finally, the I encounter the problem with fresh installs of WildFly versions 10.1.0 and 14.0.
> Please change change the project if I have categorized the ticket incorrectly.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFLY-11492) Quickstart http-custom-mechanism: documentation step fails
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/WFLY-11492?page=com.atlassian.jira.plugin... ]
Darran Lofthouse updated WFLY-11492:
------------------------------------
Priority: Major (was: Minor)
> Quickstart http-custom-mechanism: documentation step fails
> ----------------------------------------------------------
>
> Key: WFLY-11492
> URL: https://issues.jboss.org/browse/WFLY-11492
> Project: WildFly
> Issue Type: Bug
> Components: Documentation
> Reporter: Alan Hantke
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 16.0.0.Beta1
>
>
> Step #3, entitled *Configure the Application Security Domain* has the developer executing the following CLI command:
> {code:java}
> $ {jbossHomeName}/bin/jboss-cli.sh --connect --file=configure-security-domain.cli
> {code}
> However, this results in the following error:
> {code:java}
> The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error):
> WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:
> Step: step-1
> Operation: /subsystem=undertow/application-security-domain=other:add(http-authentication-factory=application-http-authentication)
> Failure: WFLYCTL0369: Required capabilities are not available:
> org.wildfly.security.http-authentication-factory.application-http-authentication; Possible registration points for this capability:
> /subsystem=elytron/http-authentication-factory=*
> {code}
> I am by no means an expert on this, but in looking at the standalone.xml file, I think that there needs to be a mate for the inserted *application-http-authentication*. I have attempted to continue without this changes installed by the CLI, but I am unable to execute the webapp even after providing the correct user/pass in the BASIC AUTH.
> I have verified that the same problem-causing syntax exists on the quickstart 'master', although I have been using branch '14.x' because neither 15.x nor 'master' would build when I execute 'mvn clean build'. Finally, the I encounter the problem with fresh installs of WildFly versions 10.1.0 and 14.0.
> Please change change the project if I have categorized the ticket incorrectly.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months