Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connection closure issue Blueprint Neo4j Graph #127

Open
i-am-senthil opened this issue Feb 20, 2023 · 0 comments
Open

Connection closure issue Blueprint Neo4j Graph #127

i-am-senthil opened this issue Feb 20, 2023 · 0 comments

Comments

@i-am-senthil
Copy link

Hello Team,

We are using Neo4j graph to persist the EMF model in our spring boot microservice.

After creating the persistence resource and its usage, we are calling the close() method to release the resource. We have made sure that we are releasing the resource once we have used it.

The ideal assumption is that the resource stream is closed.

We recently observed that when we restart our microservice ( the logs related to connection closure get generated).

17:05:01.751: [APP/PROC/WEB.0] 2023-Feb-20 11:35:01 [INFO ]                                          - PersistenceBackend closed: neo-blueprints:/app/EasyConfig/prod/_-rwqgLECEe2VX6-YCsGRfQ 17:05:01.751: [CELL/SSHD.0] Exit status 017:05:01.751: [APP/PROC/WEB.0] 2023-Feb-20 11:35:01 [INFO ]                                          - PersistenceBackend closed: neo-blueprints:/app/EasyConfig/prod/_-rwqgLECEe2VX6-YCsGRfQ 17:05:01.752: [APP/PROC/WEB.0] 2023-Feb-20 11:35:01 [INFO ]                                          - PersistenceBackend closed: neo-blueprints:/app/EasyConfig/prod/_-rwqgLECEe2VX6-YCsGRfQ 17:05:01.753: [APP/PROC/WEB.0] 2023-Feb-20 11:35:01 [INFO ]                                          - PersistenceBackend closed: neo-blueprints:/app/EasyConfig/prod/_-rwqgLECEe2VX6-YCsGRfQ 17:05:01.753: [APP/PROC/WEB.0] 2023-Feb-20 11:35:01 [INFO ]                                          - PersistenceBackend closed: neo-blueprints:/app/EasyConfig/prod/_-rwqgLECEe2VX6-YCsGRfQ 17:05:01.753: [APP/PROC/WEB.0] 2023-Feb-20 11:35:01 [INFO ]                                          - PersistenceBackend closed: neo-blueprints:/app/EasyConfig/prod/_-rwqgLECEe2VX6-YCsGRfQ 17:05:01.753: [APP/PROC/WEB.0] 2023-Feb-20 11:35:01 [INFO ]                                          - PersistenceBackend closed: neo-blueprints:/app/EasyConfig/prod/_-rwqgLECEe2VX6-YCsGRfQ 17:05:01.753: [APP/PROC/WEB.0] 2023-Feb-20 11:35:01 [INFO ]                                          - PersistenceBackend closed: neo-blueprints:/app/EasyConfig/prod/_-rwqgLECEe2VX6-YCsGRfQ 17:05:01.754: [APP/PROC/WEB.0] 2023-Feb-20 11:35:01 [INFO ]                                          - PersistenceBackend closed: neo-blueprints:/app/EasyConfig/prod/_-rwqgLECEe2VX6-YCsGRfQ

I am wondering why these logs get generated even when we have made sure all the resources are closed.

We are running into a situation where our app is not able to create connections to neo emf when more users are using it. We are forced to restart our application. (On the restart, we see a ton of connection closure logs as mentioned above).

It will be great if we can know why this could happen.

Thanks,
Senthil

Note:
We don't have concurrent access situation. Each user is working independently on his piece
We are using v1.03 of neoemf library and can't update to the latest version due to deadlines

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant