July 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-783) Intermittent Disconnection from CLI After Reload

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-783?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-783: ------------------------------------------------ Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1232933|https://bugzilla.redhat.com/show_bug.cgi?id=1232933] from ON_QA to ASSIGNED > Intermittent Disconnection from CLI After Reload > ------------------------------------------------- > > Key: WFCORE-783 > URL: https://issues.jboss.org/browse/WFCORE-783 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.0.Alpha5 > Reporter: Joe Wertz > Assignee: Joe Wertz > Fix For: 2.0.0.Alpha8 > > > Race condition in server reload. The CLI only waits for a connection to be established and does not check the server status before continuing to execute commands. If the next command is executed before the server had completed the reload, failures occur. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1548) Add fallback querry to jconsole plugin

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1548?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-1548: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=901311, https://bugzilla.redhat.com/show_bug.cgi?id=1215278 (was: https://bugzilla.redhat.com/show_bug.cgi?id=901311) > Add fallback querry to jconsole plugin > -------------------------------------- > > Key: WFLY-1548 > URL: https://issues.jboss.org/browse/WFLY-1548 > Project: WildFly > Issue Type: Enhancement > Affects Versions: 8.0.0.Alpha1 > Reporter: Bartosz Baranowski > Assignee: Darran Lofthouse > Labels: JConsole, JMX, Plugin > Fix For: 8.0.0.Beta1 > > > JConsolePlugin connecects to default port, despite chance to use proper info. > Problem: > Unless I miss somethingm JConsole has a bit tight isolation between components. There is no way for AS7 JConsolePlugin to access "connect dialog" info. Hence it has no idea what is the content of URL being passed as remote. > AS7 JConsolePlugin checks if MBeanServerConnection is instance of RemotinConnection. If its not, it fallbacks to default: localhost:9990. > However we can check for socket bindings and try to connect to proper socket. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-450) Using parent system properties in child properties fails in domain server launch

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-450?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-450: ------------------------------------------------ Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1230980|https://bugzilla.redhat.com/show_bug.cgi?id=1230980] from ON_QA to VERIFIED > Using parent system properties in child properties fails in domain server launch > -------------------------------------------------------------------------------- > > Key: WFCORE-450 > URL: https://issues.jboss.org/browse/WFCORE-450 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Samuli Saarinen > Assignee: Brian Stansberry > Fix For: 1.0.0.Alpha15 > > Attachments: domain.xml.patch, host-controller.log > > > Using wildfly domain I would like to define some properties in domain.xml and then be able to use these properties when defining others in server-group or server level. Currently this leads to JBAS014802: Cannot resolve expression. > More detailed example: > {code:xml|title=domain.xml} > <domain> > <system-properties> > <property name="foo" value="bar"/> > </system-properties> > ... > <server-group name="g1"> > <system-properties> > <property name="g1_foo" value="${foo}"/> > </system-properties> > </server-group> > </domain> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4815) AdvancedLdapLoginModuleTestCase fails on RHEL5 and IBM JDK

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4815?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4815: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1206177|https://bugzilla.redhat.com/show_bug.cgi?id=1206177] from ON_QA to VERIFIED > AdvancedLdapLoginModuleTestCase fails on RHEL5 and IBM JDK > ----------------------------------------------------------- > > Key: WFLY-4815 > URL: https://issues.jboss.org/browse/WFLY-4815 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 10.0.0.Alpha3 > Environment: IBM JDK on RHEL 5 (both x86 and x86_64) > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 10.0.0.Alpha5 > > > Upstream of https://bugzilla.redhat.com/show_bug.cgi?id=1206177 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-668) Make the INFO logging from deprecated attributes configurable, also improve the message

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-668?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-668: ------------------------------------------------ Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1213421|https://bugzilla.redhat.com/show_bug.cgi?id=1213421] from ON_QA to VERIFIED > Make the INFO logging from deprecated attributes configurable, also improve the message > --------------------------------------------------------------------------------------- > > Key: WFCORE-668 > URL: https://issues.jboss.org/browse/WFCORE-668 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 1.0.0.Final, 2.0.0.Alpha3 > > > The INFO logging that AttributeDefinition generates when a deprecated attribute is used needs to be configurable, i.e. with a boolean flag so a dev can turn it off for attributes where it serves no purpose. > The logging only serves a purpose if an admin can take action to use some alternative config. If an attribute is deprecated only because in some future release it will go away, but there's no replacement now, the logging is just noise. > The log message itself should be improved: > 1) Get rid of the ! at the end. It's not that exciting. ;) > 2) Include the address of the resource > 3) Point the user at the read-resource-description output from which they can learn more about the deprecation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1946) Auth succeeds when the node without auth starts first

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1946?page=com.atlassian.jira.plugin.... ] Bela Ban closed JGRP-1946. -------------------------- Resolution: Rejected > Auth succeeds when the node without auth starts first > ----------------------------------------------------- > > Key: JGRP-1946 > URL: https://issues.jboss.org/browse/JGRP-1946 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 3.6.4 > Environment: jdk 1.7 > Reporter: fatih fatih > Assignee: Bela Ban > Fix For: 3.6.5 > > Attachments: HAController2.java, udp.xml, udp.xml > > > Node starts without auth it becomes coordinator of its cluster > In the same cluster another node starts with X509 Auth > The node starting with auth succeeds to join to the cluster that is started by the first node instead of creating its own cluster. > The purpose is not to allow the nodes that is with auth and the nodes that is without auth to join with each other. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1946) Auth succeeds when the node without auth starts first

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1946?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1946: -------------------------------- This is not a supported use case. If the coordinator doesn't have {{AUTH}}, then it won't be able to authorize access to the cluster. > Auth succeeds when the node without auth starts first > ----------------------------------------------------- > > Key: JGRP-1946 > URL: https://issues.jboss.org/browse/JGRP-1946 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 3.6.4 > Environment: jdk 1.7 > Reporter: fatih fatih > Assignee: Bela Ban > Fix For: 3.6.5 > > Attachments: HAController2.java, udp.xml, udp.xml > > > Node starts without auth it becomes coordinator of its cluster > In the same cluster another node starts with X509 Auth > The node starting with auth succeeds to join to the cluster that is started by the first node instead of creating its own cluster. > The purpose is not to allow the nodes that is with auth and the nodes that is without auth to join with each other. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1947) JGRP000006 errors triggered by nmap TCP Connect scanning JGroups ports

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1947?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1947: -------------------------------- What's wrong with "failed accepting connection from peer" versus "peer reset connection" ? Actually, the latter is incorrect, because the peer wasn't even connected yet, whereas the first message is correct as the peer (nmap) tried to establish a connection and the accept() at the server side failed... > JGRP000006 errors triggered by nmap TCP Connect scanning JGroups ports > ---------------------------------------------------------------------- > > Key: JGRP-1947 > URL: https://issues.jboss.org/browse/JGRP-1947 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4.6 > Environment: Java 7u80 x32 > Tomcat 7.0.62 > HA-JDBC 3.0.4-SNAPSHOT + JGroups 3.4.6 > nmap 5.5.1 > Reporter: Justin Cranford > Assignee: Bela Ban > Fix For: 3.6.5 > > > I am running a two node Tomcat cluster. Both JGroups and Hazelcast are used for different parts of application clustering - JGroups for HA-JDBC, and Hazelcast for application locks outside of HA-JDBC. > Hazelcast is not relevant to JGroups, except I included the Hazelcast errors because they happen at the same time as the JGroups JGRP000006 errors. This gave me a hint of why I see JGRP000006, because the Hazelcast error is more specific about root cause. > Basically if I run a nmap TCP Connect scan on my servers like so, this opens/closes empty TCP connections. JGroups reports these events as JGRP000006, whereas Hazelcast reports them as "java.io.IOException[Connection reset by peer]". > I am wondering if JGroups can handle these nmap TCP Connect scans more gracefully, or even log a more descriptive error with the JGRP000006 error code. > My Tomcat errors for both JGroups and Hazelcast > Jul 31, 2015 12:27:52 AM com.hazelcast.nio.SocketAcceptor > INFO: [10.0.0.85]:5900 [ClusterManager] [3.2.4] Accepting socket connection from /10.0.0.86:40527 > Jul 31, 2015 12:27:52 AM com.hazelcast.nio.TcpIpConnectionManager > INFO: [10.0.0.85]:5900 [ClusterManager] [3.2.4] 5900 accepted socket connection from /10.0.0.86:40527 > Jul 31, 2015 12:27:52 AM org.jgroups.logging.JDKLogImpl warn > WARNING: JGRP000006: failed accepting connection from peer > java.net.SocketException: Connection reset > at java.net.SocketInputStream.read(Unknown Source) > at java.net.SocketInputStream.read(Unknown Source) > at java.io.BufferedInputStream.fill(Unknown Source) > at java.io.BufferedInputStream.read1(Unknown Source) > at java.io.BufferedInputStream.read(Unknown Source) > at java.io.DataInputStream.readFully(Unknown Source) > at org.jgroups.blocks.TCPConnectionMap$TCPConnection.readPeerAddress(TCPConnectionMap.java:494) > at org.jgroups.blocks.TCPConnectionMap$TCPConnection.<init>(TCPConnectionMap.java:376) > at org.jgroups.blocks.TCPConnectionMap$Acceptor.handleAccept(TCPConnectionMap.java:298) > at org.jgroups.blocks.TCPConnectionMap$Acceptor.run(TCPConnectionMap.java:282) > at java.lang.Thread.run(Unknown Source) > Jul 31, 2015 12:27:52 AM com.hazelcast.nio.TcpIpConnection > INFO: [10.0.0.85]:5900 [ClusterManager] [3.2.4] Connection [/10.0.0.86:40527] lost. Reason: java.io.IOException[Connection reset by peer] > My nmap scan which triggers the JGRP000006 errors: > root@myserver:~$ nmap -n -T4 -sT -PN --max-scan-delay 0ms --min-rate 1000000 --max-retries 0 -p 443,3306,5900,7900,7901 10.0.0.85 > Starting Nmap 5.51 ( http://nmap.org ) at 2015-07-31 01:33 UTC > Cannot find nmap-payloads. UDP payloads are disabled. > Nmap scan report for 10.0.0.85 > Host is up (0.00035s latency). > PORT STATE SERVICE > 443/tcp open https > 3306/tcp open mysql > 5900/tcp open vnc > 7900/tcp open mevent > 7901/tcp open unknown > Nmap done: 1 IP address (1 host up) scanned in 0.04 seconds -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-866) Drools decision table with contains operator in a conditional group not working

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-866?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-866: ---------------------------------- Assignee: Michael Anstis (was: Mario Fusco) > Drools decision table with contains operator in a conditional group not working > ------------------------------------------------------------------------------- > > Key: DROOLS-866 > URL: https://issues.jboss.org/browse/DROOLS-866 > Project: Drools > Issue Type: Bug > Components: decision tables > Affects Versions: 6.2.0.Final > Environment: Windows 7 > Reporter: lucio piccoli > Assignee: Michael Anstis > Attachments: FeePricing-grouping-error.xls, PricingRuleGroupingExample.java > > > I cannot get the Decision Table to using grouping in the expression. > Decision Table > ------------------------------------ > <row 10> CONDITION > <row 12> classList $param > expressions are in each row. > <row 43> (contains('AAA') || contains('BBB') ) && contains('CCC') <--fails to compile > <row 44> (contains('AAA') || contains('BBB') > <row 45> (contains('AA') || contains('BB') || contains('CCC') || contains('DDD') > where the fact classList is > List<String> classList = {'AAA', 'BB'.....} > the rule43 is meant to fire if the list contains either 'AAA' OR 'BBB' AND 'CCC' > however the decision table parser is failing with exception for rule 43 > [Error: Missing left node] > [Near : {... classList (contains("AAA") || contains("CCC")) ....}] > i have a similar rule working fine for other rows > <row 42> contains('AAA') || contains('BBB') || contains('CCC') > there seems to be something strange with using the contains operator in a group condition. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-618) Thread deadlock on org.drools.util.CompositeClassLoader

