[JBoss JIRA] (WFLY-6781) Wildfly cluster's failover functionality doesn't work as expected
by Preeta Kuruvilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-6781?page=com.atlassian.jira.plugin.... ]
Preeta Kuruvilla commented on WFLY-6781:
----------------------------------------
Hi Miroslav,
Yes it did bad on Node1 when Node2 is powered off. The JMS message on Node1 was not getting processed.
Thanks,
Preeta
> Wildfly cluster's failover functionality doesn't work as expected
> -----------------------------------------------------------------
>
> Key: WFLY-6781
> URL: https://issues.jboss.org/browse/WFLY-6781
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 8.2.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: domain.Node1.xml, host.Node1.xml, host.Node2.xml, server.RC.Node1.AfterFailover.log, server.RC.Node1.BeforeFailover.log, server.RC.Node2.AfterFailover.log, server.RC.Node2.BeforeFailover.log, server.SL.Node1.AfterFailover.log, server.SL.Node1.BeforeFailover.log
>
>
> Following are the testing scenarios we did and the outcome:-
> 1. Network disabling on a VM for testing failover – Not working for both Linux and Windows environment.
> 2. Power off of a VM using VMware client for testing failover – Is working on Linux environment but not working on windows environment.
> 3. Ctrl + C method to stop services on a node for testing failover – works on both linux and windows environment
> 4. Stopping server running on Node /VM using Admin Console for testing failover - works on both linux and windows environment.
> Jgroups subsystem configuration in domain.xml we have is below:-
> <subsystem xmlns="urn:jboss:domain:jgroups:2.0" default-stack="udp">
> <stack name="udp">
> <transport type="UDP" socket-binding="jgroups-udp"/>
> <protocol type="PING"/>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/>
> <protocol type="FD_ALL"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG2"/>
> <protocol type="RSVP"/>
> </stack>
> <stack name="tcp">
> <transport type="TCP" socket-binding="jgroups-tcp"/>
> <protocol type="MPING" socket-binding="jgroups-mping"/>
> <protocol type="MERGE2"/>
> <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/>
> <protocol type="FD"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="MFC"/>
> <protocol type="FRAG2"/>
> <protocol type="RSVP"/>
> </stack>
> </subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JGRP-2043) Improve performance of Message#readHeader
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2043?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2043:
--------------------------------
OK, created my own JMH test. MethodHandle.invokeExact() [1] showed the best perf, almost the same as directly calling the constructor:
{noformat}
Benchmark Mode Cnt Score Error Units
JGroupsBenchmark.createNormal avgt 5 25.426 ± 1.108 ns/op
JGroupsBenchmark.createWithConstructor avgt 5 271.742 ± 13.169 ns/op
JGroupsBenchmark.createWithMethodHandle avgt 5 266.403 ± 11.437 ns/op
JGroupsBenchmark.createWithMethodHandleInvokeExact avgt 5 25.102 ± 1.060 ns/op
JGroupsBenchmark.createWithMethodHandleInvokeExactAsType avgt 5 24.814 ± 1.085 ns/op
JGroupsBenchmark.createWithReflection avgt 5 302.597 ± 7.962 ns/op
{noformat}
[1] https://github.com/belaban/PerfTests/blob/master/src/main/java/org/perfte...
> Improve performance of Message#readHeader
> -----------------------------------------
>
> Key: JGRP-2043
> URL: https://issues.jboss.org/browse/JGRP-2043
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Sanne Grinovero
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 4.0
>
>
> A CPU hot spot highlighed by profiling via JFR:
> {noformat}Stack Trace Sample Count Percentage(%)
> java.lang.reflect.Constructor.newInstance(Object[]) 71 2.392
> java.lang.Class.newInstance() 71 2.392
> org.jgroups.Message.readHeader(DataInput) 71 2.392
> {noformat}
> I'd have expected the reflective constructor to perform well on a recent JVM, but apparently it's not in this case. A theory is that the {{Class}} type being unknown makes this code harder to optimise; needs to be looked into.
> It might be possible to patch the {{ClassConfigurator}} to provide instances of the required {{Header}} type rather than returning the class, and optimise that instead.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (DROOLS-1198) NoClassDefFoundError when using str[endsWith] on a field that matches an imported class name
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1198?page=com.atlassian.jira.plugi... ]
Matteo Mortari edited comment on DROOLS-1198 at 7/12/16 10:16 AM:
------------------------------------------------------------------
Thank you for your feedback; I've changed the line import into {{import mssp.io.model.*;}} and as by chance got hold on a Mac and I can confirm the problem indeed trigger on OSX, while it does not happen say on Linux, as per screenshots below.
!screenshot-linux.png|thumbnail! !screenshot-Mac.png|thumbnail!
I'm trying to synthesize a new reproducer accordingly to this platform difference.
was (Author: tari_manga):
Thank you for your feedback; I've changed the line import into {{import mssp.io.model.*;}} and as by chance got hold on a Mac and I can confirm the problem indeed trigger on OSX, while it does not happen say on Linux, as per screenshots below.
!screenshot-linux.png|thumbnail!
I'm trying to synthesize a new reproducer accordingly to this platform difference.
> NoClassDefFoundError when using str[endsWith] on a field that matches an imported class name
> --------------------------------------------------------------------------------------------
>
> Key: DROOLS-1198
> URL: https://issues.jboss.org/browse/DROOLS-1198
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.4.0.Final
> Reporter: Chris Austin
> Assignee: Mario Fusco
> Priority: Minor
> Attachments: DROOLS-1198-unabletoreproduce.zip, screenshot-linux.png, screenshot-Mac.png
>
>
> This error was triggered when accessing the user field with str[endsWith] when user is null:
> java.lang.NoClassDefFoundError: mssp/io/model/user (wrong name: mssp/io/model/User)
> Condition that triggers the error:
> $a : Alert(user!=null, user str[endsWith] "$")
> This does not trigger the error:
> $a : Alert(user!=null, user matches ".+\\$")
> If I remove the import for the User class the error will not be triggered. As a workaround I've switched to using matches instead of str[endsWith], but I'd prefer to switch back.
> I did not experience this issue in 6.3.0-Final, so it appears to be a regression in 6.4.0-Final
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (DROOLS-1198) NoClassDefFoundError when using str[endsWith] on a field that matches an imported class name
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1198?page=com.atlassian.jira.plugi... ]
Matteo Mortari commented on DROOLS-1198:
----------------------------------------
Thank you for your feedback; I've changed the line import into {{import mssp.io.model.*;}} and as by chance got hold on a Mac and I can confirm the problem indeed trigger on OSX, while it does not happen say on Linux, as per screenshots below.
!screenshot-linux.png|thumbnail!
I'm trying to synthesize a new reproducer accordingly to this platform difference.
> NoClassDefFoundError when using str[endsWith] on a field that matches an imported class name
> --------------------------------------------------------------------------------------------
>
> Key: DROOLS-1198
> URL: https://issues.jboss.org/browse/DROOLS-1198
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.4.0.Final
> Reporter: Chris Austin
> Assignee: Mario Fusco
> Priority: Minor
> Attachments: DROOLS-1198-unabletoreproduce.zip, screenshot-linux.png, screenshot-Mac.png
>
>
> This error was triggered when accessing the user field with str[endsWith] when user is null:
> java.lang.NoClassDefFoundError: mssp/io/model/user (wrong name: mssp/io/model/User)
> Condition that triggers the error:
> $a : Alert(user!=null, user str[endsWith] "$")
> This does not trigger the error:
> $a : Alert(user!=null, user matches ".+\\$")
> If I remove the import for the User class the error will not be triggered. As a workaround I've switched to using matches instead of str[endsWith], but I'd prefer to switch back.
> I did not experience this issue in 6.3.0-Final, so it appears to be a regression in 6.4.0-Final
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-6350) Configuration differences between default configuration and read/persisted in messaging and IIOP
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-6350?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-6350:
-----------------------------------
Fix Version/s: 10.1.0.Final
> Configuration differences between default configuration and read/persisted in messaging and IIOP
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-6350
> URL: https://issues.jboss.org/browse/WFLY-6350
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
> Fix For: 10.1.0.Final
>
>
> Following up on JBEAP-3093, there are still differences in these 2 subsystems:
> {noformat}
> 258a255
> > <orb socket-binding="iiop" ssl-socket-binding="iiop-ssl"/>
> 337c334
> < <role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> ---
> > <role name="guest" send="true" consume="true" create-non-durable-queue="true" delete-non-durable-queue="true"/>
> 339,341c336,338
> < <address-setting name="#" redistribution-delay="1000" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>
> < <http-connector name="http-connector" endpoint="http-acceptor" socket-binding="http"/>
> < <http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http">
> ---
> > <address-setting name="#" dead-letter-address="jms.queue.DLQ" expiry-address="jms.queue.ExpiryQueue" max-size-bytes="10485760" page-size-bytes="2097152" message-counter-history-day-limit="10" redistribution-delay="1000"/>
> > <http-connector name="http-connector" socket-binding="http" endpoint="http-acceptor"/>
> > <http-connector name="http-connector-throughput" socket-binding="http" endpoint="http-acceptor-throughput">
> 353c350
> < <cluster-connection name="my-cluster" discovery-group="dg-group1" connector-name="http-connector" address="jms"/>
> ---
> > <cluster-connection name="my-cluster" address="jms" connector-name="http-connector" discovery-group="dg-group1"/>
> 356,358c353,355
> < <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
> < <connection-factory name="RemoteConnectionFactory" reconnect-attempts="-1" block-on-acknowledge="true" ha="true" entries="java:jboss/exported/jms/RemoteConnectionFactory" connectors="http-connector"/>
> < <pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
> ---
> > <connection-factory name="InVmConnectionFactory" connectors="in-vm" entries="java:/ConnectionFactory"/>
> > <connection-factory name="RemoteConnectionFactory" ha="true" block-on-acknowledge="true" reconnect-attempts="-1" connectors="http-connector" entries="java:jboss/exported/jms/RemoteConnectionFactory"/>
> > <pooled-connection-factory name="activemq-ra" transaction="xa" connectors="in-vm" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory"/>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (DROOLS-1198) NoClassDefFoundError when using str[endsWith] on a field that matches an imported class name
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1198?page=com.atlassian.jira.plugi... ]
Matteo Mortari updated DROOLS-1198:
-----------------------------------
Attachment: screenshot-linux.png
> NoClassDefFoundError when using str[endsWith] on a field that matches an imported class name
> --------------------------------------------------------------------------------------------
>
> Key: DROOLS-1198
> URL: https://issues.jboss.org/browse/DROOLS-1198
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.4.0.Final
> Reporter: Chris Austin
> Assignee: Mario Fusco
> Priority: Minor
> Attachments: DROOLS-1198-unabletoreproduce.zip, screenshot-linux.png, screenshot-Mac.png
>
>
> This error was triggered when accessing the user field with str[endsWith] when user is null:
> java.lang.NoClassDefFoundError: mssp/io/model/user (wrong name: mssp/io/model/User)
> Condition that triggers the error:
> $a : Alert(user!=null, user str[endsWith] "$")
> This does not trigger the error:
> $a : Alert(user!=null, user matches ".+\\$")
> If I remove the import for the User class the error will not be triggered. As a workaround I've switched to using matches instead of str[endsWith], but I'd prefer to switch back.
> I did not experience this issue in 6.3.0-Final, so it appears to be a regression in 6.4.0-Final
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (DROOLS-1198) NoClassDefFoundError when using str[endsWith] on a field that matches an imported class name
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1198?page=com.atlassian.jira.plugi... ]
Matteo Mortari updated DROOLS-1198:
-----------------------------------
Attachment: screenshot-Mac.png
> NoClassDefFoundError when using str[endsWith] on a field that matches an imported class name
> --------------------------------------------------------------------------------------------
>
> Key: DROOLS-1198
> URL: https://issues.jboss.org/browse/DROOLS-1198
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.4.0.Final
> Reporter: Chris Austin
> Assignee: Mario Fusco
> Priority: Minor
> Attachments: DROOLS-1198-unabletoreproduce.zip, screenshot-Mac.png
>
>
> This error was triggered when accessing the user field with str[endsWith] when user is null:
> java.lang.NoClassDefFoundError: mssp/io/model/user (wrong name: mssp/io/model/User)
> Condition that triggers the error:
> $a : Alert(user!=null, user str[endsWith] "$")
> This does not trigger the error:
> $a : Alert(user!=null, user matches ".+\\$")
> If I remove the import for the User class the error will not be triggered. As a workaround I've switched to using matches instead of str[endsWith], but I'd prefer to switch back.
> I did not experience this issue in 6.3.0-Final, so it appears to be a regression in 6.4.0-Final
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-6823) Doesn't work using non-ASCII chars for username and/or password for BASIC authentication.
by Hynek Švábek (JIRA)
Hynek Švábek created WFLY-6823:
----------------------------------
Summary: Doesn't work using non-ASCII chars for username and/or password for BASIC authentication.
Key: WFLY-6823
URL: https://issues.jboss.org/browse/WFLY-6823
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Hynek Švábek
Assignee: Darran Lofthouse
Doesn't work using non-ASCII chars for username and/or password for BASIC authentication.
We noticed it when we looked on JIra issue https://issues.jboss.org/browse/JBEAP-3603.
We JBoss EAP 7 expects encoded UTF-8 strings in code. But we didn't find any information about it in specification.
It works with Chrome and Opera, but it doesn't work with Firefox.
Since there is no documentation for this username/password limitation it can affect customers who want to use non-ASCII credentials.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (DROOLS-1229) Event expiration cycles itself when expiring events from large set of same rules with "after" operator
by Tibor Zimányi (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1229?page=com.atlassian.jira.plugi... ]
Tibor Zimányi commented on DROOLS-1229:
---------------------------------------
PR with reproducer and proposed fix: https://github.com/droolsjbpm/drools/pull/832
> Event expiration cycles itself when expiring events from large set of same rules with "after" operator
> ------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-1229
> URL: https://issues.jboss.org/browse/DROOLS-1229
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.4.0.Final
> Reporter: Tibor Zimányi
> Assignee: Mario Fusco
>
> When using many same rules with after, event expiration cycles itself.
> Using 64 copies of this rule [1], code here [2] cycles itself. I think it is because when it searches through child and peer tuples, it can find already expired tuple and it tries to expire it again. So the problem is either there or in that there is some cycle in tuple chain.
> [1]
> import org.drools.testcoverage.common.model.EventA;
> import org.drools.testcoverage.common.model.EventB;
> declare org.drools.testcoverage.common.model.EventA @role( event ) @duration(duration) end declare org.drools.testcoverage.common.model.EventB @role( event ) @duration(duration) end rule R0 when
> $event1: org.drools.testcoverage.common.model.EventA()
> $event2: org.drools.testcoverage.common.model.EventB(this != $event1, this after [1,10] $event1)
> then end
> [2] https://github.com/droolsjbpm/drools/blob/master/drools-core/src/main/jav...
> I will make a PR with reproducer and proposed fix for this.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-6815) JDOM cannot create default parser
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/WFLY-6815?page=com.atlassian.jira.plugin.... ]
Thomas Diesler reopened WFLY-6815:
----------------------------------
> JDOM cannot create default parser
> ---------------------------------
>
> Key: WFLY-6815
> URL: https://issues.jboss.org/browse/WFLY-6815
> Project: WildFly
> Issue Type: Sub-task
> Components: Build System
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Fix For: 10.1.0.Final
>
>
> Happens when a tool accesses the org.jdom module
> {code}
> org.jdom.JDOMException: Could not load default SAX parser: org.apache.xerces.parsers.SAXParser: SAX2 driver class org.apache.xerces.parsers.SAXParser not found: org.apache.xerces.parsers.SAXParser from [Module "org.wildfly.extras.config:main" from local module loader @a3d8174 (finder: local module finder @1ba9117e (roots: /Users/tdiesler/git/wildfly-camel/itests/standalone/smoke/target/wildfly-10.1.0.Final-SNAPSHOT/modules,/Users/tdiesler/git/wildfly-camel/itests/standalone/smoke/target/wildfly-10.1.0.Final-SNAPSHOT/modules/system/layers/fuse,/Users/tdiesler/git/wildfly-camel/itests/standalone/smoke/target/wildfly-10.1.0.Final-SNAPSHOT/modules/system/layers/base))]
> at org.jdom.input.SAXBuilder.createParser(SAXBuilder.java:649)
> at org.jdom.input.SAXBuilder.build(SAXBuilder.java:489)
> at org.jdom.input.SAXBuilder.build(SAXBuilder.java:905)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months