[infinispan-issues] [JBoss JIRA] Created: (ISPN-846) In HotRod, errors reading the header should not be hidden
Galder Zamarreño (JIRA)
jira-events at lists.jboss.org
Tue Dec 21 04:08:17 EST 2010
In HotRod, errors reading the header should not be hidden
---------------------------------------------------------
Key: ISPN-846
URL: https://issues.jboss.org/browse/ISPN-846
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 5.0.0.ALPHA1, 4.2.0.Final
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.0.0.BETA1, 5.0.0.Final
If Hot Rod has an issue reading the header (for example, the cache name), the actual issue gets hidden in the logs:
2010-12-21 10:02:49,948 TRACE [HotRodEncoder$] (HotRodServerWorker-1-1) Encode msg GetResponse{messageId=1, operation=GetResponse, status=KeyDoesNotExist, data=null}
2010-12-21 10:02:50,100 TRACE [Decoder10$] (HotRodServerWorker-1-2) Operation code: 3 has been matched to GetRequest
2010-12-21 10:02:50,538 ERROR [AbstractProtocolDecoder$] (HotRodServerWorker-1-2) Exception reported
java.util.NoSuchElementException: None.get
at scala.None$.get(Option.scala:262)
at scala.None$.get(Option.scala:260)
at org.infinispan.server.hotrod.HotRodDecoder.createServerException(HotRodDecoder.scala:138)
at org.infinispan.server.core.AbstractProtocolDecoder.decode(AbstractProtocolDecoder.scala:55)
Add better error handling for such situations.
This came from trying to debug the Python Hot Rod client.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list