Re: [topbraid-users] EDG - Imported 100,000 enumeration elements .. now getting 500 HTTP Error.

Holger Knublauch Thu, 04 May 2023 05:02:54 -0700

Hi David,

thanks for the info. I am asking for these details because I do not yet understand how a stack overflow could have happened in that code. I tried to reproduce deleting an enumeration (assuming we are talking about the same thing with edg:Enumeration instances) with the attached file, but there is only one level of recursion but no runaway recursion.

The cases in which it could enter a deeper recursion would involve blank node structures - are you by any chance using those?

--
The topics of this mailing list include TopBraid EDG and related technologies such as SHACL.
To post to this group, send email to [email protected]
---
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/B31C99A2-E17F-4AAB-B8F6-D7A96BAFF3F3%40topquadrant.com.

test_enum.ttl
Description: Binary data

Now thinking more about this, do you mean rdf:Lists by any chance? Those would be blank nodes and may cause recursive delete problems.

If you cannot delete them in any other way, you could export the graph to a file, clear the graph and replace it with a hand-edited copy of the exported file. Or use the Source Code panel to delete the rdf:List.

Holger

On 4 May 2023, at 12:14 pm, David Medinets <[email protected]> wrote:

Thanks for a quick response.

> is this a stack overflow error? If yes, could you send the stack trace? I can see that MutationSupport.delete calls itself so there may be some corner cases.

Yes, the MutationSupport.delete calls itself hundreds of times. I can't share the stack trace. The version is a bit old. I think 7.1. If the delete is still calling itself, please see if that can be avoided in a future version.

> And also to clarify, did you delete these enumerations after importing them, or what were the steps that took you there.

The delete failed. I tried deleting in several ways:

* Close file without saving.
* Delete the class - using every delete button I could find.
* Delete a named individual of the class.

> What happens when you reboot - some other error message?

Same message.

On Wed, May 3, 2023 at 1:09 PM Holger Knublauch <[email protected]> wrote:

On 3 May 2023, at 5:58 pm, David Medinets <[email protected]> wrote:

The import worked but something is broken. I am seeing 500 HTTP error. The server loops running MutationSupport.delete(). I assume it runs out of RAM before it runs out of enumeration elements.

Just checking: is this a stack overflow error? If yes, could you send the stack trace? I can see that MutationSupport.delete calls itself so there may be some corner cases.

And also to clarify, did you delete these enumerations after importing them, or what were the steps that took you there.

I tried rebooting without success.

What happens when you reboot - some other error message?

Holger
Can I reset the cache by SSHing to the server?

--
The topics of this mailing list include TopBraid EDG and related technologies such as SHACL.
To post to this group, send email to [email protected]
---
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/CAOiJXP7AXTQ0bc199XCEU1z8P_k_74WbTDDjnsQj-pMnHgq%3DMQ%40mail.gmail.com.

Re: [topbraid-users] EDG - Imported 100,000 enumeration elements .. now getting 500 HTTP Error.

Reply via email to