-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[AMQ-9459]: Added JVM Arg to open sun.nio.ch #1181
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
Conversation
|
Which versions of AMQ are you refering ? |
Issue is Observed in 5.17.6, but will Ideally occur in 5.18.x and 6.0.x |
|
@AM-19 ok it's what I thought: let me check but I don't think it happens on 6.x. |
Let me validate on 6.x, Will reply in this Thread. |
|
Ok, so I don't think we need it :) |
Actually It does occur in 6.x My bad I mis-spelled property while testing.
|
|
It works for me. Which JDK are you using (provider) ? I will do some tests but it looks like an environment issue to me. Let me double check. |
Hello, I tested using Java Runtime: Eclipse Adoptium 17.0.10. Just to double check, can you share your Runtime, Ill test using the exact version, Will see how it goes, |
|
Hello, I checked with other JVM's as well. I see the same exception. Please share your Java version, let me test with that. |
|
I will double check. But I'm surprised that it doesn't fail on Jenkins too. I'm still convinced that it's environment related (I would have see that already else). I will check with different env. |
|
Can you try with following config:
|
|
Oh you don't use the default activemq.xml ? |
|
I have to check if soTimeout exists with the transport connector you are using. |
|
Using the default |

When ActiveMQ running ActiveMQ on Java 17 or later JRE, it encounters following exception:
According to Oracle, with JEP 403 (link1) and JEP 403 (link2) which has been decided to be delivered from JDK 17 and onwards , the setAccessible approach which was introduced as part of https://issues.apache.org/jira/browse/AMQ-7121 wont work.