February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13064) EJB client-side interceptor failure when using HTTPRemoting Protocol

by Francesco Marchioni (Jira)

Francesco Marchioni created WFLY-13064: ------------------------------------------ Summary: EJB client-side interceptor failure when using HTTPRemoting Protocol Key: WFLY-13064 URL: https://issues.redhat.com/browse/WFLY-13064 Project: WildFly Issue Type: Bug Components: EJB, Test Suite Affects Versions: 19.0.0.Beta1 Reporter: Francesco Marchioni Assignee: Cheng Fang Attachments: surefire-reports-RemoteProtocolChangeClientInterceptorTestCase.zip The following [test|https://github.com/wildfly/wildfly/blob/master/testsuite/integration...] fails in counting the EJB Client Interceptor count, when the HTTP Remoting Protocol is used: {code:java} @Test @InSequence(2) @OperateOnDeployment("client") public void testHttpRemotingProtocol() throws Exception { final Hashtable<String, String> props = new Hashtable<>(); props.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming"); props.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); props.put(Context.PROVIDER_URL, "http-remoting://" + TestSuiteEnvironment.getServerAddress() + ":" + (TestSuiteEnvironment.getHttpPort() + Integer.parseInt(getSystemProperty("jboss.socket.binding.port-offset", "100")))); StatelessRemote bean = getRemote(new InitialContext(props)); Assert.assertNotNull(bean); // StatelessBean.methodCount field should equal 2 after second invoking (methodCount is a static field and is shared within a single JVM) Assert.assertEquals(ProtocolSampleClientInterceptor.COUNT + 2, bean.method()); } {code} Stack Trace: {code:java} 14:46:01 [ERROR] testHttpRemotingProtocol(org.jboss.as.test.multinode.clientinterceptor.protocol.RemoteProtocolChangeClientInterceptorTestCase) Time elapsed: 0.77 s <<< FAILURE! 14:46:01 java.lang.AssertionError: expected:<12> but was:<11> 14:46:01 at org.junit.Assert.fail(Assert.java:88) 14:46:01 at org.junit.Assert.failNotEquals(Assert.java:834) 14:46:01 at org.junit.Assert.assertEquals(Assert.java:645) 14:46:01 at org.junit.Assert.assertEquals(Assert.java:631) 14:46:01 at org.jboss.as.test.multinode.clientinterceptor.protocol.RemoteProtocolChangeClientInterceptorTestCase.testHttpRemotingProtocol(RemoteProtocolChangeClientInterceptorTestCase.java:130) {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2106) Prepare for JDK 11

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2106?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2106: --------------------------- Description: Investigate the changes needed to run with JDK 11. Probably module.info classes are all that's needed. Other things to investigate: * Replace {{Condition}} with {{Predicate}} was:Investigate the changes needed to run with JDK 11. Probably module.info classes are all that's needed. > Prepare for JDK 11 > ------------------ > > Key: JGRP-2106 > URL: https://issues.redhat.com/browse/JGRP-2106 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0 > > > Investigate the changes needed to run with JDK 11. Probably module.info classes are all that's needed. > Other things to investigate: > * Replace {{Condition}} with {{Predicate}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13063) Change default values of id-cache-size or confirmation-window-size for cluster connections

by Simon Priadka (Jira)

