Needless to say I am new to both Heroku and GrapheneDB. I have a Nodejs app using Neo4j that runs fine on my local machine. I moved it to Heroku and used GrapheneDB to connect the neo4j DB to the app. When I run the app on Heroku I get a H12 Request timeout when I try to login which require the database access. The only change in my code is the following recommended by GrapheneDB:
var graphenedbURL = process.env.GRAPHENEDB_BOLT_URL;
var graphenedbUser = process.env.GRAPHENEDB_BOLT_USER;
var graphenedbPass = process.env.GRAPHENEDB_BOLT_PASSWORD;
var driver = neo4j.driver(graphenedbURL, neo4j.auth.basic(graphenedbUser, graphenedbPass));
//var driver = neo4j.driver("bolt://localhost", neo4j.auth.basic("neo4j", "xxxxx"));
where I added the first four lines and commented out the fifth line. The non-DB functions of the app works fine but any attempt to connect to the db result in a H12. I am using Javascript with Neo4j 3.0.8 and papertail for logging. The following is the papertail log when I tried to register a user:
Feb 09 18:53:44 puppydog-dev-2017 heroku/router: at=error code=H12 desc="Request timeout" method=POST path="/users/registerowner" host=puppydog-dev-2017.herokuapp.com request_id=867c7bc5-2d61-4c82-8b42-87732b21d449 fwd="104.244.227.83" dyno=web.1 connect=1ms service=30000ms status=503 bytes=0
Can anyone shed some light on whats happening here?
I discovered that the H12 is as a result of the DB being shutdown by a reset from the GrapheneDb platform. All subsequent calls to the DB result in H12 since the DB is not available. The original problem that cause the DB to shutdown is still unknown.