Search Mailing List Archives

Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-discussion] RE : problems classifying OWL-DL ontology containing import command

Ammar MECHOUCHE mechov at
Wed Jul 25 06:50:39 PDT 2007

Hi Alexandre,
 I am not sure, but try to increase the  Xmx value, try for example the following value -Xmx1024M.
 Alexandre Vidal <vidal at> a écrit : Hi. Could someone help me?

I'm testing the classification task on two OWL-DL ontologies:

I submitted both ontologies to validator, and they are Ok.

The ontology (1) does not import any ontology, while the ontology (2) does.

I'm using Eclipse and Protégé-OWL API with this simple code:

try {
 JenaOWLModel gridOwlModel =

       ReasonerManager reasonerManager = ReasonerManager.getInstance();

       ProtegeOWLReasoner reasoner = reasonerManager.getReasoner(gridOwlModel);
 // Set the reasoner URL and test the connection.
 if (reasoner.isConnected()) {
     DIGReasonerIdentity reasonerIdentity = reasoner.getIdentity();
     System.out.println("Connected to " + reasonerIdentity.getName() + " " +

     // We can classify the whole ontology, which will put the
     // inferred class hierarchy information directly into the
Protégé-OWL model.
     System.out.println("Classifying taxonomy...");
     System.out.println("...Classified taxonomy!");
 else {
                System.out.println("Reasoner not connected!");
} catch (Exception e) {
 // TODO Auto-generated catch block

I have no problem to classify the former ontology;
However, when I try to classify the later, I get the error messages
below, though I've been succeed before classifying this same ontology.
What could cause such errors?
vidal at vidal-laptop:/home/pos/aplicativos/pellet-1.4-RC1$  sh

PelletDIGServer Version 1.4-RC1 (November 7 2006)
Port: 8081
 WARN [HttpConnection] - POST / HTTP/1.1
java.lang.OutOfMemoryError: Java heap space     // error on Pellet execution
Eclipse error Message:
JVM terminated. Exit code=1
-jar /home/pub/eclipse3.2//startup.jar
-os linux
-ws gtk
-arch x86
-launcher /home/pub/eclipse3.2//eclipse
-name Eclipse
-showsplash 600
-exitdata 46000a
-data /home/vidal/Workspace
-vm /usr/bin/java
-jar /home/pub/eclipse3.2//startup.jar


protege-discussion mailing list
protege-discussion at

Instructions for unsubscribing: 

 Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the protege-discussion mailing list