got IllegalSelectorException when listen to a socket on android
GoogleCodeExporter opened this issue · 5 comments
GoogleCodeExporter commented
Hi I just got a problem when using naga on android.
I have two android devices, one runs naga very well,
but the other one always got IllegalSelectorException when listen to socket.
So I searched the web says that it seems a problem wehn do
m_channelResponder.getChannel().register in RegisterChannelEvent class
the option parameter should not be 0 or it will fail.
What steps will reproduce the problem?
1. create a nioservice
2. open socket from nioService
3. listen to the socket
What is the expected output? What do you see instead?
It should be connect to socket without problem.
What version of the product are you using? On what operating system?
android 2.1-update1
Please provide any additional information below
Original issue reported on code.google.com by wxhspl...@gmail.com
on 5 Nov 2011 at 7:13
GoogleCodeExporter commented
What version of the source code are you using?
Original comment by christof...@gmail.com
on 5 Nov 2011 at 8:46
- Added labels: ****
- Removed labels: ****
GoogleCodeExporter commented
rev76 on SVN
Original comment by wxhspl...@gmail.com
on 6 Nov 2011 at 5:37
- Added labels: ****
- Removed labels: ****
GoogleCodeExporter commented
I have test it and work ok! Thanks!
Original comment by wxhspl...@gmail.com
on 8 Nov 2011 at 1:40
- Added labels: ****
- Removed labels: ****
GoogleCodeExporter commented
It seems that this is connected to differing java-implementations.
Original comment by christof...@gmail.com
on 6 Nov 2011 at 10:55
- Changed state: Started
- Added labels: ****
- Removed labels: ****
GoogleCodeExporter commented
The following fix has been checked in:
a) m_channelResponder.getChannel().register registers for all valid ops (note
that this doesn't actually affect anything, as the interest ops are then
immediately set again in the "keyInitialized"-method of internal
ChannelResponder class.
b) Explicitly sets the initial interest ops to ACCEPT for server sockets in
keyInitialized (previously it would use the default value, which would amount
to the same thing, but this should make the intention clearer).
Please let me know if this resolves your issue.
Original comment by christof...@gmail.com
on 6 Nov 2011 at 11:10
- Changed state: Fixed
- Added labels: ****
- Removed labels: ****