Search Mailing List Archives
[protege-dev] Badly behaving Listener
matthew.horridge at stanford.edu
Tue Feb 18 10:02:16 PST 2014
It looks like there is something else going on…. most of the error messages relate to plugins that are normally “well behaved”. If something else crashed before shutdown and then prevented other plugins cleaning up properly you would get the catalog of errors that you got. It’s hard to tell what this is from your log messages. Do these error messages always appear?
On 18 Feb 2014, at 09:48, Timothy Redmond <tredmond at stanford.edu> wrote:
> On 02/18/2014 09:26 AM, Andreas Harth wrote:
>> I get the error message attached with  on a Debian Linux
>> machine. I have found via Google, however, I cannot access the
>> relevant issue in the tracker (I presume the issue is #1642 ).
> Is this log a perfect match for your error message? My suspicion is that it is approximate. It would be good to see your logs where you had the error. You can find these in the directory ~/.Protege/logs. It will probably then be easy to diagnose.
> These errors are usually not too serious - they indicate that some plugin did not clean itself up correctly. Though for the log that you showed there might have been something else going on because there were a lot of error messages.
>> Is there any way to figure out what's going on? I'd like to
>> use Protege in a practical exercise for teaching.
>>  http://protege.stanford.edu/download/protege/4.3/zip/protege-4.3.0-304.zip
>>  https://bmir-gforge.stanford.edu/gf/download/trackeritem/4247/1642/second-console-output.txt
>>  https://bmir-gforge.stanford.edu/gf/project/protege/tracker/?action=TrackerItemEdit&tracker_item_id=1642
>> protege-dev mailing list
>> protege-dev at lists.stanford.edu
> protege-dev mailing list
> protege-dev at lists.stanford.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the protege-dev