February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8148) Intermittent failure in InterDeploymentDependenciesEarTestCase

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8148?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-8148: ----------------------------------- Comment: was deleted (was: Never mind the previous comment; it still fails intermittently, although the WFLY-8149 fix does prevent the failure resulting in 200 other tests failing.) > Intermittent failure in InterDeploymentDependenciesEarTestCase > -------------------------------------------------------------- > > Key: WFLY-8148 > URL: https://issues.jboss.org/browse/WFLY-8148 > Project: WildFly > Issue Type: Bug > Components: EE, Test Suite > Reporter: Brian Stansberry > > On a fairly frequent basis we are seeing failures in InterDeploymentDependenciesEarTestCase. This then seems to be followed by ~ 200 other failures. > https://ci.wildfly.org/viewLog.html?buildId=46213&buildTypeId=WildFlyCore... is an example. > Pattern is: > Failure: > {code} > javax.ejb.NoSuchEJBException: No such EJB: app2/hello/LogAccessBean > at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:354) > at org.jboss.ejb.client.TransactionInterceptor.handleInvocationResult(TransactionInterceptor.java:75) > at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:357) > at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:608) > at org.jboss.ejb.client.EJBInvocationHandler.lambda$invoke$0(EJBInvocationHandler.java:164) > at org.jboss.ejb.client.EJBClientContext.discoverAffinityNone(EJBClientContext.java:428) > at org.jboss.ejb.client.EJBClientContext.performLocatedAction(EJBClientContext.java:387) > at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:150) > at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:100) > at com.sun.proxy.$Proxy65.getLog(Unknown Source) > at org.jboss.as.test.integration.deployment.dependencies.ear.InterDeploymentDependenciesEarTestCase.test(InterDeploymentDependenciesEarTestCase.java:127) > {code} > Earliest failure I see with this pattern in the TeamCity history is from Aug 17, 2016. But such failures were confined to JDK9 runs and stopped last Sept 2. Then they start appearing quite frequently on Feb 6, 2017. First appearance was in a test of PR #9600, but there are other failures before that PR was merged so I doubt that PR is relevant. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8148) Intermittent failure in InterDeploymentDependenciesEarTestCase

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8148?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-8148: ----------------------------------- Comment: was deleted (was: Before anyone spends time on this, I recommend checking if this test stills fails after my WFLY-8149 fix. I don't have a good reason to think it won't, but TBH I don't understand why the changes I made to the original contributor PR for that issue had the effect it did.) > Intermittent failure in InterDeploymentDependenciesEarTestCase > -------------------------------------------------------------- > > Key: WFLY-8148 > URL: https://issues.jboss.org/browse/WFLY-8148 > Project: WildFly > Issue Type: Bug > Components: EE, Test Suite > Reporter: Brian Stansberry > > On a fairly frequent basis we are seeing failures in InterDeploymentDependenciesEarTestCase. This then seems to be followed by ~ 200 other failures. > https://ci.wildfly.org/viewLog.html?buildId=46213&buildTypeId=WildFlyCore... is an example. > Pattern is: > Failure: > {code} > javax.ejb.NoSuchEJBException: No such EJB: app2/hello/LogAccessBean > at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:354) > at org.jboss.ejb.client.TransactionInterceptor.handleInvocationResult(TransactionInterceptor.java:75) > at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:357) > at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:608) > at org.jboss.ejb.client.EJBInvocationHandler.lambda$invoke$0(EJBInvocationHandler.java:164) > at org.jboss.ejb.client.EJBClientContext.discoverAffinityNone(EJBClientContext.java:428) > at org.jboss.ejb.client.EJBClientContext.performLocatedAction(EJBClientContext.java:387) > at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:150) > at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:100) > at com.sun.proxy.$Proxy65.getLog(Unknown Source) > at org.jboss.as.test.integration.deployment.dependencies.ear.InterDeploymentDependenciesEarTestCase.test(InterDeploymentDependenciesEarTestCase.java:127) > {code} > Earliest failure I see with this pattern in the TeamCity history is from Aug 17, 2016. But such failures were confined to JDK9 runs and stopped last Sept 2. Then they start appearing quite frequently on Feb 6, 2017. First appearance was in a test of PR #9600, but there are other failures before that PR was merged so I doubt that PR is relevant. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8148) Intermittent failure in InterDeploymentDependenciesEarTestCase

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8148?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-8148: ---------------------------------------- Never mind the previous comment; it still fails intermittently, although the WFLY-8149 fix does prevent the failure resulting in 200 other tests failing. > Intermittent failure in InterDeploymentDependenciesEarTestCase > -------------------------------------------------------------- > > Key: WFLY-8148 > URL: https://issues.jboss.org/browse/WFLY-8148 > Project: WildFly > Issue Type: Bug > Components: EE, Test Suite > Reporter: Brian Stansberry > > On a fairly frequent basis we are seeing failures in InterDeploymentDependenciesEarTestCase. This then seems to be followed by ~ 200 other failures. > https://ci.wildfly.org/viewLog.html?buildId=46213&buildTypeId=WildFlyCore... is an example. > Pattern is: > Failure: > {code} > javax.ejb.NoSuchEJBException: No such EJB: app2/hello/LogAccessBean > at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:354) > at org.jboss.ejb.client.TransactionInterceptor.handleInvocationResult(TransactionInterceptor.java:75) > at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:357) > at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:608) > at org.jboss.ejb.client.EJBInvocationHandler.lambda$invoke$0(EJBInvocationHandler.java:164) > at org.jboss.ejb.client.EJBClientContext.discoverAffinityNone(EJBClientContext.java:428) > at org.jboss.ejb.client.EJBClientContext.performLocatedAction(EJBClientContext.java:387) > at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:150) > at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:100) > at com.sun.proxy.$Proxy65.getLog(Unknown Source) > at org.jboss.as.test.integration.deployment.dependencies.ear.InterDeploymentDependenciesEarTestCase.test(InterDeploymentDependenciesEarTestCase.java:127) > {code} > Earliest failure I see with this pattern in the TeamCity history is from Aug 17, 2016. But such failures were confined to JDK9 runs and stopped last Sept 2. Then they start appearing quite frequently on Feb 6, 2017. First appearance was in a test of PR #9600, but there are other failures before that PR was merged so I doubt that PR is relevant. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8220) Web Manager Console doesn't display module options defined in standalone.xml

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8220?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-8220: -------------------------------------- Component/s: Web Console Assignee: Harald Pehl (was: Jason Greene) > Web Manager Console doesn't display module options defined in standalone.xml > ---------------------------------------------------------------------------- > > Key: WFLY-8220 > URL: https://issues.jboss.org/browse/WFLY-8220 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 10.1.0.Final > Reporter: Yusheng Wang > Assignee: Harald Pehl > Attachments: wildfly-bug.png > > > After fresh installation of Wildfly we got pre-defined security domains such as "jaspitest", "jboss-web-policy" or "other" etc. I can see them also in standalone.xml > {code:xml} > <security-domain name="other" cache-type="default"> > <authentication> > <login-module code="Remoting" flag="optional"> > <module-option name="password-stacking" value="useFirstPass"/> > </login-module> > <login-module code="RealmDirect" flag="required"> > <module-option name="password-stacking" value="useFirstPass"/> > </login-module> > </authentication> > </security-domain> > {code} > As you can see, the security domain with name "other" has two login modules defined in authentication, each of them has one module-option defined in it. > But we can not see any definition of module options in web console! (See screenshot in attatchment) > Also in user defined security domains we can not save module options correctly over web console. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-9) [QE] - JMAN4-152 - Install the in-process agent via RPM into an RPM installed EAP 7 installation.

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-9?page=com.atlassian.jira.plug... ] Filip Brychta commented on HAWKULARQE-9: ---------------------------------------- Link to documentation - https://docs.engineering.redhat.com/display/JP/CloudForms+Middleware+-+EA... > [QE] - JMAN4-152 - Install the in-process agent via RPM into an RPM installed EAP 7 installation. > ------------------------------------------------------------------------------------------------- > > Key: HAWKULARQE-9 > URL: https://issues.jboss.org/browse/HAWKULARQE-9 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Filip Brychta > Labels: mm-integration-hawkular-qe > > See [JMAN4-152|https://issues.jboss.org/browse/JMAN4-152] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3797) Need post-timeout for WildFly / Undertow

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3797?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3797: ----------------------------------------------- Brad Maxwell <bmaxwell(a)redhat.com> changed the Status of [bug 1016936|https://bugzilla.redhat.com/show_bug.cgi?id=1016936] from NEW to CLOSED > Need post-timeout for WildFly / Undertow > ---------------------------------------- > > Key: WFLY-3797 > URL: https://issues.jboss.org/browse/WFLY-3797 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 8.1.0.Final > Reporter: Lyle Wang > Assignee: Stuart Douglas > Fix For: 8.2.0.Final, 9.0.0.Beta1 > > > Is that possible to provide post timeout to prevent DoS ? JBoss AS 7 or WildFly has no such feature/option, but weblogic provides this: > http://docs.oracle.com/cd/E17904_01/web.1111/e13701/web_server.htm#i1059782 > Currently only "max-post-size" is supported: > https://docs.jboss.org/author/display/WFLY8/Undertow+%28web%29+subsystem+... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8220) Web Manager Console doesn't display module options defined in standalone.xml

by Yusheng Wang (JIRA)

Yusheng Wang created WFLY-8220: ---------------------------------- Summary: Web Manager Console doesn't display module options defined in standalone.xml Key: WFLY-8220 URL: https://issues.jboss.org/browse/WFLY-8220 Project: WildFly Issue Type: Bug Affects Versions: 10.1.0.Final Reporter: Yusheng Wang Assignee: Jason Greene Attachments: wildfly-bug.png After fresh installation of Wildfly we got pre-defined security domains such as "jaspitest", "jboss-web-policy" or "other" etc. I can see them also in standalone.xml {code:xml} <security-domain name="other" cache-type="default"> <authentication> <login-module code="Remoting" flag="optional"> <module-option name="password-stacking" value="useFirstPass"/> </login-module> <login-module code="RealmDirect" flag="required"> <module-option name="password-stacking" value="useFirstPass"/> </login-module> </authentication> </security-domain> {code} As you can see, the security domain with name "other" has two login modules defined in authentication, each of them has one module-option defined in it. But we can not see any definition of module options in web console! (See screenshot in attatchment) Also in user defined security domains we can not save module options correctly over web console. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8218) Add smoke tests for certificate based authentication backed by Elytron

by Ondrej Kotek (JIRA)

[ https://issues.jboss.org/browse/WFLY-8218?page=com.atlassian.jira.plugin.... ] Ondrej Kotek updated WFLY-8218: ------------------------------- Summary: Add smoke tests for certificate based authentication backed by Elytron (was: Add smoke tests for certificated based authentication backed by Elytron) > Add smoke tests for certificate based authentication backed by Elytron > ---------------------------------------------------------------------- > > Key: WFLY-8218 > URL: https://issues.jboss.org/browse/WFLY-8218 > Project: WildFly > Issue Type: Task > Components: Test Suite > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Kotek > Assignee: Ondrej Kotek > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2159) Delta view cannot be installed

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2159?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2159: -------------------------------- [~dan.berindei] Can you reproduce this? I want to create a unit test before looking into a fix. > Delta view cannot be installed > ------------------------------ > > Key: JGRP-2159 > URL: https://issues.jboss.org/browse/JGRP-2159 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.1, 4.0.1 > > Attachments: discarded_delta_view.log > > > A DeltaView cannot be installed because the ref view-id is not the current view-id. > Looking at the view sequence for members J, K and L: > {noformat} > 19:22:54,278 DEBUG (testng-Test:[]) [GMS] J: installing view [J|0] (1) [J] > 19:22:56,519 DEBUG (testng-Test:[]) [GMS] K: installing view [J|1] (2) [J, K] > 19:22:56,572 DEBUG (jgroups-7,J:[]) [GMS] J: installing view [J|1] (2) [J, K] > 19:22:56,590 DEBUG (jgroups-5,K:[]) [GMS] K: installing view [J|2] (2) [J, K] > 19:22:58,585 DEBUG (jgroups-5,J:[]) [GMS] J: installing view [J|3] (3) [J, K, L] > 19:23:00,603 DEBUG (testng-Test:[]) [GMS] L: installing view [J|3] (3) [J, K, L] > {noformat} > K cannot install DeltaView J|3 because it has view J|2 but the DeltaView has ref view-id J|1. > The reason is that J|2 was apparently installed *only* at K (but not at coordinator J1!), despite it being the same view as J|1. > We need to look into why J|2 was installed at K only. Second line of defense: when a DeltaView cannot be installed, send a message to the view sender (coord) and solicit the full view instead. > See the attached log. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8219) Add smoke tests for certificated based authentication backed by Elytron

by Ondrej Kotek (JIRA)

Ondrej Kotek created WFLY-8219: ---------------------------------- Summary: Add smoke tests for certificated based authentication backed by Elytron Key: WFLY-8219 URL: https://issues.jboss.org/browse/WFLY-8219 Project: WildFly Issue Type: Task Components: Test Suite Affects Versions: 11.0.0.Alpha1 Reporter: Ondrej Kotek Assignee: Ondrej Kotek -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 February 2017