You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Thorsten Hirsch (Jira)" <ji...@apache.org> on 2023/06/20 22:46:00 UTC
[jira] [Comment Edited] (ARTEMIS-4310) Smaller Container / Dockerfile based on Alpine
[ https://issues.apache.org/jira/browse/ARTEMIS-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735472#comment-17735472 ]
Thorsten Hirsch edited comment on ARTEMIS-4310 at 6/20/23 10:45 PM:
--------------------------------------------------------------------
Unfortunately, the "Fast Tests" don't look so good at all:
{noformat}
[INFO] ActiveMQ Artemis JUnit 4 Rules ..................... FAILURE [ 5.018 s]{noformat}
In the details I see a connection failure:
{noformat}
2023-06-20T17:19:51.6675248Z [Thread-0 (ActiveMQ-client-global-threads)] 17:19:51,666 WARN [org.apache.activemq.artemis.core.client] AMQ212037: Connection failure to invm:0 has been detected: AMQ219015: The connection was disconnected because of server shutdown [code=DISCONNECTED]{noformat}
And even before that there's a problem with libaio, just like Tapan Gupta assumed:
{noformat}
2023-06-20T17:19:51.1686698Z [main] 17:19:51,168 INFO [org.apache.activemq.artemis.core.server] AMQ221045: libaio is not available, switching the configuration into NIO{noformat}
However, all these tests seem to have been run with a JDK 11 installation in /opt instead of "my" JDK 17...
{noformat}
2023-06-20T17:16:12.5139116Z JAVA_HOME_11_X64: /opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/11.0.19-7/x64{noformat}
So... is the failed test anyhow related to the Alpine/JDK17 image or not?
was (Author: thorstenhirsch):
Unfortunately, the "Fast Tests" don't look so good at all:
{noformat}
[INFO] ActiveMQ Artemis JUnit 4 Rules ..................... FAILURE [ 5.018 s]{noformat}
In the details I see a connection failure:
{noformat}
2023-06-20T17:19:51.6675248Z [Thread-0 (ActiveMQ-client-global-threads)] 17:19:51,666 WARN [org.apache.activemq.artemis.core.client] AMQ212037: Connection failure to invm:0 has been detected: AMQ219015: The connection was disconnected because of server shutdown [code=DISCONNECTED]{noformat}
And even before that there's a problem with libaio, just like Tapan Gupta assumed:
{noformat}
2023-06-20T17:19:51.1686698Z [main] 17:19:51,168 INFO [org.apache.activemq.artemis.core.server] AMQ221045: libaio is not available, switching the configuration into NIO{noformat}
However, all these tests seem to have been run with a JDK 11 installation in /opt instead of "my" JDK 17...
{noformat}
2023-06-20T17:16:12.5139116Z JAVA_HOME_11_X64: /opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/11.0.19-7/x64{noformat}
So... is the failed test anyhow related to the Alpine/JDK17 image or not?
> Smaller Container / Dockerfile based on Alpine
> ----------------------------------------------
>
> Key: ARTEMIS-4310
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4310
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 2.28.0
> Reporter: Thorsten Hirsch
> Priority: Major
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)