June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11767) Remove unused dependencies from org.jboss.as.connector

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFLY-11767?page=com.atlassian.jira.plugi... ] Ranabir Chakraborty reopened WFLY-11767: ---------------------------------------- > Remove unused dependencies from org.jboss.as.connector > ------------------------------------------------------ > > Key: WFLY-11767 > URL: https://issues.redhat.com/browse/WFLY-11767 > Project: WildFly > Issue Type: Sub-task > Components: Class Loading > Reporter: Yeray Borges Santana > Assignee: Ranabir Chakraborty > Priority: Major > > The analysis shows these dependencies are not used by this module: > * org.jboss.jts > * org.glassfish.javax.el -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10173) EjbInvocationStatisticsTestCase fails intermittently: wait-time=0

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-10173?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-10173: ------------------------------------ Fix Version/s: 20.0.1.Final > EjbInvocationStatisticsTestCase fails intermittently: wait-time=0 > ----------------------------------------------------------------- > > Key: WFLY-10173 > URL: https://issues.redhat.com/browse/WFLY-10173 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 12.0.0.Final > Reporter: Jan Kalina > Assignee: Cheng Fang > Priority: Major > Fix For: 21.0.0.Beta1, 20.0.1.Final > > > Sometime, when running EjbInvocationStatisticsTestCase on Windows, assertion fails, as wait-time is 0 (verified it is 0 by adding debug message). > For me it fails allTests in most of cases, but when running test standalone, it fails only in 1 of 4 cases. > I suppose it is because of too short sleep in AbstractManagedBean. (in test is called 4 times, each invocation include 50ms sleep, so I consider probable the wait-time is 0 - need to use longer sleeps to fulfill the test) > {code} > [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.078 s <<< FAILURE! - in org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase > [ERROR] testSingletonWaitTime(org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase) Time elapsed: 0.438 s <<< FAILURE! > java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase.validateWaitTimeStatistic(EjbInvocationStatisticsTestCase.java:179) > at org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase.testSingletonWaitTime(EjbInvocationStatisticsTestCase.java:148) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:564) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.jboss.arquillian.junit.Arquillian$8$1.invoke(Arquillian.java:379) > ... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1970) The service descriptors in the wildfly-elytron module do not correctly combine the other modules.

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1970?page=com.atlassian.jira.plugin.... ] Farah Juma resolved ELY-1970. ----------------------------- Resolution: Done > The service descriptors in the wildfly-elytron module do not correctly combine the other modules. > ------------------------------------------------------------------------------------------------- > > Key: ELY-1970 > URL: https://issues.redhat.com/browse/ELY-1970 > Project: WildFly Elytron > Issue Type: Bug > Components: Build > Affects Versions: 1.12.0.CR3 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.13.0.CR1 > > Attachments: ELY-1970.txt > > > At the moment it looks like it is some kind of first / last match wins rather than aggregating the names of the services. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5423) Fix java 11 usage with kie-pmml-new

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-5423: ---------------------------------------- Summary: Fix java 11 usage with kie-pmml-new Key: DROOLS-5423 URL: https://issues.redhat.com/browse/DROOLS-5423 Project: Drools Issue Type: Bug Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Kie-pmml-new is broken when running under Java 11. This is due to the missing jaxb api/implementations. Solution should be to add a java-11 profile inside kie-pmml-compiler-commons/pom.xml {code:java} // <profiles> <profile> <id>java11-pmml</id> <activation> <jdk>[11,)</jdk> </activation> <properties> <jaxb.api.version>2.3.2</jaxb.api.version> </properties> <dependencies> <dependency> <groupId>org.jboss.spec.javax.xml.bind</groupId> <artifactId>jboss-jaxb-api_2.3_spec</artifactId> </dependency> <dependency> <groupId>org.glassfish.jaxb</groupId> <artifactId>jaxb-runtime</artifactId> </dependency> </dependencies> </profile> </profiles> {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13580) Intermittent testsuite failure: org.jboss.as.test.clustering.cluster.xsite.XSiteSimpleTestCase

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-13580: --------------------------------------- Summary: Intermittent testsuite failure: org.jboss.as.test.clustering.cluster.xsite.XSiteSimpleTestCase Key: WFLY-13580 URL: https://issues.redhat.com/browse/WFLY-13580 Project: WildFly Issue Type: Bug Components: Clustering Reporter: Brian Stansberry Assignee: Paul Ferraro Test failed at [https://ci.wildfly.org/viewLog.html?buildId=208417&buildTypeId=WF_Pul... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12887) Clustering: com.ibm.db2.jcc.am.SqlSyntaxErrorException when DB2 is used as invalidation-cache

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFLY-12887?page=com.atlassian.jira.plugi... ] Ranabir Chakraborty commented on WFLY-12887: -------------------------------------------- [~tommaso-borgato] Can you please provide the steps to reproduce this issue? > Clustering: com.ibm.db2.jcc.am.SqlSyntaxErrorException when DB2 is used as invalidation-cache > --------------------------------------------------------------------------------------------- > > Key: WFLY-12887 > URL: https://issues.redhat.com/browse/WFLY-12887 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 19.0.0.Beta1 > Reporter: Tommaso Borgato > Assignee: Paul Ferraro > Priority: Critical > > The error happens in clustering tests where the cache is backed by a DB2 relational database; > The cache is configured as follows: > {noformat} > embed-server --server-config=standalone-ha.xml > /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp) > /subsystem=infinispan/cache-container=web/invalidation-cache=offload:add() > /subsystem=infinispan/cache-container=web/invalidation-cache==offload/component=transaction:write-attribute(name=mode, value=BATCH) > /subsystem=infinispan/cache-container=web/invalidation-cache=offload/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ) > data-source add --name=testDS --jndi-name=java:jboss/datasources/testDS --driver-name=db2-connector.jar --connection-url=jdbc:db2://db2-111.hosts.mwqe.eng.bos.redhat.com:50000/dballo --enabled=true --jta=true --use-java-context=true --transaction-isolation=TRANSACTION_READ_COMMITTED --min-pool-size=1 --max-pool-size=5 --pool-prefill=true --user-name=dballo00 --password=dballo00 --prepared-statements-cache-size=32 --share-prepared-statements=true > /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc:add(data-source=testDS,fetch-state=false,passivation=false,purge=false,shared=true,dialect=DB2){allow-resource-service-restart=true} > /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=prefix,value=s) > /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=id-column.name,value=id) > /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=id-column.type,value=VARCHAR(255)) > /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=data-column.name,value=datum) > /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=data-column.type,value=BLOB) > /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=timestamp-column.name,value=version) > /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=timestamp-column.type,value=BIGINT) > /subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=offload) > /subsystem=transactions:write-attribute(name=node-identifier,value=wildfly1) > /subsystem=datasources/data-source=testDS:write-attribute(name=spy,value=true) > /subsystem=logging/logger=jboss.jdbc.spy:add(level=TRACE) > {noformat} > The error is the following: > {noformat} > 2019-12-16 16:49:31,961 DEBUG [jboss.jdbc.spy] (expiration-thread--p24-t1) java:jboss/datasources/testDS [DataSource] getConnection() > 2019-12-16 16:49:31,961 DEBUG [jboss.jdbc.spy] (expiration-thread--p24-t1) java:jboss/datasources/testDS [Connection] setAutoCommit(false) > 2019-12-16 16:49:31,962 DEBUG [jboss.jdbc.spy] (expiration-thread--p24-t1) java:jboss/datasources/testDS [Connection] prepareStatement(SELECT datum, id FROM "s_cbnc_ear_a_war" WHERE version < ? AND version > 0 FOR UPDATE) > 2019-12-16 16:49:31,971 DEBUG [jboss.jdbc.spy] (expiration-thread--p24-t1) java:jboss/datasources/testDS [PreparedStatement] setLong(1, 1576514971971) > 2019-12-16 16:49:31,971 DEBUG [jboss.jdbc.spy] (expiration-thread--p24-t1) java:jboss/datasources/testDS [PreparedStatement] executeQuery() > 2019-12-16 16:49:31,987 DEBUG [jboss.jdbc.spy] (persistence-thread--p25-t4) java:jboss/datasources/testDS [Connection] close() > 2019-12-16 16:49:31,991 DEBUG [jboss.jdbc.spy] (persistence-thread--p25-t2) java:jboss/datasources/testDS [DataSource] getConnection() > 2019-12-16 16:49:31,992 DEBUG [jboss.jdbc.spy] (persistence-thread--p25-t2) java:jboss/datasources/testDS [Connection] isValid(10) > 2019-12-16 16:49:31,998 ERROR [org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore] (expiration-thread--p24-t1) ISPN008001: Failed clearing cache store: com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=DBALLO00.s_cbnc_ear_a_war, DRIVER=4.25.1301 > at deployment.db2-connector.jar//com.ibm.db2.jcc.am.b6.a(b6.java:810) > at deployment.db2-connector.jar//com.ibm.db2.jcc.am.b6.a(b6.java:66) > at deployment.db2-connector.jar//com.ibm.db2.jcc.am.b6.a(b6.java:140) > at deployment.db2-connector.jar//com.ibm.db2.jcc.am.k3.c(k3.java:2824) > at deployment.db2-connector.jar//com.ibm.db2.jcc.am.k3.d(k3.java:2808) > at deployment.db2-connector.jar//com.ibm.db2.jcc.am.k3.a(k3.java:2234) > at deployment.db2-connector.jar//com.ibm.db2.jcc.am.k4.a(k4.java:8242) > at deployment.db2-connector.jar//com.ibm.db2.jcc.t4.ab.i(ab.java:206) > at deployment.db2-connector.jar//com.ibm.db2.jcc.t4.ab.b(ab.java:96) > at deployment.db2-connector.jar//com.ibm.db2.jcc.t4.p.a(p.java:32) > at deployment.db2-connector.jar//com.ibm.db2.jcc.t4.av.i(av.java:150) > at deployment.db2-connector.jar//com.ibm.db2.jcc.am.k3.al(k3.java:2203) > at deployment.db2-connector.jar//com.ibm.db2.jcc.am.k4.bq(k4.java:3730) > at deployment.db2-connector.jar//com.ibm.db2.jcc.am.k4.a(k4.java:4609) > at deployment.db2-connector.jar//com.ibm.db2.jcc.am.k4.b(k4.java:4182) > at deployment.db2-connector.jar//com.ibm.db2.jcc.am.k4.bd(k4.java:780) > at deployment.db2-connector.jar//com.ibm.db2.jcc.am.k4.executeQuery(k4.java:745) > at org.jboss.ironjacamar.jdbcadapters@1.4.19.Final//org.jboss.jca.adapters.jdbc.CachedPreparedStatement.executeQuery(CachedPreparedStatement.java:113) > at org.jboss.ironjacamar.jdbcadapters@1.4.19.Final//org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:504) > at org.infinispan.persistence.jdbc@9.4.16.Final//org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore.purge(JdbcStringBasedStore.java:456) > at org.infinispan@9.4.16.Final//org.infinispan.persistence.manager.PersistenceManagerImpl.lambda$purgeExpired$6(PersistenceManagerImpl.java:470) > at java.base/java.util.ArrayList.forEach(ArrayList.java:1540) > at org.infinispan@9.4.16.Final//org.infinispan.persistence.manager.PersistenceManagerImpl.purgeExpired(PersistenceManagerImpl.java:473) > at org.infinispan@9.4.16.Final//org.infinispan.expiration.impl.ExpirationManagerImpl.processExpiration(ExpirationManagerImpl.java:111) > at org.infinispan@9.4.16.Final//org.infinispan.expiration.impl.ExpirationManagerImpl$ScheduledTask.run(ExpirationManagerImpl.java:245) > at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) > at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) > at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at org.jboss.as.clustering.common@19.0.0.Beta1-SNAPSHOT//org.jboss.as.clustering.context.ContextReferenceExecutor.execute(ContextReferenceExecutor.java:49) > at org.jboss.as.clustering.common@19.0.0.Beta1-SNAPSHOT//org.jboss.as.clustering.context.ContextualExecutor$1.run(ContextualExecutor.java:70) > at java.base/java.lang.Thread.run(Thread.java:834) > {noformat} > The issue is set as "Blocker" because DB2 is one of the supported databases and we don't have a workaround at present -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1981) SSL Module missing plugin configuration to assemble multi-version jar

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1981?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated ELY-1981: ---------------------------------- Fix Version/s: 1.10.7.CR1 > SSL Module missing plugin configuration to assemble multi-version jar > --------------------------------------------------------------------- > > Key: ELY-1981 > URL: https://issues.redhat.com/browse/ELY-1981 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.12.0.Final > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Labels: downstream_dependency > Fix For: 1.10.7.CR1, 1.12.1.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1952) SSLConfigurator ignores some of the SSLParameters passed in via setSSLParameters method

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1952?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated ELY-1952: ---------------------------------- Fix Version/s: 1.10.7.CR1 > SSLConfigurator ignores some of the SSLParameters passed in via setSSLParameters method > --------------------------------------------------------------------------------------- > > Key: ELY-1952 > URL: https://issues.redhat.com/browse/ELY-1952 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Diana Vilkolakova > Assignee: Diana Vilkolakova > Priority: Major > Fix For: 1.10.7.CR1, 1.12.0.CR2 > > > Method redefine in SSLConfiguratorImpl ignores some of the SSLParameters passed in, eg. cipher suites, protocols, needClientAuth, and others. Because of this, the assert in the code snippet below fails: > ``` > SSLParameters sslParameters = clientSslSocket.getSSLParameters(); > sslParameters.setNeedClientAuth(true); > clientSslSocket.setSSLParameters(sslParameters); > Assert.assertTrue(clientSslSocket.getSSLParameters().getNeedClientAuth()); > ``` > This issue is to address that. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1979) Elytron needs to deal with JEPS 244 in the org.wildfly.security.ssl package

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1979?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated ELY-1979: ---------------------------------- Fix Version/s: 1.10.7.CR1 > Elytron needs to deal with JEPS 244 in the org.wildfly.security.ssl package > --------------------------------------------------------------------------- > > Key: ELY-1979 > URL: https://issues.redhat.com/browse/ELY-1979 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.12.0.Final > Reporter: Brian Stansberry > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.10.7.CR1, 1.12.1.Final > > > JEPS 244, available in JDK 9 or later and in JDK 8 since the 251 release[1] has added new methods to some of the javax.net.ssl classes that elytron wraps in org.wildfly.security.ssl. But the elytron classes do not handle those new methods. I believe the relevant change is at [2] and updates the SSLEngine, SSLParameters and SSLSocket classes (plus various non-javax classes.) > If Elytron were to require 251 or later to build perhaps this could be a simple matter of adding new methods to the wrappers and calling the delegate, under the expectation that at runtime the wrapper methods would not be invoked in a JVM < 251. Or the wrappers could use reflection and throw a UOE if the methods are not available. > [1] https://www.oracle.com/technetwork/java/javase/8u251-relnotes-5972664.htm... > [2] https://hg.openjdk.java.net/jdk8u/jdk8u41/jdk/rev/b26b096d4c89 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13579) Make most of the calls which wait for timeout configurable with TimeoutUtil

by Ondrej Chaloupka (Jira)

Ondrej Chaloupka created WFLY-13579: --------------------------------------- Summary: Make most of the calls which wait for timeout configurable with TimeoutUtil Key: WFLY-13579 URL: https://issues.redhat.com/browse/WFLY-13579 Project: WildFly Issue Type: Enhancement Components: Test Suite Reporter: Ondrej Chaloupka Assignee: Ondrej Chaloupka There are several places in WFLY testsuite which use calls like {{Thread.sleep(...)}} or wait for some time elapses. Some of these calls do not consider that waiting time should be adapted based on the system property {{ts.timeout.factor}}. This is for what is created a helper class in testsuite {{shared}} module {{TimeoutUtil}} (https://github.com/wildfly/wildfly-core/blob/12.0.1.Final/testsuite/share...). Reason: we have a slower CI machine and we struggle with timeout issues from places which does not consider this configuration -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2020