Server keeps Expiring Session.

[TimothyMischief]

I've tried the following in node 7.3.0, 7.3.1 and 8.0.1:

import * as v1 from 'neo4j-driver';

const neo4j = v1.v1;
const auth = neo4j.auth.basic( 'neo4j', 'password' );
console.log( 'auth.basic returned: ' + JSON.stringify( auth ));
const driver = neo4j.driver( 'bolt://localhost', auth );
const session = driver.session();

const query = `
	CREATE (string:TEST:Type {name: 'String'})
	CREATE (int:TEST:Type {name: 'Int'})
	CREATE (id:TEST:Type {name: 'ID'})
	CREATE (query:TEST:Type {name: 'Query'})
	CREATE (mutation:TEST:Type {name: 'Mutation'})
	CREATE (subscription:TEST:Type {name: 'Subscription'})
	CREATE (author:TEST:Type {name: 'Author'})
	CREATE (post:TEST:Type {name: 'Post'})
	CREATE (comment:TEST:Type {name: 'Comment'})
`

session.run( { statements: query } )
	.then( ( result ) => {
		console.log( result );
	} )
	.catch( ( err ) => { console.log( err ); } );

That gives me (with debug on):

auth.basic returned: {"scheme":"basic","principal":"neo4j","credentials":"password"}
C:INIT "neo4j-javascript/0.0.0-dev" {"scheme":"basic","principal":"neo4j","credentials":"password"}
S:SUCCESS {"server":"Neo4j/3.1.0"}
C:RUN {"statements":"\n\tCREATE (string:TEST:Type {name: 'String'})\n\tCREATE (int:TEST:Type {name: 'Int'})\n\tCREATE (id:TEST:Type {name: 'ID'})\n\t
CREATE (query:TEST:Type {name: 'Query'})\n\tCREATE (mutation:TEST:Type {name: 'Mutation'})\n\tCREATE (subscription:TEST:Type {name: 'Subscription'})\
n\tCREATE (author:TEST:Type {name: 'Author'})"} {}
C:PULL_ALL
{ Error: Connection was closed by server
    at new Neo4jError (/Users/timhope/Dev/ts-koapollo/node_modules/neo4j-driver/lib/v1/error.js:65:132)
    at newError (/Users/timhope/Dev/ts-koapollo/node_modules/neo4j-driver/lib/v1/error.js:55:10)
    at NodeChannel._handleConnectionTerminated (/Users/timhope/Dev/ts-koapollo/node_modules/neo4j-driver/lib/v1/internal/ch-node.js:330:41)
    at emitNone (events.js:91:20)
    at TLSSocket.emit (events.js:185:7)
    at endReadableNT (_stream_readable.js:974:12)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9) code: 'SessionExpired' }

I thought maybe it was a bolt or server-side problem so I tried cypher-shell.

Same query through cypher-shell:

bash-3.2$ ./neo4j-community-3.1.0/bin/cypher-shell
username: neo4j
password: ********
Connected to Neo4j 3.1.0 at bolt://localhost:7687 as user neo4j.
Type :help for a list of available commands or :exit to exit the shell.
Note that Cypher queries must end with a semicolon.
neo4j> :help

Available commands:
  :begin    Open a transaction
  :commit   Commit the currently open transaction
  :exit     Exit the logger
  :help     Show this help message
  :history  Print a list of the last commands executed
  :param    Set the value of a query parameter
  :params   Prints all currently set query parameters and their values
  :rollback Rollback the currently open transaction

For help on a specific command type:
    :help command


For help on cypher please visit:
    https://neo4j.com/docs/developer-manual/3.1-beta/cypher/

neo4j> CREATE (string:TEST:Type {name: 'String'})
       CREATE (int:TEST:Type {name: 'Int'})
       CREATE (id:TEST:Type {name: 'ID'})
       CREATE (query:TEST:Type {name: 'Query'})
       CREATE (mutation:TEST:Type {name: 'Mutation'})
       CREATE (subscription:TEST:Type {name: 'Subscription'});
