Open lalisand opened 1 year ago
When trying to get all fault trees, the request takes approximately 27 seconds and then we get 500 with the exception.
Can I ask you for help, please? @ledsoft Have you ever faced this problem?
@blcham
It could be that the query you use causes RDF4J to fail. Try checking the RDF4J log (located in ~/.RDF4J/server/logs
) if there is any error. Also try checking the Tomcat log running RDF4J.
It seems to be ok, there is no error. We were thinking if we can somehow set a connection timeout for request. Because it works fine on localhost (request takes 13 seconds) but it fails on the kbss.
AFAIK, RDF4J client has no connection timeout by default, so that should not be an issue. Also, are you using RDF4J server, or GraphDB? Free or SE? What version of RDF4J (or JOPA)?
GraphDB SE (the one running on onto) and JOPA 0.14.7
@Matthew-Kulich, Martin suggested upgrading JOPA first and then continuing with the investigation. (There is little chance it will be resolved by the upgrade, but we need to upgrade anyway)
Alright, I will upgrade it
Fixed. @lalisand
The loading time takes approximately 2 minutes.
@Matthew-Kulich is it deployed as well?
@blcham Yeah, it is
@Matthew-Kulich my students were testing the tool today but the issue re-appeared after 2 hours of working with the tool. Since this is a blocker for us, could you have a look on it one more time?
Yes
@lalisand It is working now. But I'm still trying to prevent this next time.
@Matthew-Kulich I do not understand why this ticket was closed. If this problem can occur again I would not close it, otherwise provide a reference to the solution, please.
@lalisand It is working now. But I'm still trying to prevent this next time.
Just to understand what u wrote here: If the problem occurs we can temporarily fix it by restarting the server right?
@Matthew-Kulich I do not understand why this ticket was closed. If this problem can occur again I would not close it, otherwise provide a reference to the solution, please.
Yeah, you're right, I should have not closed it.
Just to understand what u wrote here: If the problem occurs we can temporarily fix it by restarting the server right?
We can fix it by clearing data in GraphDB (Because there were set two values for property which can have only one at a time )
Recently, my students tried to create FTA analysis for the entire L-39NG hydraulic system (the only system currently managed within the Aero Vodochody deployment). This implied creating a component for the entire hydraulic system, and adding every subsystem as part thereof. This led to unstable behavior, probably due to the tool being overloaded. I cannot open the system, I am getting an error "failed to load fault trees". When logging in to the tool, I can see only FMEA analyses (see my screenshot below).