July 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9130) RemoteStatefulEJBConcurrentFailoverTestCase fails intermittently

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9130?page=com.atlassian.jira.plugin.... ] Paul Ferraro moved JBEAP-12344 to WFLY-9130: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9130 (was: JBEAP-12344) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering (was: Clustering) Affects Version/s: 11.0.0.Alpha1 (was: 7.1.0.ER2) > RemoteStatefulEJBConcurrentFailoverTestCase fails intermittently > ---------------------------------------------------------------- > > Key: WFLY-9130 > URL: https://issues.jboss.org/browse/WFLY-9130 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > This is looks like an issue with EJB client failing to retry the EJB lookup on EJBComponentUnavailableException. > e.g. > https://ci.wildfly.org/viewLog.html?buildId=67940&tab=buildResultsDiv&bui... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1862) [QE] 7.1.0 Server hanging on HP-UX when reload is initiated quickly after server was sending large amount of data

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1862?page=com.atlassian.jira.plugi... ] Brian Stansberry resolved WFCORE-1862. -------------------------------------- Fix Version/s: 3.0.0.Alpha12 Resolution: Done > [QE] 7.1.0 Server hanging on HP-UX when reload is initiated quickly after server was sending large amount of data > ----------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1862 > URL: https://issues.jboss.org/browse/WFCORE-1862 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 2.2.0.Final > Environment: Noticed only on HP-UX ia64 with java version "1.8.0.04-hp-ux" > Reporter: Radim Hatlapatka > Assignee: David Lloyd > Priority: Blocker > Fix For: 3.0.0.Alpha12 > > Attachments: connector-metrics.war, duringReload.jstack, eap.jstack > > > Originally reported for EAP 7.0.3.CP.CR2, still this issue is valid also for WildFly 10.1.0.Final > Upgrade to XNIO 3.4.0.Final causes regression resulting in server hanging during reload on HP-UX in situation when servlet was sending more than 4 GB of data and suddenly reload operation is called. The reload operation doesn't finish. > The deployment sending the data is according to log stopped, still there is visible running thread in awaitWritable \[1\]. > Note: If I use older version of XNIO => replacing XNIO 3.4.0.Final with XNIO 3.3.6.Final, it works just fine. > Attaching eap.jstack (thread dump when arquillian tries to stop the server after reload operation timed out) and duringReload.jstack (thread dump when reload is called and it is waited for server to be reloaded) > \[1\] > {noformat} > "default task-1" #786 prio=5 os_prio=-179 tid=0x00c18000 nid=796 lwp_id=8999064 runnable [0x27cc0000] > java.lang.Thread.State: RUNNABLE > at sun.nio.ch.DevPollArrayWrapper.poll0(Native Method) > at sun.nio.ch.DevPollArrayWrapper.poll(DevPollArrayWrapper.java:223) > at sun.nio.ch.DevPollSelectorImpl.doSelect(DevPollSelectorImpl.java:84) > at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86) > - locked <0x6c393e50> (a sun.nio.ch.Util$2) > - locked <0x6c393e40> (a java.util.Collections$UnmodifiableSet) > - locked <0x6c393d40> (a sun.nio.ch.DevPollSelectorImpl) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:101) > at org.xnio.nio.SelectorUtils.await(SelectorUtils.java:46) > at org.xnio.nio.NioSocketConduit.awaitWritable(NioSocketConduit.java:233) > at org.xnio.conduits.AbstractSinkConduit.awaitWritable(AbstractSinkConduit.java:66) > at org.xnio.conduits.AbstractSinkConduit.awaitWritable(AbstractSinkConduit.java:66) > at io.undertow.conduits.ChunkedStreamSinkConduit.awaitWritable(ChunkedStreamSinkConduit.java:361) > at org.xnio.conduits.ConduitStreamSinkChannel.awaitWritable(ConduitStreamSinkChannel.java:134) > at io.undertow.channels.DetachableStreamSinkChannel.awaitWritable(DetachableStreamSinkChannel.java:87) > at io.undertow.server.HttpServerExchange$WriteDispatchChannel.awaitWritable(HttpServerExchange.java:1951) > at org.xnio.channels.Channels.writeBlocking(Channels.java:154) > at io.undertow.servlet.spec.ServletOutputStreamImpl.write(ServletOutputStreamImpl.java:184) > at io.undertow.servlet.spec.ServletOutputStreamImpl.write(ServletOutputStreamImpl.java:128) > at org.jboss.qa.management.web.resources.DataSenderServlet.doGet(DataSenderServlet.java:33) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.MetricsHandler.handleRequest(MetricsHandler.java:62) > at io.undertow.servlet.core.MetricsChainHandler.handleRequest(MetricsChainHandler.java:59) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:285) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:264) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:175) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:207) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:802) > 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.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1677) `not` keyword not supported with rule-unit oopath constraints.

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1677?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-1677: -------------------------------- Issue Type: Feature Request (was: Bug) Sprint: 2017 Week 30-31 Implemented by https://github.com/kiegroup/drools/commit/3b8e875166b296c1fb33c3b1aae59a7... > `not` keyword not supported with rule-unit oopath constraints. > -------------------------------------------------------------- > > Key: DROOLS-1677 > URL: https://issues.jboss.org/browse/DROOLS-1677 > Project: Drools > Issue Type: Feature Request > Components: core engine > Reporter: Bob McWhirter > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1859) Investigate and fix JDK9 modular params propagation to forked processes

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1859?page=com.atlassian.jira.plugi... ] Brian Stansberry resolved WFCORE-1859. -------------------------------------- Fix Version/s: 3.0.0.Beta28 Resolution: Done AIUI, our testsuite passes on JDK9 now, including the domain tests. > Investigate and fix JDK9 modular params propagation to forked processes > ----------------------------------------------------------------------- > > Key: WFCORE-1859 > URL: https://issues.jboss.org/browse/WFCORE-1859 > Project: WildFly Core > Issue Type: Sub-task > Components: Server, Test Suite > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Blocker > Fix For: 3.0.0.Beta28 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1677) `not` keyword not supported with rule-unit oopath constraints.

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1677?page=com.atlassian.jira.plugi... ] Mario Fusco reassigned DROOLS-1677: ----------------------------------- Assignee: Mario Fusco (was: Edson Tirelli) > `not` keyword not supported with rule-unit oopath constraints. > -------------------------------------------------------------- > > Key: DROOLS-1677 > URL: https://issues.jboss.org/browse/DROOLS-1677 > Project: Drools > Issue Type: Bug > Reporter: Bob McWhirter > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1677) `not` keyword not supported with rule-unit oopath constraints.

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1677?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-1677: -------------------------------- Component/s: core engine > `not` keyword not supported with rule-unit oopath constraints. > -------------------------------------------------------------- > > Key: DROOLS-1677 > URL: https://issues.jboss.org/browse/DROOLS-1677 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Bob McWhirter > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3045) Elytron - unable to use OTP SASL mechanism

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3045?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3045: ------------------------------------- Priority: Major (was: Blocker) Dropping priority in accordance with the downstream JIRA. > Elytron - unable to use OTP SASL mechanism > ------------------------------------------ > > Key: WFCORE-3045 > URL: https://issues.jboss.org/browse/WFCORE-3045 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Josef Cacek > Assignee: Darran Lofthouse > Labels: eap7.1-rfe-failure > > I'm not able to use the new OTP SASL mechanism in WildFly (introduced as part of EAP7-530). > It seems the only security-realm which has subsystem support for OTP is the {{ldap-realm}} now. Nevertheless the name filtering in {{AbstractMechanismAuthenticationFactory.getMechanismNames()}} doesn't return OTP as supported in ldap-realm. Neither the {{PasswordGuessEvidence}} nor {{PasswordCredential}} checked in the method seems to be supported. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3045) Elytron - unable to use OTP SASL mechanism

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3045?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3045: ------------------------------------- Fix Version/s: (was: 3.0.0.Beta29) > Elytron - unable to use OTP SASL mechanism > ------------------------------------------ > > Key: WFCORE-3045 > URL: https://issues.jboss.org/browse/WFCORE-3045 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Josef Cacek > Assignee: Darran Lofthouse > Priority: Blocker > Labels: eap7.1-rfe-failure > > I'm not able to use the new OTP SASL mechanism in WildFly (introduced as part of EAP7-530). > It seems the only security-realm which has subsystem support for OTP is the {{ldap-realm}} now. Nevertheless the name filtering in {{AbstractMechanismAuthenticationFactory.getMechanismNames()}} doesn't return OTP as supported in ldap-realm. Neither the {{PasswordGuessEvidence}} nor {{PasswordCredential}} checked in the method seems to be supported. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3045) Elytron - unable to use OTP SASL mechanism

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3045?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3045: ------------------------------------- Fix Version/s: 3.0.0.Beta29 > Elytron - unable to use OTP SASL mechanism > ------------------------------------------ > > Key: WFCORE-3045 > URL: https://issues.jboss.org/browse/WFCORE-3045 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Josef Cacek > Assignee: Darran Lofthouse > Priority: Blocker > Labels: eap7.1-rfe-failure > Fix For: 3.0.0.Beta29 > > > I'm not able to use the new OTP SASL mechanism in WildFly (introduced as part of EAP7-530). > It seems the only security-realm which has subsystem support for OTP is the {{ldap-realm}} now. Nevertheless the name filtering in {{AbstractMechanismAuthenticationFactory.getMechanismNames()}} doesn't return OTP as supported in ldap-realm. Neither the {{PasswordGuessEvidence}} nor {{PasswordCredential}} checked in the method seems to be supported. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3080) elytron-tool.ps1 script not working properly after [WFCORE-2966]

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3080?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3080: ------------------------------------- Fix Version/s: 3.0.0.Beta29 > elytron-tool.ps1 script not working properly after [WFCORE-2966] > ---------------------------------------------------------------- > > Key: WFCORE-3080 > URL: https://issues.jboss.org/browse/WFCORE-3080 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta28 > Reporter: Peter Skopek > Assignee: Peter Skopek > Priority: Blocker > Fix For: 3.0.0.Beta29 > > > Elytron tool scripts use script name as the first parameter. > PS1 script is not working as the last change broke list of parameters. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 2017