Added 9 nodes

I'm absolutely stumped, any help is much appreciated. I'm going mad. I've tried a million variations of starting and closing sessions and drivers to no avail.

[lutovich]

Hi @SnappyCroissant,

Does this happen every time you run the query? Did you check neo4j database log when this error happens?

[TimothyMischief]

It's happening with all queries executed through the driver, every time.

neo4j.log, debug.log all read nothing.

query.log isn't generating despite being turned on. Neither from the cypher-shell queries or the ones coming from node. Threshold is set to 0 so it should be getting everything.

[TimothyMischief]

I've tried to recreate the issue in a fresh project and I can't. I'm thinking it's something in the project setup somewhere breaking it. For the moment I've switched to REST, this project won't see production so efficiency isn't mission critical. When I get some time though I'll see if I can isolate the problem incase anyone else runs into it.

[lutovich]

@SnappyCroissant are you using the same database instance in the fresh project? do you ever close sessions (your example does not have session.close call)?

[TimothyMischief]

In the original code that failed before I started reconfiguring to test there was a session.close call in .then and .catch. I missed them when running the examples above but still had a driver.close running on exit. And I've added session.close calls back in .then and .catch

I tried the fresh project on a new instance and the same one, same results.

I played around with it some more and got the vanilla node version working inside the original project after wiping and reinstalling all npm modules incase I'd broken somethign unknowingly going through turning on logs and playing with typings and such. But it still breaks the same way within the project so I'm thinking there's a conflict somewhere around transpiling, streams or next tick that's corrupting something on the way to the server and back.

I've started stripping things back layer by layer. Starting at where I first encountered the problem.

First encounter conditions:

• Running tests in mocha through ts-node with nyc watching for coverage

• Stopped running inside NYC

• Ran transpiled JS rather than inside ts-node

• Removed Typescript decorators from mocha-typescript

Next step is to run outside of mocha but trying to isolate the production code. Then switching from transpiled es6 imports to require statements. I've already run the script as part of the larger project which has been failing from the start. But I want to pull things out piece by piece. At the moment though none of those changes have changed anything.

It's really got me stumped. There's got to be some strange conflict somewhere. I'm definitely moving away from typescript in further projects. I've got a hobby project at home running pure node with harmony flags that is working brilliantly with this module. This combined with async await is a dream.

[lutovich]

@SnappyCroissant could you maybe create a github repo with a project that reproduces the problem? We can then take a look as well.

[TimothyMischief]

You can find it here: https://github.com/SnappyCroissant/ts-koapollo

I've cleaned it up a little and left some notes in the readme.

[lutovich]

Thanks @SnappyCroissant! We will take a look.

[lutovich]

Hi @SnappyCroissant,

I created a PR with tentative fix for this problem: https://github.com/SnappyCroissant/ts-koapollo/pull/1.

Problem happened because of session.run( { statements: query } ). This function expects first argument to be string. Second argument is optional and can be an object of query parameters. Driver does not check the type of the first query argument so it tried to send object to the server as is. This caused a protocol violation on the server and it immediately closed the connection.

I can't fully verify the fix because project does not build. Some TypeScript errors...

We need to improve logging in the database and possibly verify types in session.run arguments.

Please let me know if this helps.

[TimothyMischief]

That's worked! I'm not sure where I got that structure for parameters, or how I managed to miss it. Maybe from early attempts with other libraries it got left over. I'm glad something has come of my mistake though.

Thanks for all your help!

[lutovich]

Hi @SnappyCroissant,

Both PRs are now merged. Error logging will be available in next neo4j 3.1.1 and 3.2. Parameter type checks will be available in JS driver 1.1.0 or 1.2.

Thanks for your help!

[Prateek218]

Hi @SnappyCroissant and @lutovich
I'm facing the same issue can you plz help me and tell me where I can find the solution.
I'm new to neo4j and node plz help me