ByteBuffer is getting initialized inside DefaultThreadPool, which is
located in grizzly-utils module.
Can I ask you, Sebastien, to provide a test case to reproduce issue?
Thank you.
WBR,
Alexey.
On Jan 12, 2009, at 16:24 , Jeanfrancois Arcand wrote:
> Salut,
>
> Sebastian Dehne wrote:
>> Dear list,
>> I've upgraded from 1.8.6 to 1.9.3 and used a ExecutorService with
>> own ThreadFactoryas shown on http://blogs.sun.com/oleksiys/entry/grizzly_1_9_0_executorservice
>> .
>> However, now I run into a NPE @ ReadFilter:124 because the
>> byteBuffer has never been set with this thread. I've done some
>> source-coding browsing and it seems to me there is no way this
>> buffer is ever set. The method
>> WorkerThreadImpl.createByteBuffer(boolean) is only used if the
>> DefaultThreadPool is used, which is not the case here.
>
> Looks like a bug to me. Can you file an issue here so we can fix it
> for our 1.9.4 releae (this week).
>
> https://grizzly.dev.java.net/issues/
>
> Thanks!
>
> -- Jeanfrancois
>
>> Any suggestions?
>> Thanks & kind regards,
>> Sebastian Dehne
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>