[ https://issues.redhat.com/browse/WFLY-13063?page=com.atlassian.jira.plugi... ] Simon Priadka moved JBEAP-18643 to WFLY-13063: ---------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-13063 (was: JBEAP-18643) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering (was: ActiveMQ) Affects Version/s: 19.0.0.Beta2 (was: 7.3.0.GA) > Change default values of id-cache-size or confirmation-window-size for cluster connections > ------------------------------------------------------------------------------------------ > > Key: WFLY-13063 > URL: https://issues.redhat.com/browse/WFLY-13063 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 19.0.0.Beta2 > Reporter: Simon Priadka > Assignee: Justin Bertram > Priority: Major > > When establishing a new messaging cluster, default values of *id-cache-size* and *confirmation-window-size* are producing a *WARN* with following message: > {code} > 2020-02-04 21:35:20,228 WARN [org.apache.activemq.artemis.core.server] (Thread-2 (ActiveMQ-client-global-threads)) AMQ224078: The size of duplicate cache detection (<id_cache-size/>) appears to be too large 20,000. It should be no greater than the number of messages that can be squeezed into confirmation window buffer (<confirmation-window-size/>) 1,048,576. > {code} > According to the [method|https://github.com/apache/activemq-artemis/blob/3743bc9d9f39b0731f...] validating these values, this variable combination is "invalid" -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2446) MessageBatch: iterate with filter

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2446?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2446. ---------------------------- Resolution: Done > MessageBatch: iterate with filter > --------------------------------- > > Key: JGRP-2446 > URL: https://issues.redhat.com/browse/JGRP-2446 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0 > > > Create a {{MessageBatch.BatchIterator}} with a predicate that defines which messages are selected by the iterator. Non-selected messages are skipped. > See the code in Pedro's branch [1]. > [1] https://github.com/pruivo/JGroups/tree/t_msg_batch_iterator -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4482) Out of the box SSL with Wildfly Elytron

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-4482?page=com.atlassian.jira.plug... ] Darran Lofthouse updated WFCORE-4482: ------------------------------------- Fix Version/s: (was: 11.0.0.Beta9) > Out of the box SSL with Wildfly Elytron > --------------------------------------- > > Key: WFCORE-4482 > URL: https://issues.redhat.com/browse/WFCORE-4482 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Labels: EAP-CD19 > > The details of this RFE will be explored within the analysis, presently Undertow depends on a security-realm that generates a self signed cert on start up so we will require an Elytron equivalent. > There may be opportunities to tie this in in some way with the new CA integration support but that can be explored in the analysis. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-944) truststore path is ignored if provider is not JKS

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-944?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-944: ------------------------------------ Fix Version/s: (was: 11.0.0.Beta9) > truststore path is ignored if provider is not JKS > ------------------------------------------------- > > Key: WFCORE-944 > URL: https://issues.redhat.com/browse/WFCORE-944 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Arto Huusko > Priority: Major > > truststore configuration ignores the path and relative-to parameters if the truststore provider is anything else than JKS. > This works as documented, but it is not correct. There can be and are truststore implementations that need to load parameters or whatever data from a file, and the current implementation prevents these truststore providers from working. > We have a custom truststore that is loaded from database, and database access parameters are read from a properties file. When trying to use this with Wildfly 9, the keystore engineLoad parameter is passed in as null, even though path and relative-to are configured. > Even standard java supports PKCS12 truststores, where the same problem would occur. > So I would suggest that > - if provider is JKS, path is mandatory > - if provider is not JKS, but path is specified, it is passed to the provider -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11939) FineDatabasePersistenceWebFailoverTestCase fails intermittently

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/WFLY-11939?page=com.atlassian.jira.plugi... ] Thomas Jenkinson commented on WFLY-11939: ----------------------------------------- I am not sure if this is the same issue, but we observed a failure on Narayana CI from a test in the same suite after the fixVersion that this was marked for. Our CI script rebases the fork we use for testing and so I think the commits we would have been running from WildFly would be as of https://github.com/wildfly/wildfly/tree/65d364f1435258428d945094e77b6eb4b... The failure was: {code}FineDatabasePersistenceWebFailoverTestCase>AbstractWebFailoverTestCase.test:87->AbstractWebFailoverTestCase.testGracefulUndeployFailover:96->AbstractWebFailoverTestCase.testFailover:104->AbstractWebFailoverTestCase.establishTopology:389 expected:<200> but was:<500>{code} The console output: http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/563/PROFILE=AS_TE... More data: http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/563/PROFILE=AS_TE... and http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/563/PROFILE=AS_TE... [~pferraro] would you like a new issue to be created or could it be the same as and a recurrence of this issue? > FineDatabasePersistenceWebFailoverTestCase fails intermittently > --------------------------------------------------------------- > > Key: WFLY-11939 > URL: https://issues.redhat.com/browse/WFLY-11939 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: No Release > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > Fix For: 17.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13062) Upgrade WildFly Core 11.0.0.Beta9

by Jeff Mesnil (Jira)

Jeff Mesnil created WFLY-13062: ---------------------------------- Summary: Upgrade WildFly Core 11.0.0.Beta9 Key: WFLY-13062 URL: https://issues.redhat.com/browse/WFLY-13062 Project: WildFly Issue Type: Component Upgrade Components: Management Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 19.0.0.Beta2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13062) Upgrade WildFly Core 11.0.0.Beta8

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-13062?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFLY-13062: ------------------------------- Summary: Upgrade WildFly Core 11.0.0.Beta8 (was: Upgrade WildFly Core 11.0.0.Beta9) > Upgrade WildFly Core 11.0.0.Beta8 > --------------------------------- > > Key: WFLY-13062 > URL: https://issues.redhat.com/browse/WFLY-13062 > Project: WildFly > Issue Type: Component Upgrade > Components: Management > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > Fix For: 19.0.0.Beta2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4482) Out of the box SSL with Wildfly Elytron

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-4482?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-4482: -------------------------------- Fix Version/s: 11.0.0.Beta9 (was: 11.0.0.Beta8) > Out of the box SSL with Wildfly Elytron > --------------------------------------- > > Key: WFCORE-4482 > URL: https://issues.redhat.com/browse/WFCORE-4482 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Labels: EAP-CD19 > Fix For: 11.0.0.Beta9 > > > The details of this RFE will be explored within the analysis, presently Undertow depends on a security-realm that generates a self signed cert on start up so we will require an Elytron equivalent. > There may be opportunities to tie this in in some way with the new CA integration support but that can be explored in the analysis. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2020