davidnadeau opened a new issue, #1763:
URL: https://github.com/apache/fury/issues/1763

   ### Search before asking
   
   - [X] I had searched in the [issues](https://github.com/apache/fury/issues) 
and found no similar issues.
   
   
   ### Version
   
   0.6.0
   
   ### Component(s)
   
   Java
   
   ### Minimal reproduce step
   
   I have not been able to produce a minimal code example. It is very difficult 
to debug, since I am just getting: `java.lang.NullPointerException: null` as 
the exception.
   
   I am seeing large numbers of null pointers when trying to serialize data. I 
wonder if the ThreadPoolFury.execute function is thread safe.
   
   ### What did you expect to see?
   
   No null pointers when serializing data.
   
   ### What did you see instead?
   
   j.l.NullPointerException: null
   
   ### Anything Else?
   
   I am using Scala 2.13.12, my application runs in k8s (debian 11), with JDK 
17.
   
   I configure Fury in a scala Object like so:
   
   ```scala
   object FuryUtils {
     lazy val fury = Fury
       .builder()
       .withLanguage(Language.JAVA)
       .withScalaOptimizationEnabled(true)
       .requireClassRegistration(false)
       .withRefTracking(false)
       .buildThreadSafeFuryPool(Runtime.getRuntime.availableProcessors() * 2, 
Runtime.getRuntime.availableProcessors() * 2)
   }
   ```
   
   and i serialize/deserialze my values like:
   ```scala
   fury.serialize(value)
   fury.deserialize(bytes).asInstanceOf[MyData]
   ```
   
   I am calling this function ~20,000 per second. And it is failing ~30 times 
per second.
   
   ### Are you willing to submit a PR?
   
   - [ ] I'm willing to submit a PR!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to