ok, I see. Well, killing the jvm is not a fix of course, but yes, in 2.7.4, this crude workaround at least won't bust the data.
But the real point of the Issue is that one rogue query should not jeopardize the entire application server, i.e. it needs to abort when instructed to do so From: Andy Seaborne <[email protected]> To: [email protected] Date: 10/04/2012 04:52 PM Subject: Re: 2.7.4 release? On 04/10/12 21:34, Simon Helsen wrote: > "And the email earlier this week?" > > well, it was musing about whether to release SDB together with the rest as > 2.7.4, but it was also considering not doing this. > > "Starting testing." > > I assume I have to read this as "start testing"? > > One additional question (not blocking a new release!): in JENA 289, you > write "So 2.7.4 will provide a crude workaround for now ". How is that to > be understood? (this discussion can move to the JIRA issue) You can kill the JVM. As per your dig at 2.7.1 vs 2.7.4, that's now safe. And anyway, all JENA-289 gives you is platform integrity - as you will then be killing application queries, the app is not helped. The queries have to be fixed anyway (c.f. JENA-294 [*]) Andy [*] https://issues.apache.org/jira/browse/JENA-294?focusedCommentId=13451979&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13451979 > > Simon
