[Mulgara-dev] Lost phase token

Paul Gearon gearon at ieee.org
Wed Sep 23 18:26:28 UTC 2009


On Wed, Sep 23, 2009 at 1:22 PM, Alex Hall <alexhall at revelytix.com> wrote:
> James Leigh wrote:
>> What else could be causing this lost phase token?
>
> It could still be an Answer object, if you're doing explicit transaction
> management by setting autocommit to false.  In that case the new phase
> is created upon the first modify operation, and any subsequent query
> operations made before that transaction is committed will reference that
> same phase.  If you leave autocommit set to true, as is the default,
> then it's correct that Answers are not going to be your culprit.
>
> -Alex

It's not an Answer. The stack trace shows that the phase was created
when a statement was inserted. The phase can only be released during
prepare/commit, so this isn't happening. The only other thing that can
happen (other than prepare/commit) is a crash or a rollback. Given
that he's running out of heap, then this looks to be the issue.

Paul



More information about the Mulgara-dev mailing list