Skip to content

Transport Exception? #34

Open
kvaccaro opened this Issue Jan 11, 2011 · 1 comment

2 participants

@kvaccaro

I thought things were going so well :) but now when I try to copy any large amount of data into flockdb, I get the following transport exception error. Any ideas what's going wrong? Suggestions for how to fix it?

irb(main):447:0> while row = res.fetch_row do
irb(main):448:1* flock.add(Integer(row[0]),:follows,Integer(row[1]))
irb(main):449:1> end
Flock::Edges::FlockDB::Client::TransportException: Flock::Edges::FlockDB::Client::TransportException
from /var/lib/gems/1.8/gems/thrift-0.2.0.4/lib/thrift/transport/socket.rb:119:in read'
from /var/lib/gems/1.8/gems/thrift-0.2.0.4/lib/thrift/transport/buffered_transport.rb:50:in
read'
from /var/lib/gems/1.8/gems/thrift-0.2.0.4/lib/thrift/transport/base_transport.rb:52:in read_all'
from /var/lib/gems/1.8/gems/thrift-0.2.0.4/lib/thrift/protocol/binary_protocol.rb:186:in
read_i32'
from /var/lib/gems/1.8/gems/thrift-0.2.0.4/lib/thrift/protocol/binary_protocol.rb:111:in read_message_begin'
from /var/lib/gems/1.8/gems/thrift-0.2.0.4/lib/thrift/client.rb:45:in
receive_message'
from /var/lib/gems/1.8/gems/flockdb-0.5.1/lib/flock/gen-rb/flock_d_b.rb:106:in recv_execute'
from /var/lib/gems/1.8/gems/flockdb-0.5.1/lib/flock/gen-rb/flock_d_b.rb:98:in
execute'
from /var/lib/gems/1.8/gems/thrift_client-0.5.0/lib/thrift_client/abstract_thrift_client.rb:115:in send'
from /var/lib/gems/1.8/gems/thrift_client-0.5.0/lib/thrift_client/abstract_thrift_client.rb:115:in
handled_proxy'
from /var/lib/gems/1.8/gems/thrift_client-0.5.0/lib/thrift_client/abstract_thrift_client.rb:57:in execute'
from /var/lib/gems/1.8/gems/flockdb-0.5.1/lib/flock/operations/execute_operations.rb:13:in
apply'
from /var/lib/gems/1.8/gems/flockdb-0.5.1/lib/flock/client.rb:77:in update'
from /var/lib/gems/1.8/gems/flockdb-0.5.1/lib/flock/client.rb:82:in
add'
from (irb):448
from /usr/lib/ruby/1.8/rubygems.rb:123

@robey
robey commented Jan 12, 2011

did it maybe just disconnect due to idleness or something? maybe the client library should retry more aggressively.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.