Forum: Building VoltDB Applications

Post: NETWORK: VoltPort died due to an unexpected exception

NETWORK: VoltPort died due to an unexpected exception
karlh
Feb 13, 2012
Hi,
we have written our own load testing package using YCSB. At some point, a few million transactions into our test (it has varied between 2 million and 8 million operations before it happens), we get one of the following errors. One thing to note is our row size, one of our columns is a 4000 character long string.

This is blocking us from getting any meaningful work done, so if there is any help we could get it would be great, as we are kind of at a loss.

Deployment: 2 node cluster with 8 sites-per-host, kfactor of 1.

ERROR 16:16:47,803 [Network Thread - 0] NETWORK: VoltPort died due to an unexpected exception
java.lang.RuntimeException: java.io.IOException: Serializable strings cannot be longer then 1048576 bytes
at org.voltdb.ClientInterface$ClientInputHandler.handleMessage(ClientInterface.java:658)
at org.voltdb.network.VoltPort.call(VoltPort.java:208)
at org.voltdb.network.VoltNetwork$4.run(VoltNetwork.java:598)
at org.voltdb.network.VoltNetwork$2.run(VoltNetwork.java:236)
at org.voltdb.network.VoltNetwork$1$1.run(VoltNetwork.java:200)
Caused by: java.io.IOException: Serializable strings cannot be longer then 1048576 bytes
at org.voltdb.messaging.FastDeserializer.readString(FastDeserializer.java:208)
at org.voltdb.StoredProcedureInvocation.readExternal(StoredProcedureInvocation.java:127)
at org.voltdb.messaging.FastDeserializer.readObject(FastDeserializer.java:114)
at org.voltdb.ClientInterface.handleRead(ClientInterface.java:910)
at org.voltdb.ClientInterface.access$1300(ClientInterface.java:89)
at org.voltdb.ClientInterface$ClientInputHandler.handleMessage(ClientInterface.java:656)
... 4 more

ERROR 15:49:33,744 [Network Thread - 0] NETWORK: VoltPort died due to an unexpected exception
java.lang.RuntimeException: java.nio.BufferUnderflowException
at org.voltdb.ClientInterface$ClientInputHandler.handleMessage(ClientInterface.java:658)
at org.voltdb.network.VoltPort.call(VoltPort.java:208)
at org.voltdb.network.VoltNetwork$4.run(VoltNetwork.java:598)
at org.voltdb.network.VoltNetwork$2.run(VoltNetwork.java:236)
at org.voltdb.network.VoltNetwork$1$1.run(VoltNetwork.java:200)
Caused by: java.nio.BufferUnderflowException
at java.nio.Buffer.nextGetIndex(Buffer.java:478)
at java.nio.HeapByteBuffer.getInt(HeapByteBuffer.java:336)
at org.voltdb.messaging.FastDeserializer.readInt(FastDeserializer.java:410)
at org.voltdb.messaging.FastDeserializer.readString(FastDeserializer.java:200)
at org.voltdb.StoredProcedureInvocation.readExternal(StoredProcedureInvocation.java:127)
at org.voltdb.messaging.FastDeserializer.readObject(FastDeserializer.java:114)
at org.voltdb.ClientInterface.handleRead(ClientInterface.java:910)
at org.voltdb.ClientInterface.access$1300(ClientInterface.java:89)
at org.voltdb.ClientInterface$ClientInputHandler.handleMessage(ClientInterface.java:656)
... 4 more
ERROR 15:51:39,078 [Network Thread - 1] NETWORK: VoltPort died due to an unexpected exception
java.lang.RuntimeException: java.io.IOException: String length is negative -2147483648
at org.voltdb.ClientInterface$ClientInputHandler.handleMessage(ClientInterface.java:658)
at org.voltdb.network.VoltPort.call(VoltPort.java:208)
at org.voltdb.network.VoltNetwork$4.run(VoltNetwork.java:598)
at org.voltdb.network.VoltNetwork$2.run(VoltNetwork.java:236)
at org.voltdb.network.VoltNetwork$1$1.run(VoltNetwork.java:200)
Caused by: java.io.IOException: String length is negative -2147483648
at org.voltdb.messaging.FastDeserializer.readString(FastDeserializer.java:212)
at org.voltdb.StoredProcedureInvocation.readExternal(StoredProcedureInvocation.java:127)
at org.voltdb.messaging.FastDeserializer.readObject(FastDeserializer.java:114)
at org.voltdb.ClientInterface.handleRead(ClientInterface.java:910)
at org.voltdb.ClientInterface.access$1300(ClientInterface.java:89)
at org.voltdb.ClientInterface$ClientInputHandler.handleMessage(ClientInterface.java:656)
... 4 more
ERROR 15:52:31,039 [Network Thread - 0] NETWORK: VoltPort died due to an unexpected exception
java.lang.RuntimeException: java.io.IOException: String length is negative -2147483648
at org.voltdb.ClientInterface$ClientInputHandler.handleMessage(ClientInterface.java:658)
at org.voltdb.network.VoltPort.call(VoltPort.java:208)
at org.voltdb.network.VoltNetwork$4.run(VoltNetwork.java:598)
at org.voltdb.network.VoltNetwork$2.run(VoltNetwork.java:236)
at org.voltdb.network.VoltNetwork$1$1.run(VoltNetwork.java:200)
Caused by: java.io.IOException: String length is negative -2147483648
at org.voltdb.messaging.FastDeserializer.readString(FastDeserializer.java:212)
at org.voltdb.StoredProcedureInvocation.readExternal(StoredProcedureInvocation.java:127)
at org.voltdb.messaging.FastDeserializer.readObject(FastDeserializer.java:114)
at org.voltdb.ClientInterface.handleRead(ClientInterface.java:910)
at org.voltdb.ClientInterface.access$1300(ClientInterface.java:89)
at org.voltdb.ClientInterface$ClientInputHandler.handleMessage(ClientInterface.java:656)
... 4 more
VoltSessionStore::CreateSession: Attempted violation of constraint
Constraint Type UNIQUE, Table CatalogId SESSIONS
header size: 237
status code: -128 column count: 14
cols (SESSION_ID:STRING), (SUB_ID:STRING), (CREATE_TIME:STRING), (LAST_UPDATED:STRING), (UPDATE_CNT:INTEGER), (SESSION_DATA:VARBINARY), (LOCK_TIMEOUT:STRING), (NEXT_TIMER_TIMEOUT:STRING), (TIMER_UPDATE_CNT:INTEGER), (NEXT_TIMER_NAME:STRING), (TIMERS:STRING), (AFFINITY_LIST:STRING), (CTE_ID:STRING), (BU_TIMER_INTERVAL:INTEGER),
rows -
1782512310,1782512510,!$)! 9#3:7*'-:25687",=8#,1329148364780,0,bin[crc:2504269880,value:0x3230333233...],NULL,","=" $09/3-94=9!5:"&3&,,0,"":.5/04/#,;4#.6#61>79&!,-"!58<??<5+<: 16 1;-14?:,022*+:%+96)5/?:"(:5$.;<%:=*/*5-41."2);$(2'/5/235,17 245(&"14#/)35!??.15;&?0.%"0:50*;&?+!?%10&031 #9-,=*=;9+,*6-,60
Hi Karl, Can you send the
aweisberg
Feb 13, 2012
Hi Karl,

Can you send the code you are using to

support@voltdb.com ?

It looks like the client library is generating a bad serialization of the request.

-Ariel
Sure, Have sent that in
karlh
Feb 13, 2012
Sure,

Have sent that in there. Will be in tomorrow if you have any questions on it.

Karl.