by kevin li (JIRA)

[ https://issues.jboss.org/browse/DROOLS-618?page=com.atlassian.jira.plugin... ] kevin li commented on DROOLS-618: --------------------------------- Thanks for your reply, and changing dialect from java to mvel can avoid that problem. > Thread deadlock on org.drools.util.CompositeClassLoader > ------------------------------------------------------- > > Key: DROOLS-618 > URL: https://issues.jboss.org/browse/DROOLS-618 > Project: Drools > Issue Type: Bug > Affects Versions: 5.6.0.Final > Environment: drools expert > Reporter: Shashank Agarwal > Assignee: Mark Proctor > Attachments: http-54350-Processor15.txt, http-54350-Processor18.txt, http-54350-Processor20.txt > > > Sometimes we are facing issues of thread deadlock due to which our application goes unresponsive. Drools version 5.6.0 > Below is the deadlock statements detected by jconsole, also attached full tread dumps. There three threads are deadlocked triangularly. > Name: http-54350-Processor15 > State: BLOCKED on org.drools.rule.JavaDialectRuntimeData$PackageClassLoader@1d5787a owned by: http-54350-Processor18 > Name: http-54350-Processor18 > State: WAITING on java.util.concurrent.locks.ReentrantLock$NonfairSync@3cda324d owned by: http-54350-Processor15 > Name: http-54350-Processor20 > State: BLOCKED on org.drools.util.CompositeClassLoader@61269654 owned by: http-54350-Processor15 > We do not have definite threads to re-produce the issue. > But deadlocks are happening repeatedly on our production. > Regarding out environment details: > 1. We have windows box on which application runs. > 2. The rules used are kept in .drl and .xls formats > 3. Call StatefulKnowledgeSession session = base.newStatefulKnowledgeSession(); > 4. Setup a few session globals as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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 July 2015