Re: [Owlim-discussion] RepositoryConnection.clear() very slow
Am I the only one who experiences this problem or thinks that it is indeed a problem? cheers, johann On 2012-01-16 17:54, Johann Petrak wrote: Hi all, I found recently that even with a moderately-sized ontology, performing RepositoryConnection.clear() takes a very long time (tens of minutes for a few dozen classes with a few thousand instances). I am experiencing this with OWLIM-Lite 4.3 combined with openrdf-sesame 2.6.1. Have not tried this with OWLIM-SE. I understand that removing triples can be a time-consuming process with a forward-chaining strategy but in the case of clear(), should this not be much faster as it is certain that all triples can be removed? Cheers, johann ___ OWLIM-discussion mailing list OWLIM-discussion@ontotext.com http://ontotext.com/mailman/listinfo/owlim-discussion
[Owlim-discussion] Problem with jdk1.7.0_02
Is there any known problem when using Sesame/OWLIM-Lite on a 32 bit Linux system with JDK 1.7.0_02? I am seeing a hanging condition which does not occur with Java 1.6.x in my app which embeds OWLIM-Lite and thought I ask about this before digging deeper. Cheers, johann ___ OWLIM-discussion mailing list OWLIM-discussion@ontotext.com http://ontotext.com/mailman/listinfo/owlim-discussion
[Owlim-discussion] Sesame 2.6.3 officially supported with OWLIM 4.3?
As was pointed out to me, Sesame 2.6.3 seems to fix problems with using Java 1.7. So I am wondering is Sesame 2.6.3 officially supported and known to be compatible with OWLIM 4.3 (especially OWLIM-Lite 4.3.4248 which originally came with sesame 2.6.0)? Should I assume compatibility if Sesame is receiving an update in its maintenance version number or minor version number? Is it possible to find out about testing results with more recent sesame version on the owlim webpage somewhere? Cheers, johann ___ OWLIM-discussion mailing list OWLIM-discussion@ontotext.com http://ontotext.com/mailman/listinfo/owlim-discussion
Re: [Owlim-discussion] Problem with jdk1.7.0_02
Hi, from my experience there is problem with jdk1.7.x and Sesame. In my case I can't simply run Sesame Console, so I think the issue is connected somehow with sesame. Try to replace your version of sesame lib, with the new one 2.6.3(it is not mentioned on main page but it is in download repository). Maybe your problem will dissapear. Marek___ OWLIM-discussion mailing list OWLIM-discussion@ontotext.com http://ontotext.com/mailman/listinfo/owlim-discussion
Re: [Owlim-discussion] JMX monitoring in OWLIM-SE 4.2
Hi Jerven,
I also wasn't able to reproduce your problem, nor do I see anything wrong with
the code registering the mbeans. Could you please have a look at the Sesame
logs for any warnings about failing to register mbeans?
Regards,
Dimitar
On Wednesday 25 Jan 2012 15:12:46 Jerven Bolleman wrote:
Hi Barry,
I am just raising this issue again.
Sometimes the com.ontotext.AVLRepositoryManager bean does not seem to
register itself other times it does.
I get the instance via the PlatformMBeanServer which works most of the
time but sometimes there is nothing there.
final ObjectName avl = new
ObjectName(com.ontotext:type=AVLRepositoryManager,*);
for (final ObjectName instance :
ManagementFactory.getPlatformMBeanServer().queryNames(avl, null))
{
ManagementFactory.getPlatformMBeanServer().setAttribute(instance,
new Attribute(CollectionsStatisticsFlag,
true));
}
using Jconsole or visualvm mbean also show no ontotext beans in this
case. As this differs run to run could you have a look at the code you
use to register these beans to the MBeanServer?
Regards,
Jerven
On 10/07/2011 11:12 PM, Barry Bishop wrote:
Hi Jerven,
This might be a stupid question, but have you enabled JMX in Tomcat?
i.e. with kind of thing:
-Dcom.sun.management.jmxremote.port=8089
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
If you have then I will investigate further, because it is working at
the moment and I don't remember any issues being raised about this.
Have a great weekend,
barry
--
Barry Bishop
OWLIM Product Manager
Ontotext AD
Tel: +43 650 2000 237
email:barry.bis...@ontotext.com
www.ontotext.com
On 07/10/11 16:34, Jerven Bolleman wrote:
Dear Owlim developers,
Is it just me or have the JMX beans disappeared in release 4.2?
Both my statistics code and JVisualVM no longer see them.
Regards,
Jerven
___
OWLIM-discussion mailing list
OWLIM-discussion@ontotext.com
http://ontotext.com/mailman/listinfo/owlim-discussion
___
OWLIM-discussion mailing list
OWLIM-discussion@ontotext.com
http://ontotext.com/mailman/listinfo/owlim-discussion
Re: [Owlim-discussion] RepositoryConnection.clear() very slow
Johann, we experience this problem also with OWLIM-Lite. Barry Norton at a Meetup in NYC recommended going to OWLIM-SE, if you can get a copy from Ontotext. We have our copy but have not tested it yet. John - Original Message - From: Johann Petrak johann.pet...@jpetrak.com To: owlim-discussion@ontotext.com Sent: Wednesday, January 25, 2012 6:34:06 AM Subject: Re: [Owlim-discussion] RepositoryConnection.clear() very slow Am I the only one who experiences this problem or thinks that it is indeed a problem? cheers, johann On 2012-01-16 17:54, Johann Petrak wrote: Hi all, I found recently that even with a moderately-sized ontology, performing RepositoryConnection.clear() takes a very long time (tens of minutes for a few dozen classes with a few thousand instances). I am experiencing this with OWLIM-Lite 4.3 combined with openrdf-sesame 2.6.1. Have not tried this with OWLIM-SE. I understand that removing triples can be a time-consuming process with a forward-chaining strategy but in the case of clear(), should this not be much faster as it is certain that all triples can be removed? Cheers, johann ___ OWLIM-discussion mailing list OWLIM-discussion@ontotext.com http://ontotext.com/mailman/listinfo/owlim-discussion ___ OWLIM-discussion mailing list OWLIM-discussion@ontotext.com http://ontotext.com/mailman/listinfo/owlim-discussion
Re: [Owlim-discussion] JMX monitoring in OWLIM-SE 4.2
Hi Dimitar,
No nothing shows up in the logs. Anything I should look out for?
By the way I do not use the sesame web app so if the mbean registering depends
on this somehow let me know.
Regards,
Jerven
On Jan 25, 2012, at 2:51 PM, Dimitar Toshev wrote:
Hi Jerven,
I also wasn't able to reproduce your problem, nor do I see anything wrong
with
the code registering the mbeans. Could you please have a look at the Sesame
logs for any warnings about failing to register mbeans?
Regards,
Dimitar
On Wednesday 25 Jan 2012 15:12:46 Jerven Bolleman wrote:
Hi Barry,
I am just raising this issue again.
Sometimes the com.ontotext.AVLRepositoryManager bean does not seem to
register itself other times it does.
I get the instance via the PlatformMBeanServer which works most of the
time but sometimes there is nothing there.
final ObjectName avl = new
ObjectName(com.ontotext:type=AVLRepositoryManager,*);
for (final ObjectName instance :
ManagementFactory.getPlatformMBeanServer().queryNames(avl, null))
{
ManagementFactory.getPlatformMBeanServer().setAttribute(instance,
new Attribute(CollectionsStatisticsFlag,
true));
}
using Jconsole or visualvm mbean also show no ontotext beans in this
case. As this differs run to run could you have a look at the code you
use to register these beans to the MBeanServer?
Regards,
Jerven
On 10/07/2011 11:12 PM, Barry Bishop wrote:
Hi Jerven,
This might be a stupid question, but have you enabled JMX in Tomcat?
i.e. with kind of thing:
-Dcom.sun.management.jmxremote.port=8089
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
If you have then I will investigate further, because it is working at
the moment and I don't remember any issues being raised about this.
Have a great weekend,
barry
--
Barry Bishop
OWLIM Product Manager
Ontotext AD
Tel: +43 650 2000 237
email:barry.bis...@ontotext.com
www.ontotext.com
On 07/10/11 16:34, Jerven Bolleman wrote:
Dear Owlim developers,
Is it just me or have the JMX beans disappeared in release 4.2?
Both my statistics code and JVisualVM no longer see them.
Regards,
Jerven
___
OWLIM-discussion mailing list
OWLIM-discussion@ontotext.com
http://ontotext.com/mailman/listinfo/owlim-discussion
___
OWLIM-discussion mailing list
OWLIM-discussion@ontotext.com
http://ontotext.com/mailman/listinfo/owlim-discussion
Re: [Owlim-discussion] RepositoryConnection.clear() very slow
Hi Johann, We have a test-case to check for excessive execution times that uses OWLIM-Lite with the owl2-rl-conf ruleset and a handful of statements. I tried adding a lot more statements and it does take longer, but nowhere near as long as you say. The only way I can make things take an excessive time is a combination of owl2-rl-conf ruleset and more than about 5000 statements. What rule-set are you using? barry On 25/01/12 12:34, Johann Petrak wrote: Am I the only one who experiences this problem or thinks that it is indeed a problem? cheers, johann On 2012-01-16 17:54, Johann Petrak wrote: Hi all, I found recently that even with a moderately-sized ontology, performing RepositoryConnection.clear() takes a very long time (tens of minutes for a few dozen classes with a few thousand instances). I am experiencing this with OWLIM-Lite 4.3 combined with openrdf-sesame 2.6.1. Have not tried this with OWLIM-SE. I understand that removing triples can be a time-consuming process with a forward-chaining strategy but in the case of clear(), should this not be much faster as it is certain that all triples can be removed? Cheers, johann ___ OWLIM-discussion mailing list OWLIM-discussion@ontotext.com http://ontotext.com/mailman/listinfo/owlim-discussion ___ OWLIM-discussion mailing list OWLIM-discussion@ontotext.com http://ontotext.com/mailman/listinfo/owlim-discussion
Re: [Owlim-discussion] JMX monitoring in OWLIM-SE 4.2
Hi Jerven,
No, you don't need the webapp. I meant warnings like Error registering so-
and-so mbean.
How exactly are you initialising and using owlim?
Regards,
Dimitar
On Wednesday 25 Jan 2012 17:15:55 Jerven Bolleman wrote:
Hi Dimitar,
No nothing shows up in the logs. Anything I should look out for?
By the way I do not use the sesame web app so if the mbean registering
depends on this somehow let me know.
Regards,
Jerven
On Jan 25, 2012, at 2:51 PM, Dimitar Toshev wrote:
Hi Jerven,
I also wasn't able to reproduce your problem, nor do I see anything wrong
with the code registering the mbeans. Could you please have a look at
the Sesame logs for any warnings about failing to register mbeans?
Regards,
Dimitar
On Wednesday 25 Jan 2012 15:12:46 Jerven Bolleman wrote:
Hi Barry,
I am just raising this issue again.
Sometimes the com.ontotext.AVLRepositoryManager bean does not seem to
register itself other times it does.
I get the instance via the PlatformMBeanServer which works most of the
time but sometimes there is nothing there.
final ObjectName avl = new
ObjectName(com.ontotext:type=AVLRepositoryManager,*);
for (final ObjectName instance :
ManagementFactory.getPlatformMBeanServer().queryNames(avl, null))
{
ManagementFactory.getPlatformMBeanServer().setAttribute(instance,
new Attribute(CollectionsStatisticsFlag,
true));
}
using Jconsole or visualvm mbean also show no ontotext beans in this
case. As this differs run to run could you have a look at the code you
use to register these beans to the MBeanServer?
Regards,
Jerven
On 10/07/2011 11:12 PM, Barry Bishop wrote:
Hi Jerven,
This might be a stupid question, but have you enabled JMX in Tomcat?
i.e. with kind of thing:
-Dcom.sun.management.jmxremote.port=8089
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
If you have then I will investigate further, because it is working at
the moment and I don't remember any issues being raised about this.
Have a great weekend,
barry
--
Barry Bishop
OWLIM Product Manager
Ontotext AD
Tel: +43 650 2000 237
email:barry.bis...@ontotext.com
www.ontotext.com
On 07/10/11 16:34, Jerven Bolleman wrote:
Dear Owlim developers,
Is it just me or have the JMX beans disappeared in release 4.2?
Both my statistics code and JVisualVM no longer see them.
Regards,
Jerven
___
OWLIM-discussion mailing list
OWLIM-discussion@ontotext.com
http://ontotext.com/mailman/listinfo/owlim-discussion
___
OWLIM-discussion mailing list
OWLIM-discussion@ontotext.com
http://ontotext.com/mailman/listinfo/owlim-discussion
Re: [Owlim-discussion] JMX monitoring in OWLIM-SE 4.2
Hi Dimitar,
I use a spring config that creates a ConfigRepository object which
extends OwlimSchemaRepository. This is a thin wrapper to inject
properties into the owlim code without using the system properties.
So basically by calling the OwlimSchemaRepository constructor.
Regards,
Jerven
public class ConfigRepository
extends OwlimSchemaRepository
{
private static final Logger log =
Logger.getInstance(ConfigRepository.class);
public ConfigRepository()
{
super();
super.setParameter(inferencer-threads,
String.valueOf(Runtime.getRuntime().availableProcessors()));
}
public String getDataLocation(String file)
{
return super.getDataDir().getName();
}
public void setDataLocation(String file)
{
super.setDataDir(new File(file));
}
public void setStorageFolder(String file)
{
super.setParameter(storage-folder, file);
}
public void setRepositoryType(String type)
{
super.setParameter(repository-type, clean(type));
}
public void setRuleset(String type)
{
super.setParameter(ruleset, clean(type));
}
public void setEntityIndexSize(String size)
{
super.setParameter(entity-index-size, clean(size));
}
etc... etc...
and
public void shutDown()
throws SailException
{
super.shutDown();
log.info(Repository shutting down.);
while (super.isShuttingDown())
{
try
{
Thread.sleep(1000);
} catch (InterruptedException e)
{
if (super.isShutDown())
{
log.info(Repository shut down!);
return;
}
}
log.info(Repository still shutting down.);
}
}
On 01/25/2012 04:57 PM, Dimitar Toshev wrote:
Hi Jerven,
No, you don't need the webapp. I meant warnings like Error registering so-
and-so mbean.
How exactly are you initialising and using owlim?
Regards,
Dimitar
On Wednesday 25 Jan 2012 17:15:55 Jerven Bolleman wrote:
Hi Dimitar,
No nothing shows up in the logs. Anything I should look out for?
By the way I do not use the sesame web app so if the mbean registering
depends on this somehow let me know.
Regards,
Jerven
On Jan 25, 2012, at 2:51 PM, Dimitar Toshev wrote:
Hi Jerven,
I also wasn't able to reproduce your problem, nor do I see anything wrong
with the code registering the mbeans. Could you please have a look at
the Sesame logs for any warnings about failing to register mbeans?
Regards,
Dimitar
On Wednesday 25 Jan 2012 15:12:46 Jerven Bolleman wrote:
Hi Barry,
I am just raising this issue again.
Sometimes the com.ontotext.AVLRepositoryManager bean does not seem to
register itself other times it does.
I get the instance via the PlatformMBeanServer which works most of the
time but sometimes there is nothing there.
final ObjectName avl = new
ObjectName(com.ontotext:type=AVLRepositoryManager,*);
for (final ObjectName instance :
ManagementFactory.getPlatformMBeanServer().queryNames(avl, null))
{
ManagementFactory.getPlatformMBeanServer().setAttribute(instance,
new Attribute(CollectionsStatisticsFlag,
true));
}
using Jconsole or visualvm mbean also show no ontotext beans in this
case. As this differs run to run could you have a look at the code you
use to register these beans to the MBeanServer?
Regards,
Jerven
On 10/07/2011 11:12 PM, Barry Bishop wrote:
Hi Jerven,
This might be a stupid question, but have you enabled JMX in Tomcat?
i.e. with kind of thing:
-Dcom.sun.management.jmxremote.port=8089
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
If you have then I will investigate further, because it is working at
the moment and I don't remember any issues being raised about this.
Have a great weekend,
barry
--
Barry Bishop
OWLIM Product Manager
Ontotext AD
Tel: +43 650 2000 237
email:barry.bis...@ontotext.com
www.ontotext.com
On 07/10/11 16:34, Jerven Bolleman wrote:
Dear Owlim developers,
Is it just me or have the JMX beans disappeared in release 4.2?
Both my statistics code and JVisualVM no longer see them.
Regards,
Jerven
___
OWLIM-discussion mailing list
OWLIM-discussion@ontotext.com
http://ontotext.com/mailman/listinfo/owlim-discussion
--
---
Jerven Bolleman
Re: [Owlim-discussion] JMX monitoring in OWLIM-SE 4.2
Hi Jerven, Dimitar,
This might be stating the obvious, but when OWLIM is deployed with
Tomcat (and the Sesame webapp) then it won't register anything until it
is loaded for the first time.
(During an OWLIM-Enterprise install, users have to click on something in
the workbench, e.g. 'query', which causes an exception, but it actually
loads the OWLIM jars for the first time. After this the replication
cluster bean can be seen)
@Jerven, is the bean missing even after OWLIM has been initialised and
loaded?
Best,
barry
On 25/01/12 16:57, Dimitar Toshev wrote:
Hi Jerven,
No, you don't need the webapp. I meant warnings like Error registering so-
and-so mbean.
How exactly are you initialising and using owlim?
Regards,
Dimitar
On Wednesday 25 Jan 2012 17:15:55 Jerven Bolleman wrote:
Hi Dimitar,
No nothing shows up in the logs. Anything I should look out for?
By the way I do not use the sesame web app so if the mbean registering
depends on this somehow let me know.
Regards,
Jerven
On Jan 25, 2012, at 2:51 PM, Dimitar Toshev wrote:
Hi Jerven,
I also wasn't able to reproduce your problem, nor do I see anything wrong
with the code registering the mbeans. Could you please have a look at
the Sesame logs for any warnings about failing to register mbeans?
Regards,
Dimitar
On Wednesday 25 Jan 2012 15:12:46 Jerven Bolleman wrote:
Hi Barry,
I am just raising this issue again.
Sometimes the com.ontotext.AVLRepositoryManager bean does not seem to
register itself other times it does.
I get the instance via the PlatformMBeanServer which works most of the
time but sometimes there is nothing there.
final ObjectName avl = new
ObjectName(com.ontotext:type=AVLRepositoryManager,*);
for (final ObjectName instance :
ManagementFactory.getPlatformMBeanServer().queryNames(avl, null))
{
ManagementFactory.getPlatformMBeanServer().setAttribute(instance,
new Attribute(CollectionsStatisticsFlag,
true));
}
using Jconsole or visualvm mbean also show no ontotext beans in this
case. As this differs run to run could you have a look at the code you
use to register these beans to the MBeanServer?
Regards,
Jerven
On 10/07/2011 11:12 PM, Barry Bishop wrote:
Hi Jerven,
This might be a stupid question, but have you enabled JMX in Tomcat?
i.e. with kind of thing:
-Dcom.sun.management.jmxremote.port=8089
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
If you have then I will investigate further, because it is working at
the moment and I don't remember any issues being raised about this.
Have a great weekend,
barry
--
Barry Bishop
OWLIM Product Manager
Ontotext AD
Tel: +43 650 2000 237
email:barry.bis...@ontotext.com
www.ontotext.com
On 07/10/11 16:34, Jerven Bolleman wrote:
Dear Owlim developers,
Is it just me or have the JMX beans disappeared in release 4.2?
Both my statistics code and JVisualVM no longer see them.
Regards,
Jerven
___
OWLIM-discussion mailing list
OWLIM-discussion@ontotext.com
http://ontotext.com/mailman/listinfo/owlim-discussion
___
OWLIM-discussion mailing list
OWLIM-discussion@ontotext.com
http://ontotext.com/mailman/listinfo/owlim-discussion
Re: [Owlim-discussion] Problem with jdk1.7.0_02
Hi Johann, We do not generally test with Java 1.7 and hence do not officially support it. However, if you are having trouble then we would very much like to hear about it. Best, barry On 25/01/12 12:38, Johann Petrak wrote: Is there any known problem when using Sesame/OWLIM-Lite on a 32 bit Linux system with JDK 1.7.0_02? I am seeing a hanging condition which does not occur with Java 1.6.x in my app which embeds OWLIM-Lite and thought I ask about this before digging deeper. Cheers, johann ___ OWLIM-discussion mailing list OWLIM-discussion@ontotext.com http://ontotext.com/mailman/listinfo/owlim-discussion ___ OWLIM-discussion mailing list OWLIM-discussion@ontotext.com http://ontotext.com/mailman/listinfo/owlim-discussion
Re: [Owlim-discussion] JMX monitoring in OWLIM-SE 4.2
Hi Barry,
Well lets put it this way after inserting a few million statements into the an
OWLIM repository the beans is not visible. Nor is it after a few queries
against the repository.
Does it depend on a specific class being loaded? I am looking for the
com.ontotext:type=AVLRepositoryManager so that I can plot cache hit rates as I
am loading data.
Regards,
Jerven
On Jan 25, 2012, at 5:21 PM, Barry Bishop wrote:
Hi Jerven, Dimitar,
This might be stating the obvious, but when OWLIM is deployed with Tomcat
(and the Sesame webapp) then it won't register anything until it is loaded
for the first time.
(During an OWLIM-Enterprise install, users have to click on something in the
workbench, e.g. 'query', which causes an exception, but it actually loads the
OWLIM jars for the first time. After this the replication cluster bean can be
seen)
@Jerven, is the bean missing even after OWLIM has been initialised and loaded?
Best,
barry
On 25/01/12 16:57, Dimitar Toshev wrote:
Hi Jerven,
No, you don't need the webapp. I meant warnings like Error registering so-
and-so mbean.
How exactly are you initialising and using owlim?
Regards,
Dimitar
On Wednesday 25 Jan 2012 17:15:55 Jerven Bolleman wrote:
Hi Dimitar,
No nothing shows up in the logs. Anything I should look out for?
By the way I do not use the sesame web app so if the mbean registering
depends on this somehow let me know.
Regards,
Jerven
On Jan 25, 2012, at 2:51 PM, Dimitar Toshev wrote:
Hi Jerven,
I also wasn't able to reproduce your problem, nor do I see anything wrong
with the code registering the mbeans. Could you please have a look at
the Sesame logs for any warnings about failing to register mbeans?
Regards,
Dimitar
On Wednesday 25 Jan 2012 15:12:46 Jerven Bolleman wrote:
Hi Barry,
I am just raising this issue again.
Sometimes the com.ontotext.AVLRepositoryManager bean does not seem to
register itself other times it does.
I get the instance via the PlatformMBeanServer which works most of the
time but sometimes there is nothing there.
final ObjectName avl = new
ObjectName(com.ontotext:type=AVLRepositoryManager,*);
for (final ObjectName instance :
ManagementFactory.getPlatformMBeanServer().queryNames(avl, null))
{
ManagementFactory.getPlatformMBeanServer().setAttribute(instance,
new Attribute(CollectionsStatisticsFlag,
true));
}
using Jconsole or visualvm mbean also show no ontotext beans in this
case. As this differs run to run could you have a look at the code you
use to register these beans to the MBeanServer?
Regards,
Jerven
On 10/07/2011 11:12 PM, Barry Bishop wrote:
Hi Jerven,
This might be a stupid question, but have you enabled JMX in Tomcat?
i.e. with kind of thing:
-Dcom.sun.management.jmxremote.port=8089
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
If you have then I will investigate further, because it is working at
the moment and I don't remember any issues being raised about this.
Have a great weekend,
barry
--
Barry Bishop
OWLIM Product Manager
Ontotext AD
Tel: +43 650 2000 237
email:barry.bis...@ontotext.com
www.ontotext.com
On 07/10/11 16:34, Jerven Bolleman wrote:
Dear Owlim developers,
Is it just me or have the JMX beans disappeared in release 4.2?
Both my statistics code and JVisualVM no longer see them.
Regards,
Jerven
___
OWLIM-discussion mailing list
OWLIM-discussion@ontotext.com
http://ontotext.com/mailman/listinfo/owlim-discussion
___
OWLIM-discussion mailing list
OWLIM-discussion@ontotext.com
http://ontotext.com/mailman/listinfo/owlim-discussion
Re: [Owlim-discussion] JMX monitoring in OWLIM-SE 4.2
Hi Barry,
I think that in the code path that I use the following method may not be called.
public class com.ontotext.trree.big.AVLRepositoryMBeanFactory
public java.util.List createAndRegisterMBeansFor(com.ontotext.trree.big.h)
i.e. is there a guarantee that this method is called when constructing an
OwlimSchemaRepository?
How can I make sure that this is called and that the mbeans are registered in
the platformMBeanServer?
Regards,
Jerven
On Jan 25, 2012, at 5:30 PM, Jerven Bolleman wrote:
Hi Barry,
Well lets put it this way after inserting a few million statements into the
an OWLIM repository the beans is not visible. Nor is it after a few queries
against the repository.
Does it depend on a specific class being loaded? I am looking for the
com.ontotext:type=AVLRepositoryManager so that I can plot cache hit rates as
I am loading data.
Regards,
Jerven
On Jan 25, 2012, at 5:21 PM, Barry Bishop wrote:
Hi Jerven, Dimitar,
This might be stating the obvious, but when OWLIM is deployed with Tomcat
(and the Sesame webapp) then it won't register anything until it is loaded
for the first time.
(During an OWLIM-Enterprise install, users have to click on something in the
workbench, e.g. 'query', which causes an exception, but it actually loads
the OWLIM jars for the first time. After this the replication cluster bean
can be seen)
@Jerven, is the bean missing even after OWLIM has been initialised and
loaded?
Best,
barry
On 25/01/12 16:57, Dimitar Toshev wrote:
Hi Jerven,
No, you don't need the webapp. I meant warnings like Error registering so-
and-so mbean.
How exactly are you initialising and using owlim?
Regards,
Dimitar
On Wednesday 25 Jan 2012 17:15:55 Jerven Bolleman wrote:
Hi Dimitar,
No nothing shows up in the logs. Anything I should look out for?
By the way I do not use the sesame web app so if the mbean registering
depends on this somehow let me know.
Regards,
Jerven
On Jan 25, 2012, at 2:51 PM, Dimitar Toshev wrote:
Hi Jerven,
I also wasn't able to reproduce your problem, nor do I see anything wrong
with the code registering the mbeans. Could you please have a look at
the Sesame logs for any warnings about failing to register mbeans?
Regards,
Dimitar
On Wednesday 25 Jan 2012 15:12:46 Jerven Bolleman wrote:
Hi Barry,
I am just raising this issue again.
Sometimes the com.ontotext.AVLRepositoryManager bean does not seem to
register itself other times it does.
I get the instance via the PlatformMBeanServer which works most of the
time but sometimes there is nothing there.
final ObjectName avl = new
ObjectName(com.ontotext:type=AVLRepositoryManager,*);
for (final ObjectName instance :
ManagementFactory.getPlatformMBeanServer().queryNames(avl, null))
{
ManagementFactory.getPlatformMBeanServer().setAttribute(instance,
new Attribute(CollectionsStatisticsFlag,
true));
}
using Jconsole or visualvm mbean also show no ontotext beans in this
case. As this differs run to run could you have a look at the code you
use to register these beans to the MBeanServer?
Regards,
Jerven
On 10/07/2011 11:12 PM, Barry Bishop wrote:
Hi Jerven,
This might be a stupid question, but have you enabled JMX in Tomcat?
i.e. with kind of thing:
-Dcom.sun.management.jmxremote.port=8089
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
If you have then I will investigate further, because it is working at
the moment and I don't remember any issues being raised about this.
Have a great weekend,
barry
--
Barry Bishop
OWLIM Product Manager
Ontotext AD
Tel: +43 650 2000 237
email:barry.bis...@ontotext.com
www.ontotext.com
On 07/10/11 16:34, Jerven Bolleman wrote:
Dear Owlim developers,
Is it just me or have the JMX beans disappeared in release 4.2?
Both my statistics code and JVisualVM no longer see them.
Regards,
Jerven
___
OWLIM-discussion mailing list
OWLIM-discussion@ontotext.com
http://ontotext.com/mailman/listinfo/owlim-discussion
___
OWLIM-discussion mailing list
OWLIM-discussion@ontotext.com
http://ontotext.com/mailman/listinfo/owlim-discussion
Re: [Owlim-discussion] JMX monitoring in OWLIM-SE 4.2
Hi Jerven,
If this method isn't called, this points to a problem with your classpath
configuration. There should be a file called
META-INF/services/com.ontotext.trree.mbeans.MBeanFactory
on your classpath - most likely in the owlim jar.
Regards,
Dimitar
On Wednesday 25 Jan 2012 19:11:32 Jerven Bolleman wrote:
Hi Barry,
I think that in the code path that I use the following method may not be
called.
public class com.ontotext.trree.big.AVLRepositoryMBeanFactory
public java.util.List
createAndRegisterMBeansFor(com.ontotext.trree.big.h)
i.e. is there a guarantee that this method is called when constructing an
OwlimSchemaRepository?
How can I make sure that this is called and that the mbeans are registered
in the platformMBeanServer?
Regards,
Jerven
On Jan 25, 2012, at 5:30 PM, Jerven Bolleman wrote:
Hi Barry,
Well lets put it this way after inserting a few million statements into
the an OWLIM repository the beans is not visible. Nor is it after a few
queries against the repository. Does it depend on a specific class being
loaded? I am looking for the com.ontotext:type=AVLRepositoryManager so
that I can plot cache hit rates as I am loading data.
Regards,
Jerven
On Jan 25, 2012, at 5:21 PM, Barry Bishop wrote:
Hi Jerven, Dimitar,
This might be stating the obvious, but when OWLIM is deployed with
Tomcat (and the Sesame webapp) then it won't register anything until it
is loaded for the first time.
(During an OWLIM-Enterprise install, users have to click on something in
the workbench, e.g. 'query', which causes an exception, but it actually
loads the OWLIM jars for the first time. After this the replication
cluster bean can be seen)
@Jerven, is the bean missing even after OWLIM has been initialised and
loaded?
Best,
barry
On 25/01/12 16:57, Dimitar Toshev wrote:
Hi Jerven,
No, you don't need the webapp. I meant warnings like Error registering
so- and-so mbean.
How exactly are you initialising and using owlim?
Regards,
Dimitar
On Wednesday 25 Jan 2012 17:15:55 Jerven Bolleman wrote:
Hi Dimitar,
No nothing shows up in the logs. Anything I should look out for?
By the way I do not use the sesame web app so if the mbean registering
depends on this somehow let me know.
Regards,
Jerven
On Jan 25, 2012, at 2:51 PM, Dimitar Toshev wrote:
Hi Jerven,
I also wasn't able to reproduce your problem, nor do I see anything
wrong with the code registering the mbeans. Could you please have a
look at the Sesame logs for any warnings about failing to register
mbeans?
Regards,
Dimitar
On Wednesday 25 Jan 2012 15:12:46 Jerven Bolleman wrote:
Hi Barry,
I am just raising this issue again.
Sometimes the com.ontotext.AVLRepositoryManager bean does not seem
to register itself other times it does.
I get the instance via the PlatformMBeanServer which works most of
the time but sometimes there is nothing there.
final ObjectName avl = new
ObjectName(com.ontotext:type=AVLRepositoryManager,*);
for (final ObjectName instance :
ManagementFactory.getPlatformMBeanServer().queryNames(avl, null))
{
ManagementFactory.getPlatformMBeanServer().setAttribute(instance,
new
Attribute(CollectionsStatisticsFlag, true));
}
using Jconsole or visualvm mbean also show no ontotext beans in this
case. As this differs run to run could you have a look at the code
you use to register these beans to the MBeanServer?
Regards,
Jerven
On 10/07/2011 11:12 PM, Barry Bishop wrote:
Hi Jerven,
This might be a stupid question, but have you enabled JMX in
Tomcat? i.e. with kind of thing:
-Dcom.sun.management.jmxremote.port=8089
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
If you have then I will investigate further, because it is working
at the moment and I don't remember any issues being raised about
this.
Have a great weekend,
barry
--
Barry Bishop
OWLIM Product Manager
Ontotext AD
Tel: +43 650 2000 237
email:barry.bis...@ontotext.com
www.ontotext.com
On 07/10/11 16:34, Jerven Bolleman wrote:
Dear Owlim developers,
Is it just me or have the JMX beans disappeared in release 4.2?
Both my statistics code and JVisualVM no longer see them.
Regards,
Jerven
___
OWLIM-discussion mailing list
OWLIM-discussion@ontotext.com
http://ontotext.com/mailman/listinfo/owlim-discussion
___
OWLIM-discussion mailing list
OWLIM-discussion@ontotext.com
http://ontotext.com/mailman/listinfo/owlim-discussion
Re: [Owlim-discussion] JMX monitoring in OWLIM-SE 4.2
Hi Ditmar,
They are sometimes available although today I have not seen them :(.
OwlimSchemaRepository.initialize() completes succesfully
Spring in my config adds two beans to the platform mbean server but when
removing it the Owlim mbeans do not appear.
Regards,
Jerven
On Jan 25, 2012, at 6:08 PM, Dimitar Toshev wrote:
Hi Jerven,
Everything seems fine. Can you reproduce the problem reliably - i.e. are the
MBeans missing always for a given configuration or only sometimes? They
should
be present after OwlimSchemaRepository.initialize() completes.
Also, I'm not familiar with Spring and this might sound stupid, but is it
possible that Spring somehow messes with the PlatformMBeanServer?
On Wednesday 25 Jan 2012 18:12:45 Jerven Bolleman wrote:
Hi Dimitar,
I use a spring config that creates a ConfigRepository object which
extends OwlimSchemaRepository. This is a thin wrapper to inject
properties into the owlim code without using the system properties.
So basically by calling the OwlimSchemaRepository constructor.
Regards,
Jerven
public class ConfigRepository
extends OwlimSchemaRepository
{
private static final Logger log =
Logger.getInstance(ConfigRepository.class);
public ConfigRepository()
{
super();
super.setParameter(inferencer-threads,
String.valueOf(Runtime.getRuntime().availableProcessors()));
}
public String getDataLocation(String file)
{
return super.getDataDir().getName();
}
public void setDataLocation(String file)
{
super.setDataDir(new File(file));
}
public void setStorageFolder(String file)
{
super.setParameter(storage-folder, file);
}
public void setRepositoryType(String type)
{
super.setParameter(repository-type, clean(type));
}
public void setRuleset(String type)
{
super.setParameter(ruleset, clean(type));
}
public void setEntityIndexSize(String size)
{
super.setParameter(entity-index-size, clean(size));
}
etc... etc...
and
public void shutDown()
throws SailException
{
super.shutDown();
log.info(Repository shutting down.);
while (super.isShuttingDown())
{
try
{
Thread.sleep(1000);
} catch (InterruptedException e)
{
if (super.isShutDown())
{
log.info(Repository shut down!);
return;
}
}
log.info(Repository still shutting down.);
}
}
On 01/25/2012 04:57 PM, Dimitar Toshev wrote:
Hi Jerven,
No, you don't need the webapp. I meant warnings like Error registering
so- and-so mbean.
How exactly are you initialising and using owlim?
Regards,
Dimitar
On Wednesday 25 Jan 2012 17:15:55 Jerven Bolleman wrote:
Hi Dimitar,
No nothing shows up in the logs. Anything I should look out for?
By the way I do not use the sesame web app so if the mbean registering
depends on this somehow let me know.
Regards,
Jerven
On Jan 25, 2012, at 2:51 PM, Dimitar Toshev wrote:
Hi Jerven,
I also wasn't able to reproduce your problem, nor do I see anything
wrong with the code registering the mbeans. Could you please have a
look at the Sesame logs for any warnings about failing to register
mbeans?
Regards,
Dimitar
On Wednesday 25 Jan 2012 15:12:46 Jerven Bolleman wrote:
Hi Barry,
I am just raising this issue again.
Sometimes the com.ontotext.AVLRepositoryManager bean does not seem to
register itself other times it does.
I get the instance via the PlatformMBeanServer which works most of the
time but sometimes there is nothing there.
final ObjectName avl = new
ObjectName(com.ontotext:type=AVLRepositoryManager,*);
for (final ObjectName instance :
ManagementFactory.getPlatformMBeanServer().queryNames(avl, null))
{
ManagementFactory.getPlatformMBeanServer().setAttribute(instance,
new Attribute(CollectionsStatisticsFlag,
true));
}
using Jconsole or visualvm mbean also show no ontotext beans in this
case. As this differs run to run could you have a look at the code you
use to register these beans to the MBeanServer?
Regards,
Jerven
On 10/07/2011 11:12 PM, Barry Bishop wrote:
Hi Jerven,
This might be a stupid question, but have you enabled JMX in Tomcat?
i.e. with kind of thing:
-Dcom.sun.management.jmxremote.port=8089
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
If you have then I
Re: [Owlim-discussion] Problem with jdk1.7.0_02
Thank you for that information! As I already mentioned elsewhere, the problem appears when using OWLIM-Lite with Sesame 2.6.1 but went away with Sesame 2.6.3 so this seems to be a Sesame problem really. Therefore I would also be interested in what the official statement about compatibility of OWLIM with Sesame versions which are released after the release of OWLIM versions is ... Java 1.7 was not really an issue so far but it seems now to be the recommended default version on the Oracle download page so I expect it will become important to support it soon. Cheers, johann On 2012-01-25 17:27, Barry Bishop wrote: Hi Johann, We do not generally test with Java 1.7 and hence do not officially support it. However, if you are having trouble then we would very much like to hear about it. Best, barry On 25/01/12 12:38, Johann Petrak wrote: Is there any known problem when using Sesame/OWLIM-Lite on a 32 bit Linux system with JDK 1.7.0_02? I am seeing a hanging condition which does not occur with Java 1.6.x in my app which embeds OWLIM-Lite and thought I ask about this before digging deeper. Cheers, johann ___ OWLIM-discussion mailing list OWLIM-discussion@ontotext.com http://ontotext.com/mailman/listinfo/owlim-discussion ___ OWLIM-discussion mailing list OWLIM-discussion@ontotext.com http://ontotext.com/mailman/listinfo/owlim-discussion
[Owlim-discussion] Rép. : Re: RepositoryConnection.clear() very slow
Hi, I don't know if this is relevant or not, but doing some tests with OWLIM-Lite, and sometimes having to delete one context in the repository, I noticed that using the Sesame work-bench's clear option on a context was much slower then executing a SPARQL-update query to delete all the triples from that context (which finally does erase the context itself). I have no idea if it was just by chance, if it was because of my configuration or rule-set...but I did have this case more than once. Fabian John del Corral jdcor...@iri.columbia.edu 25.01.2012 16:06 Johann, we experience this problem also with OWLIM-Lite. Barry Norton at a Meetup in NYC recommended going to OWLIM-SE, if you can get a copy from Ontotext. We have our copy but have not tested it yet. John - Original Message - From: Johann Petrak johann.pet...@jpetrak.com To: owlim-discussion@ontotext.com Sent: Wednesday, January 25, 2012 6:34:06 AM Subject: Re: [Owlim-discussion] RepositoryConnection.clear() very slow Am I the only one who experiences this problem or thinks that it is indeed a problem? cheers, johann On 2012-01-16 17:54, Johann Petrak wrote: Hi all, I found recently that even with a moderately-sized ontology, performing RepositoryConnection.clear() takes a very long time (tens of minutes for a few dozen classes with a few thousand instances). I am experiencing this with OWLIM-Lite 4.3 combined with openrdf-sesame 2.6.1. Have not tried this with OWLIM-SE. I understand that removing triples can be a time-consuming process with a forward-chaining strategy but in the case of clear(), should this not be much faster as it is certain that all triples can be removed? Cheers, johann ___ OWLIM-discussion mailing list OWLIM-discussion@ontotext.com http://ontotext.com/mailman/listinfo/owlim-discussion ___ OWLIM-discussion mailing list OWLIM-discussion@ontotext.com http://ontotext.com/mailman/listinfo/owlim-discussion ___ OWLIM-discussion mailing list OWLIM-discussion@ontotext.com http://ontotext.com/mailman/listinfo/owlim-discussion
