[ http://issues.apache.org/jira/brows...INA-91?page=all ]

Trustin Lee closed DIRMINA-91:
------------------------------

Resolution: Fixed

I found that IoAdapter don't delay the release of the buffer which caused de
coding failure.  The buffer will be released immediately when IoAdapter.Sess
ionHandlerAdapter.dataRead() method returns regardless ProtocolViolationExce
ption uses it or not.

I fixed this issue by acquiring the buffer once more when I create ProtocolV
iolationException.

> BufferUnderflowException while calling ProtocolViolationException.getMessa
ge()
> --------------------------------------------------------------------------
----
>
>          Key: DIRMINA-91
>          URL: http://issues.apache.org/jira/browse/DIRMINA-91
>      Project: Directory MINA
>         Type: Bug
>     Versions: 0.7
>     Reporter: Trustin Lee
>     Assignee: Trustin Lee
>     Priority: Minor
>      Fix For: 0.8

>
> This issues has been posted to MINA forum by Thomas:
> http://gleamynode.net/dev/forum/read.php?1,146
> Posted by: Thomas (aurorum10-0.aurorum.se)
> Date: September 21, 2005 11:00PM
> Hi. I'm running a server with mina 0.7.4 on linux and somtimes I get a Buf
ferUnderflowException in my server. It dosn't seem to affect the server howe
ver.
> java.nio.BufferUnderflowException
> at java.nio.Buffer.nextGetIndex(Buffer.java:398)
> at java.nio.DirectByteBuffer.get(DirectByteBuffer.java:205)
> at org.apache.mina.common.ByteBuffer$DefaultByteBuffer.get(ByteBuffer.java
:720)
> at org.apache.mina.common.ByteBufferHexDumper.getHexdump(ByteBufferHexDump
er.java:78)
> at org.apache.mina.common.ByteBuffer$DefaultByteBuffer.getHexDump(ByteBuff
er.java:1029)
> at org.apache.mina.protocol.ProtocolViolationException.getMessage(Protocol
ViolationException.java:84)
> at com.agency9.network.masterserver.A9MasterProtocolHandler.exceptionCaugh
t(A9MasterProtocolHandler.java:41)
> at org.apache.mina.protocol.AbstractProtocolFilterChain$2.exceptionCaught(
AbstractProtocolFilterChain.java:142)
> at org.apache.mina.protocol.AbstractProtocolFilterChain.callNextExceptionC
aught(AbstractProtocolFilterChain.java:405)
> at org.apache.mina.protocol.AbstractProtocolFilterChain.access$900(Abstrac
tProtocolFilterChain.java:50)
> at org.apache.mina.protocol.AbstractProtocolFilterChain$Entry$1.exceptionC
aught(AbstractProtocolFilterChain.java:518)
> at org.apache.mina.protocol.AbstractProtocolFilterChain$1.exceptionCaught(
AbstractProtocolFilterChain.java:93)
> at org.apache.mina.protocol.AbstractProtocolFilterChain.callNextExceptionC
aught(AbstractProtocolFilterChain.java:405)
> at org.apache.mina.protocol.AbstractProtocolFilterChain.exceptionCaught(Ab
stractProtocolFilterChain.java:396)
> at org.apache.mina.protocol.ProtocolSessionManagerFilterChain$1.exceptionC
aught(ProtocolSessionManagerFilterChain.java:71)
> at org.apache.mina.protocol.AbstractProtocolFilterChain.callNextExceptionC
aught(AbstractProtocolFilterChain.java:405)
> at org.apache.mina.protocol.AbstractProtocolFilterChain.access$900(Abstrac
tProtocolFilterChain.java:50)
> at org.apache.mina.protocol.AbstractProtocolFilterChain$Entry$1.exceptionC
aught(AbstractProtocolFilterChain.java:518)
> at org.apache.mina.protocol.filter.ProtocolThreadPoolFilter.processEvent(P
rotocolThreadPoolFilter.java:116)
> at org.apache.mina.util.BaseThreadPool$Worker.processEvents(BaseThreadPool
.java:393)
> at org.apache.mina.util.BaseThreadPool$Worker.run(BaseThreadPool.java:333)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira

[ Post a follow-up to this message ]