Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WFCORE-5790] Upgrade jboss-parent from 37 to 39 #4998

Merged
merged 1 commit into from Mar 8, 2022

Conversation

jamezp
Copy link
Member

@jamezp jamezp commented Mar 8, 2022

Signed-off-by: James R. Perkins <jperkins@redhat.com>
@jamezp jamezp added the 18.x PRs meant for 18.x (corresponding to WildFly 26.x) label Mar 8, 2022
@wildfly-ci
Copy link

Core - Full Integration Build 11081 outcome was FAILURE using a merge of 8dde8db
Summary: Tests failed: 1 (1 new), passed: 7199, ignored: 142 Build time: 05:35:04

Failed tests

org.jboss.as.test.manualmode.messaging.ha.ReplicatedFailoverTestCase.testBackupFailoverAfterFailback: javax.jms.JMSRuntimeException: AMQ219014: Timed out after waiting 30,000 ms for response when sending packet -18
	at org.apache.activemq.artemis.jms.client.JmsExceptionUtils.convertToRuntimeException(JmsExceptionUtils.java:88)
	at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createContext(ActiveMQConnectionFactory.java:326)
	at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createContext(ActiveMQConnectionFactory.java:314)
	at org.jboss.as.test.manualmode.messaging.ha.AbstractMessagingHATestCase.receiveNoMessage(AbstractMessagingHATestCase.java:213)
	at org.jboss.as.test.manualmode.messaging.ha.FailoverTestCase.testBackupFailoverAfterFailback(FailoverTestCase.java:218)
Caused by: javax.jms.JMSException: AMQ219014: Timed out after waiting 30,000 ms for response when sending packet -18
	at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:539)
	at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:443)
	at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.createSessionContext(ActiveMQClientProtocolManager.java:306)
	at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.createSessionContext(ActiveMQClientProtocolManager.java:254)
	at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSessionChannel(ClientSessionFactoryImpl.java:1435)
	at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:741)
	at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:322)
	at org.apache.activemq.artemis.jms.client.ActiveMQConnection.authorize(ActiveMQConnection.java:674)
	at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:920)
	at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createContext(ActiveMQConnectionFactory.java:321)
	... 135 more
Caused by: ActiveMQConnectionTimedOutException[errorType=CONNECTION_TIMEDOUT message=AMQ219014: Timed out after waiting 30,000 ms for response when sending packet -18]
	... 145 more
------- Stdout: -------
 [0m13:44:36,915 INFO  [org.jboss.modules] (main) JBoss Modules version 2.0.0.Final
 [0m [0m13:44:37,518 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.13.Final
 [0m [0m13:44:37,536 INFO  [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final
 [0m [0m13:44:37,760 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 26.1.0.Beta1-SNAPSHOT (WildFly Core 18.0.5.Final-SNAPSHOT) starting
 [0m [0m13:44:39,466 INFO  [org.wildfly.security] (ServerService Thread Pool -- 10) ELY00001: WildFly Elytron version 1.18.3.Final
 [0m [0m13:44:41,775 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
 [0m [0m13:44:41,813 INFO  [org.xnio] (MSC service thread 1-7) XNIO version 3.8.6.Final
 [0m [0m13:44:41,860 INFO  [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.8.6.Final
 [0m [0m13:44:42,145 INFO  [org.wildfly.extension.microprofile.config.smallrye] (ServerService Thread Pool -- 74) WFLYCONF0001: Activating MicroProfile Config Subsystem
 [0m [0m13:44:42,152 INFO  [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 5.0.23.Final
 [0m [0m13:44:42,165 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 61) WFLYCLINF0001: Activating Infinispan subsystem.
 [0m [0m13:44:42,167 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 63) WFLYRS0016: RESTEasy version 4.7.4.Final
 [0m [0m13:44:42,169 INFO  [org.wildfly.extension.microprofile.jwt.smallrye] (ServerService Thread Pool -- 75) WFLYJWT0001: Activating MicroProfile JWT Subsystem
 [0m [0m13:44:42,191 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 66) WFLYCLJG0001: Activating JGroups subsystem. JGroups version 4.2.20
 [0m [33m13:44:42,215 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 86) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
 [0m [0m13:44:42,242 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 78) WFLYNAM0001: Activating Naming Subsystem
 [0m [0m13:44:42,259 INFO  [org.wildfly.extension.elytron.oidc._private] (ServerService Thread Pool -- 58) WFLYOIDC0001: Activating WildFly Elytron OIDC Subsystem
 [0m [0m13:44:42,276 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 69) WFLYJSF0007: Activated the following Jakarta Server Faces Implementations: [main]
 [0m [0m13:44:42,290 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 88) WFLYWS0002: Activating WebServices Extension
 [0m [0m13:44:42,290 INFO  [org.wildfly.extension.health] (ServerService Thread Pool -- 59) WFLYHEALTH0001: Activating Base Health Subsystem
 [0m [0m13:44:42,326 INFO  [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 60) WFLYIIOP0001: Activating IIOP Subsystem
 [0m [0m13:44:42,455 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 50) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
 [0m [0m13:44:42,491 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 62) WFLYIO001: Worker 'default' has auto-configured to 8 IO threads with 64 max task threads based on your 4 available processors
 [0m [0m13:44:42,509 INFO  [org.wildfly.extension.metrics] (ServerService Thread Pool -- 73) WFLYMETRICS0001: Activating Base Metrics Subsystem
 [0m [0m13:44:42,525 INFO  [org.jboss.as.connector] (MSC service thread 1-8) WFLYJCA0009: Starting Jakarta Connectors Subsystem (WildFly/IronJacamar 1.5.3.Final)
 [0m [0m13:44:42,544 INFO  [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 76) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
 [0m [0m13:44:42,731 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2
 [0m [0m13:44:42,730 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0003: Undertow 2.2.16.Final starting
 [0m [0m13:44:42,944 INFO  [org.jboss.as.naming] (MSC service thread 1-8) WFLYNAM0003: Starting Naming Service
 [0m [0m13:44:42,961 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]


@bstansberry bstansberry merged commit a09cbbd into wildfly:18.x Mar 8, 2022
@bstansberry
Copy link
Contributor

Thanks, @jamezp

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
18.x PRs meant for 18.x (corresponding to WildFly 26.x)
Projects
None yet
3 participants