[jira] [Commented] (AMQ-7087) Add Java 11 Support (runtime)
[ https://issues.apache.org/jira/browse/AMQ-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142667#comment-17142667 ] ASF subversion and git services commented on AMQ-7087: -- Commit 0f92f2cabb379559b504c034ab096a89c3b61b77 in activemq's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=0f92f2c ] Merge pull request #546 from jbonofre/AMQ-7087 [AMQ-7087] Add JDK 9+ specific JVM args to avoid warnings > Add Java 11 Support (runtime) > - > > 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: Jean-Baptiste Onofré >Priority: Critical > Fix For: 5.16.0 > > Time Spent: 20m > Remaining Estimate: 0h > > 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)
[jira] [Commented] (AMQ-7087) Add Java 11 Support (runtime)
[ https://issues.apache.org/jira/browse/AMQ-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142665#comment-17142665 ] ASF subversion and git services commented on AMQ-7087: -- Commit 7db424758f9a3b04bde3dfe6319345049651e617 in activemq's branch refs/heads/master from jbonofre [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=7db4247 ] [AMQ-7087] Add JDK 9+ specific JVM args to avoid warnings > Add Java 11 Support (runtime) > - > > 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: Jean-Baptiste Onofré >Priority: Critical > Fix For: 5.16.0 > > Time Spent: 20m > Remaining Estimate: 0h > > 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)
[jira] [Commented] (AMQ-7087) Add Java 11 Support (runtime)
[ https://issues.apache.org/jira/browse/AMQ-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142666#comment-17142666 ] ASF subversion and git services commented on AMQ-7087: -- Commit 0f92f2cabb379559b504c034ab096a89c3b61b77 in activemq's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=0f92f2c ] Merge pull request #546 from jbonofre/AMQ-7087 [AMQ-7087] Add JDK 9+ specific JVM args to avoid warnings > Add Java 11 Support (runtime) > - > > 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: Jean-Baptiste Onofré >Priority: Critical > Fix For: 5.16.0 > > Time Spent: 20m > Remaining Estimate: 0h > > 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)
[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=17060112#comment-17060112 ] Christopher L. Shannon commented on AMQ-7087: - [~jbonofre] - I found an old branch from like a year ago where I worked on JDK 11 build support that seems to somewhat work, I'm going to create a new Jira for it and have you take a look for 5.16.0 to see what you think. > 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: Jean-Baptiste Onofré >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)
[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=17060101#comment-17060101 ] Christopher L. Shannon commented on AMQ-7087: - [~jbonofre] - I took a quick look and seems like there's a decent number of changes to get it to build with JDK 11 so maybe we just do that in a point release like 5.16.1 or something. I think it's fine as we are only updating the build to be JDK 11 compatible and wouldn't be changing the targeted runtime. > 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: Jean-Baptiste Onofré >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)
[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=17060098#comment-17060098 ] Christopher L. Shannon commented on AMQ-7087: - [~jbonofre] - I think it might also be a good idea to be able to build 5.16.0 using JDK 11 if there aren't too many changes to make it happen. The runtime should still target JDK 8 for Java 8 compatibility but I just checked and can't actually build using JDK 11 yet which I think is an issue because 5.16.0 will probably be around for a long time under maintenance. > 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: Jean-Baptiste Onofré >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)
[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=17060022#comment-17060022 ] Wojciech Sliwinski commented on AMQ-7087: - Hi [~jbonofre], Thanks for the update. Please comment here once 5.15.12 and/or 5.16.0 version(s) are released. > 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: Jean-Baptiste Onofré >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)
[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=17059945#comment-17059945 ] Jean-Baptiste Onofré commented on AMQ-7087: --- [~wsliwins] if you talk at runtime, it's already supported. 5.15.12 and 5.16.0 can run with Java 11 without problem (both standalone and in Karaf). I sent a message on the mailing list couple of weeks ago. I'm doing a full runtime pass again before submitting 5.16.0 to vote. > 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: Jean-Baptiste Onofré >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)
[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=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)
[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=16743049#comment-16743049 ] Christopher L. Shannon commented on AMQ-7087: - [~jbonofre] - did you get a chance to check on osgi with my github patch? [~jgoodyear] - I think you have some experience with OSGi/Karaf as well so maybe this is something you could take a look at if you have some time...my OSGi experience is pretty limited If we can at least get basic compatibility with JDK 11 then we can go forward with 5.16 > 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 (v7.6.3#76005)
[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=16703727#comment-16703727 ] Jean-Baptiste Onofré commented on AMQ-7087: --- Regarding OSGi/Karaf, I gonna take a look. > 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 (v7.6.3#76005)
[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=16703624#comment-16703624 ] Daniel Kulp commented on AMQ-7087: -- Those jars are fine as they are dual licensed with one of the options being CDDL1.1 which is Category B. That said, longer term, we'll likely need to flip them from the javax.* coordinates to the new jakarta.* coordinates. Now that all of those have moved to Eclipse, that's where the new versions will be placed. annotation-api is there already, but jaxb isn't there yet. See https://wiki.eclipse.org/New_Maven_Coordinates > 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 (v7.6.3#76005)
[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=16703601#comment-16703601 ] Christopher L. Shannon commented on AMQ-7087: - I have a commit that currently works on JDK 11 (with some caveats). You can use JDK 11 to build and also run the broker. It also keeps compatibility with JDK 8 so if you build with JDK 11 it will still run on JDK 8, etc. I pushed my working commit here: https://github.com/cshannon/activemq/commit/68c91621a0568a0d47e66a800833e1770c27b7d8 There are some issues however: 1) OSGI/Karaf is broken. When running tests it is missing a bunch of dependencies. This may have something to do with the fact that I had to upgrade the maven-bundle-plugin to work with JDK 11. We are now using version 3.5.1. As part of the plugin update I had to comment out the Private-Package line of the config inside the activemq-parent pom otherwise it wouldn't include any classes in the jar. So there's clearly some work to be done here to get it working properly with Karaf and OSGi. [~jbonofre] - maybe you can take a look at this if you get a chance? 2) I'm not sure about the licensing issues in terms of the new jars I had to add. We have to include new jars now such as javax.annotation-api and jaxb-api etc. I added the standard javax versions but I'm not sure if we can use them because of licensing and maybe we need to find geronimo versions or other jars that are compatible. [~dkulp] - Do you know if the licensing is an issue with these jars? 3) There are still more dependencies we should probably update and we need to run through the full test suite. I imagine some stuff might break when we run all the unit tests. > 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 (v7.6.3#76005)
[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=16703404#comment-16703404 ] Jezza commented on AMQ-7087: To make matters even more annoying, the broker and the client use the same packages, so I can't even get it to my project to compile. Not complaining, just saying that the packages will also need to be taken into account. > 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 (v7.6.3#76005)
[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=16686632#comment-16686632 ] Christopher L. Shannon commented on AMQ-7087: - Ok thanks I will try it > 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 (v7.6.3#76005)
[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=16686612#comment-16686612 ] Daniel Kulp commented on AMQ-7087: -- The xic-utils use it's own version numbers and release schedule. No different than ActiveMQ vs Artemis. 3.2.3 should work. > 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 (v7.6.3#76005)
[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=16686596#comment-16686596 ] Christopher L. Shannon commented on AMQ-7087: - Right but I don't see 3.3 yet: https://mvnrepository.com/artifact/org.apache.cxf/cxf-xjc-plugin > 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 (v7.6.3#76005)
[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=16686589#comment-16686589 ] Daniel Kulp commented on AMQ-7087: -- I believe AMQ only used the cxf-xjc-plugin. That was released a couple weeks ago. > 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 (v7.6.3#76005)
[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=16686461#comment-16686461 ] Christopher L. Shannon commented on AMQ-7087: - We need CXF version 3.3 to be released for our xsd generation: https://issues.apache.org/jira/browse/CXF-7852 I ran into code generation issues on JDK 11 but will be fixed in 3.3 > 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 (v7.6.3#76005)
[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=16665312#comment-16665312 ] Jeff Gullett commented on AMQ-7087: --- That wouldn't surprise me, as AMQ Broker has a ton of dependencies. We just updated our code base, and it was kind of a pain due to lack of support from 3rd party vendors. JAXB was one of the biggest headaches, as there isn't yet an official release that is fully functional without modification. > 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 (v7.6.3#76005)
[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=16665257#comment-16665257 ] Christopher L. Shannon commented on AMQ-7087: - Looking at this we might have some blockers as several things will need to be updated and to support jdk 11...such as the cxf-xjc-plugin and we need to fix scala, etc. Also I'm not sure how OSGi is going to go. Others are welcome to help out with this effort as well as it will be a lot of changes. > 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 (v7.6.3#76005)
[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=16665076#comment-16665076 ] Christopher L. Shannon commented on AMQ-7087: - I will work on this but it will probably take a little while as there is going to be a lot of work to upgrade to Java 11. > 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 (v7.6.3#76005)
[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=16665022#comment-16665022 ] Christopher L. Shannon commented on AMQ-7087: - Java 11 support along with updated dependencies that are necessary like Spring are probably a good candidate to drive the release of 5.16.0 later this year. > 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 >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 (v7.6.3#76005)
