December 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1229) Reloading the embed host controller logs ERROR messages

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1229?page=com.atlassian.jira.plugi... ] Ken Wills commented on WFCORE-1229: ----------------------------------- I am able to get this to log if I start 3 concurrent instances (doesn't happen with < 3) of the test, I'm investigating. > Reloading the embed host controller logs ERROR messages > ------------------------------------------------------- > > Key: WFCORE-1229 > URL: https://issues.jboss.org/browse/WFCORE-1229 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.2.Final > Reporter: Petr Kremensky > Assignee: Ken Wills > > Embed host controller sometime logs ERROR message while booting up after the reload ('reload --host=master --admin-only=true'). > {noformat} > ERROR [org.jboss.as.controller.management-operation] (main) WFLYCTL0013: Operation ("read-attribute") failed - address: ([("host" => "master")]) - failure description: "WFLYCTL0030: No resource definition is registered for address [(\"host\" => \"master\")]" > {noformat} > My initial thought on this was that issue is reproducible only on virtualized systems as I saw the error only a few times on my local machine, but I tried some bare-metal servers in MWQE lab and the error poped-up quite often there. > *Reproducer job* (#6 and #7 ran with 7.0.0.ER2 bits) : > \- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-cli-embed-hos... > In extreme cases, error can appear after every other reload operation (46 out of 99) > \- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-cli-embed-hos... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5862) Update Javax.mail to 1.5.4

by Erick de Oliveira Leal (JIRA)

Erick de Oliveira Leal created WFLY-5862: -------------------------------------------- Summary: Update Javax.mail to 1.5.4 Key: WFLY-5862 URL: https://issues.jboss.org/browse/WFLY-5862 Project: WildFly Issue Type: Component Upgrade Components: EE, Mail Affects Versions: 10.0.0.CR4 Reporter: Erick de Oliveira Leal Assignee: Tomaz Cerar Fix For: 10.0.0.CR5 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5452) Sometimes the calling javax.security.auth.login.Configuration.getConfiguration() fails with SecurityException in our tests

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5452?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-5452: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1268222|https://bugzilla.redhat.com/show_bug.cgi?id=1268222] from MODIFIED to ON_QA > Sometimes the calling javax.security.auth.login.Configuration.getConfiguration() fails with SecurityException in our tests > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-5452 > URL: https://issues.jboss.org/browse/WFLY-5452 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 10.0.0.CR2 > Reporter: Ondrej Lukas > Assignee: Ondrej Lukas > Fix For: 10.0.0.CR4 > > > Sometimes the calling javax.security.auth.login.Configuration.getConfiguration() fails with SecurityException in our tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-868) CLI if/else is not handling special characters strings with parenthesis

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-868?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-868: ------------------------------------------------ Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1249773|https://bugzilla.redhat.com/show_bug.cgi?id=1249773] from MODIFIED to ON_QA > CLI if/else is not handling special characters strings with parenthesis > ----------------------------------------------------------------------- > > Key: WFCORE-868 > URL: https://issues.jboss.org/browse/WFCORE-868 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.0.Alpha12 > Reporter: Tomas Hofman > Assignee: Alexey Loubyansky > Fix For: 2.0.0.Beta7 > > > When using CLI if-else scripting that uses a string that contains parenthesis it fails with the following message: > Failed to handle 'if (outcome == success && result.value != "a64180c0)e7187af86b435229de904104") of /system-property=test:read-resource': Unexpected operation at 49 in '(outcome == success && result.value != "a64180c0)e7187af86b435229de904104")' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-851) Remoting Subsystem RemoteOutboundConnectionService is caching ConnectionURI causing issues when DNS changes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-851?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-851: ------------------------------------------------ Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1248156|https://bugzilla.redhat.com/show_bug.cgi?id=1248156] from MODIFIED to ON_QA > Remoting Subsystem RemoteOutboundConnectionService is caching ConnectionURI causing issues when DNS changes > ----------------------------------------------------------------------------------------------------------- > > Key: WFCORE-851 > URL: https://issues.jboss.org/browse/WFCORE-851 > Project: WildFly Core > Issue Type: Bug > Components: Remoting > Reporter: Brad Maxwell > Assignee: David Lloyd > > Description of problem: > EJB CLient was configured with DNS FQDN to configure access to a remote EJB. If run a simple test adding an entry in /etc/hosts file pointing that FQDN to localhost for tests everything works. However, after finish the tests and remove the entry, the client still connects to localhost instead of resolve the new IP address. Even adding networkaddress.cache.ttl=30 inside security settings didn't work too. > How reproducible: > Everytime you use DNS names to connect to a remote EJB. > Steps to Reproduce: > 1. Configure a simple client that connects to a remote EJB using dns name > 2. add an entry in /etc/hosts mapping the dns name to localhost > 3. run the client code > 4. remove the entry in /etc/hosts > 5. run the client code again > Actual results: > EJB remote is still reached from localhost > Expected results: > After changing DNS record EJB will be reached in this new address -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5607) EJB Server side is needlessly closing remoting channel

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5607?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-5607: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1276513|https://bugzilla.redhat.com/show_bug.cgi?id=1276513] from MODIFIED to ON_QA > EJB Server side is needlessly closing remoting channel > ------------------------------------------------------ > > Key: WFLY-5607 > URL: https://issues.jboss.org/browse/WFLY-5607 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.CR4 > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Fix For: 10.0.0.CR5 > > > When an EJB Bean throws a Runtime exception, it is causing the server side to close the remoting channel. This causes several issues such as performance issue of having to recreate the channel, channel leak on the client side and some occasional EJBCLIENT...25 - no ejb receiver exceptions on the client side. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5596) MessageDrivenComponent startDelivery/stopDelivery is not thread safe

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5596?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-5596: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1282661|https://bugzilla.redhat.com/show_bug.cgi?id=1282661] from MODIFIED to ON_QA > MessageDrivenComponent startDelivery/stopDelivery is not thread safe > -------------------------------------------------------------------- > > Key: WFLY-5596 > URL: https://issues.jboss.org/browse/WFLY-5596 > Project: WildFly > Issue Type: Bug > Components: EJB, JMS > Affects Versions: 10.0.0.CR4 > Reporter: James Livingston > Assignee: Jeff Mesnil > > WFLY-4470 made a change to prevent MDBs being activated or deactivated multiple times, but it is not thread safe. A volatile boolean is used for the flag, but there is no protection against multiple threads invoking the methods simultaneously. > Possible effects include: > * activating the endpoint twice, with (probably) only one deactivation later, leading to not de-registering XA resources from the recovery manager properly > * activate() and deactivate() running in the wrong order if done by separate threads > Several simple solutions probably will not work correctly. Using an AtomicBoolean would stop multiple activations/deactivations from concurrent calls, but would mean that startDelivery() could return before the activation was one. Using a synchronized block or other exclusive lock would work, however since it involves invoking non-container code (the resource adapter), there could potentially be a deadlock risk if that invoked some related container functionality. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1294) caching the value of isTraceEnabled

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1294?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1294: ------------------------------------------------ Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1259840|https://bugzilla.redhat.com/show_bug.cgi?id=1259840] from MODIFIED to ON_QA > caching the value of isTraceEnabled > ----------------------------------- > > Key: JBJCA-1294 > URL: https://issues.jboss.org/browse/JBJCA-1294 > Project: IronJacamar > Issue Type: Bug > Affects Versions: 1.2.6.Final > Reporter: Johnathon Lee > Assignee: Bartosz Baranowski > Fix For: WildFly/IronJacamar 1.3.2.Final, 1.0.35.Final > > > caching the value of isTraceEnabled does not allow for complete dynamic control of the logging level. This has ramifications in support scenarios where diagnostics are needed and the ability to reload an instance to enable TRACE level logging is prohibitive. > see examples of TRACE being cached: > grep 'log.isTraceEnabled();' -r * --include='*.java' > Replacement of all if (trace) with calls to log.tracef would be needed. > Note, that some "if (trace)" would have to be replaced by if (log.isTraceEnabled()) calls, as they guard multiple lines of code, and even synchronization blocks -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4839) annotation must be scanned regardless of the version of web.xml unless metadata-complete is explicitly set to true

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4839?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4839: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1235627|https://bugzilla.redhat.com/show_bug.cgi?id=1235627] from MODIFIED to ON_QA > annotation must be scanned regardless of the version of web.xml unless metadata-complete is explicitly set to true > ------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-4839 > URL: https://issues.jboss.org/browse/WFLY-4839 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Alpha4 > Reporter: Chao Wang > Assignee: Chao Wang > Fix For: 10.0.0.Beta2 > > > {noformat} > ### Description of problem: > Annotation must be scanned regardless of the version of web.xml unless metadata-complete is explicitly set to true. > Note that Servlet 3.0 specification clearly states the following: > ~~~ > 1.6.2 Processing annotations > In Servlet 2.5, metadata-complete only affected the scanning of annotations at > deployment time. The notion of web-fragments did not exist in servlet 2.5. However > in servlet 3.0 metadata-complete affects scanning of all annotations and web- > fragments at deployment time. The version of the descriptor MUST not affect which > annotations you scan for in a web application. An implementation of a particular > version of the specification MUST scan for all annotations supported in that > configuration, unless metadata-complete is specified. > ~~~ > ### How reproducible: > Anytime > ### Steps to Reproduce: > 1. Create a library jar which contains a servlet filter using @WebFilter > 2. Put the jar under WEB-INF/lib of the web application which web.xml version is 2.3 or 2.4 > 3. Start JBoss EAP 6 > 4. Access the web application and see if the servlet filter works > ### Actual results: > The servlet filter is not invoked > ### Expected results: > The servlet filter is invoked > ### Additional info: > It works when the version of web.xml is 2.5 or 3.0 > [reply] [−] > Private > Comment 1 Masafumi Miura 2015-06-25 07:18:17 EDT > RED HAT CONFIDENTIAL > It looks metadata-complete is always set to true when the version of web.xml is 2.3 or 2.4 at the line 96 of web/src/main/java/org/jboss/as/web/deployment/WarMetaDataProcessor.java. > Though Servlet 2.3/2.3 specification does not have metadata-complete attribute, Servlet 3.0 specification states the following. I think it means that the metadata-complete attribute default to false if it is not specified. > ~~~ > 8.1 Annotations and pluggability > if the metadata-complete attribute is not specified or is set to "false", the > deployment tool must examine the class files of the application for annotations, and > scan for web fragments. > ~~~ > * web/src/main/java/org/jboss/as/web/deployment/WarMetaDataProcessor.java > 76 public class WarMetaDataProcessor implements DeploymentUnitProcessor { > 77 > 78 @Override > 79 public void deploy(DeploymentPhaseContext phaseContext) throws DeploymentUnitProcessingException { > ... > 87 boolean isComplete = false; > 88 WebMetaData specMetaData = warMetaData.getWebMetaData(); > 89 if (specMetaData != null) { > 90 if (specMetaData instanceof Web25MetaData) { > 91 isComplete |= ((Web25MetaData) specMetaData).isMetadataComplete(); > 92 } else if (specMetaData instanceof Web30MetaData) { > 93 isComplete |= ((Web30MetaData) specMetaData).isMetadataComplete(); > 94 } else { > 95 // Any web.xml 2.4 or earlier deployment is metadata complete > 96 isComplete = true; > 97 } > 98 } > 99 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5498) Transaction probe needlessly locks CLI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5498?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-5498: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1270281|https://bugzilla.redhat.com/show_bug.cgi?id=1270281] from MODIFIED to ON_QA > Transaction probe needlessly locks CLI > -------------------------------------- > > Key: WFLY-5498 > URL: https://issues.jboss.org/browse/WFLY-5498 > Project: WildFly > Issue Type: Bug > Reporter: Aaron Ogburn > Assignee: Jason Greene > Fix For: 10.0.0.CR3 > > > A transaction probe grabs the controller lock before proceeding. Transaction probes may see long run times depending upon db responsiveness. So other CLI operations can end up needlessly blocked for quite some time waiting for the db to respond for a transaction probe to proceed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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