[
https://issues.apache.org/jira/browse/THRIFT-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216867#comment-14216867
]
Branden Visser commented on THRIFT-1754:
----------------------------------------
There is a unit test over in a github fork of this that reproduces the issue:
https://github.com/simplereach/node-thrift/commit/602b7b275641016b30ebd715ee40288e3418080a
If that unit test can be ported, then it would be possible to ensure it is
resolved.
> RangeError in buffer handling
> -----------------------------
>
> Key: THRIFT-1754
> URL: https://issues.apache.org/jira/browse/THRIFT-1754
> Project: Thrift
> Issue Type: Bug
> Components: Node.js - Library
> Affects Versions: 0.9
> Environment: Ubuntu 12.04, Node.js v0.8.8
> Reporter: Vesa Poikajärvi
> Assignee: Randy Abernethy
> Priority: Minor
> Fix For: 0.9.2
>
>
> I have a Node.js service that connects to multiple Thrift servers (using
> TFramedTransport with C++ servers and TBufferedTransport with Python
> servers). Every now and then for reasons rather hard to track the following
> happens:
> {noformat}
> buffer.js:242
> this.parent = new SlowBuffer(this.length);
> ^
> RangeError: length > kMaxLength
> at new Buffer (buffer.js:242:21)
> at Socket.TFramedTransport.receiver
> (/home/me/my_service/node_modules/thrift/lib/thrift/transport.js:59:17)
> at Socket.EventEmitter.emit (events.js:88:17)
> at TCP.onread (net.js:395:14)
> {noformat}
> Node module is extracted from Thrift 0.9 tarball due to THRIFT-1637. And as
> mentioned, I cannot really tell what triggers the behavior. When running in
> development mode I use [Forever|https://github.com/nodejitsu/forever] to
> relaunch a crashed process, and when it first crashes because of this it will
> keep relaunching a few times, maybe ten or so (I connect to the services upon
> startup), and then it starts working again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
