You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Wojciech Sliwinski (Jira)" <ji...@apache.org> on 2020/03/15 15:37:00 UTC

[jira] [Commented] (AMQ-7087) Add Java 11 Support

    [ https://issues.apache.org/jira/browse/AMQ-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17059714#comment-17059714 ] 

Wojciech Sliwinski commented on AMQ-7087:
-----------------------------------------

Dear All,

Would be great to see more progress with Java 11 support.
It is critical for us to move to Java 11 ASAP this year as Java 8 reached its EOL.
For some teams, lack of Java 11 support could be a big no-go for ActiveMQ ...

> Add Java 11 Support
> -------------------
>
>                 Key: AMQ-7087
>                 URL: https://issues.apache.org/jira/browse/AMQ-7087
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.15.6
>         Environment: Windows 10 with the OpenJDK 11 "bin" directory on the path.
>            Reporter: Jeff Gullett
>            Assignee: Christopher L. Shannon
>            Priority: Critical
>             Fix For: 5.16.0
>
>
> Java 8 support is ending in January, 2019 (in 2 months).  Currently, the ActiveMQ Broker only supports Java 8.  When I try to start the broker using Java 11 (the latest long-term-support version), I get the following error:
> Unable to execute Java command.  The system cannot find the file specified. (0x2)
> Critical error: wait for JVM process failed
> Since both Java 9 and Java 10 are already EOL, support for Java 11 needs to be added by January 2019.  The issue to add Java 9 support (AMQ-6864) is OBE, and should be replaced by this issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)