-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Intermittent failure to serialize payloads with boolean
field (jackson 2.15.2)
#4715
Comments
We prefer to get cases where the problem is minimised to just involving Jackson. Noone is going to voluntarily try to reproduce your scenario which is far from fully described - which if I repeat it here, involves purchasing licenses for Websphere, setting up an instance, coding and deploying a POC and sending it messages for a week or 2 and then debugging. Have you even looked at the possibility that some of the messages are malformed and how your code reacts to those malformed messages? |
The same requests work on other servers, same server after the server restart. |
It could be anything: maybe your JVM server got corrupted, maybe there's memory problem, firewall problem, could be anything. 🤷♂️ You should get your team's/company's senior devs to investigate this. |
And one additional note: 2.15.2 is not the latest version, so you'd really want to try out with either latest release (2.17.2) or pre-release (2.18.0-rc1). |
we had ibm check the issue and they have confirmed it is not related to jvm server or memory problem, firewall problem. |
What we need is a reproduction. Jackson-only reproduction to be more specific. Without seeing how it is used, we cannot tell what is causing the problem |
This is just my opinion. This issue is super hard to reproduce and there are lots of moving parts. If this was my problem, I would try replacing the code that I suspect. There are lots of alternative libraries for working with JSON. |
Can you at least share the stack trace of the error? |
@fc76gsk Are you seriously not going to include any useful information here?!?! What the #%(%^ is "failed to serialize payload error"? Stack trace is absolutely needed, even if no reproduction available. Similarly "the behavior changed suddenly and the surrounding code has been the same since 2021" -- suddenly when? Upgrading Jackson version? If so, from which (and to which) version? Did you try newer versions? 2.15 hasn't been latest for a while. I would not immediately recommend "use something other than Jackson" like @pjfanning often suggests. But without more information there's very little we can do. |
We are not able to reproduce this issue. |
@fc76gsk can you share the source for (I think I can already guess where this is going...) |
This is the class
|
Why are you sharing (incomplete!!!) source code for |
this is the same class, updated the name, pls check |
Please show the getter and setter. And are you sure the type is |
|
So it wasn't due to unwrapping a null wrapper to primitive, which would've resulted in different exception thrown:
...while yours is:
What exactly is that UPDATE |
I'm suspecting that the thing being serialised is a proxy/bytecode-manipulated and sometimes it goes bad (eg ThreadLocal problem, or other causes?). What I recommend is to add some code to call That's all I can offer with my limited knowledge. Maybe other people have better thoughts. |
At this point we should probably stop @fc76gsk from throwing out questions, without giving answers to the questions asked 🤔 |
While vague, it sounds more like something in JDK is having rare issues with Reflection-based |
just to make it clear again to @JooHyukKim we are unable to reproduce this, this happens for some time and when we restart the server it stops, all the same requests work, what other questions do you want me to answer here, these are provided in the initial issue already |
At this point I am unfortunately not sure what we could do. Symptoms do not point to anything Jackson could do, change, nor is there a reproduction As I said, I would look into JDK version, ensure it's the latest. Will leave open for a bit in case anyone has any ideas, suggestions. |
boolean
field (jackson 2.15.2)
Search before asking
Describe the bug
getting - failed to serialize payload error for boolean field intermittently with java liberty servers, few times a week and then all the requests are getting same error until the server is restarted. we are using java 1.8, ibm websphere application server liberty 21.0.0.9
2.15.2 version of jackson databind
Version Information
2.15.2
Reproduction
<-- Any of the following
-->
The payload is not having this field being sent, but intermittently we are getting failed to serialize payload error for this and then the particular server on which it started this error will start for all the other api calls and the server becomes non-responsive, after restart of the server the server becomes normal and no error for most of the time, and then happens once a week or two weeks
Expected behavior
no serialization error
Additional context
No response
The text was updated successfully, but these errors were encountered: