-
Notifications
You must be signed in to change notification settings - Fork 11
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
setObject on ObjectMessage hangs when running in GraalVM #10
Comments
I don't see it hang, but throw, coming directly from GraalVM being unable to do the needed ObjectOutputStream.writeObject() serialization operation:
This is confirmed by oracle/graal#460, though that does now indicate support is coming in GraalVM 21.0.0 via oracle/graal#2730 |
I am currently on I am not getting the exception, only a hang. |
I was using GraalVM CE 20.3.0 and my own reproducer. Note that it isn't an [JMS]Exception that is thrown but an Error. The above code example wont catch it. |
You are right. Adding a I was expecting anything I didn't catch to bubble up through the Quarkus code and show up in the logs. |
Serialization has been added into GraalVM. Worth rechecking with a recent version. |
I will give it a go. |
I have code that creates and puts in turn TextMessage, BytesMessage, StreamMessage, ObjectMessage and MapMessage onto queues. It works when running under standard Quarkus, but when the code is compiled and run as a GraalVM executable it hangs, with no timeout on
setObject
code just enough to recreate:
The text was updated successfully, but these errors were encountered: