[SNMP4J] DefaultTcpTransportMapping.SocketEnry.nextMessage() needs to be synchronized

[Frank Fock]

Hi Larry,

You are right, the bug is obvious.
It will be fixed in the next release (1.9), which
will be available very soon (early next week).
Besides several fixes, it will add (optional)
3DES support.

Best regards,
Frank

Sachs, Larry wrote:
> Hi Frank,
> 
>  
> 
> Just like DefaultTcpTransportMapping.SocketEnry.addMessage(),
> DefaultTcpTransportMapping.SocketEnry.nextMessage() needs to be
> synchronized.  In our multi-threaded app I've seen this occasionally:
> 
>  
> 
> 2007-09-21 07:30:17,660 [DefaultTCPTransportMapping_134.242.164.192/0]
> WARN  taskexecutor Encountered unhandled exception
> 
> java.util.NoSuchElementException
> 
>         at java.util.LinkedList.remove(LinkedList.java:644)
> 
>         at java.util.LinkedList.removeFirst(LinkedList.java:134)
> 
>         at
> com.ncube.nable.app.subagent.DefaultTcpTransportMapping$SocketEntry.next
> Message(DefaultTcpTransportMapping.java:393)
> 
>         at
> com.ncube.nable.app.subagent.DefaultTcpTransportMapping$ServerThread.wri
> teMessage(DefaultTcpTransportMapping.java:887)
> 
>         at
> com.ncube.nable.app.subagent.DefaultTcpTransportMapping$ServerThread.run
> (DefaultTcpTransportMapping.java:672)
> 
>  
> 
>  
> 
> Thanks,
> 
> ls
> 
> 
> _______________________________________________
> SNMP4J mailing list
> SNMP4J at agentpp.org
> http://lists.agentpp.org/mailman/listinfo/snmp4j

-- 
AGENT++
http://www.agentpp.com
http://www.mibexplorer.com
http://www.mibdesigner.com