[protege-discussion] installation problem, cannot load the list of ontologies, cannot login

[Tania Tudorache]

Michal,

I'm developing WebProtege using also Ubuntu and Tomcat 5.5 and there is 
no problem with the configuration, it runs well.

It seems that this is a file access problem. The log kind of already 
says what the problem is:

"INFO: Illegal access: this web application instance has been stopped 
already.  Could not load logging.properties..."

Looks like tomcat tries to load the logging.properties from:
/var/lib/tomcat5.5/webapps/webprotege/WEB-INF/classes/logging.properties

I am not sure why it tries to load it from the classes folder..

I'm not an expert in tomcat, but it seems that you need to configure the 
tomcat policy file. Here is the solution for a similar case:

http://aleph-null.tv/article/20080327-0118-335.xml/Tomcat-5.5-On-Debian:-AccessControlException-for-logging.properties

Another thing that was suspicious in one of your log files was:

May 19, 2009 7:37:45 PM 
edu.stanford.bmir.protege.web.server.ProjectManager getServer
SEVERE: Could not connect to server: localhost

This means that you did not start the Protege server, or that WebProtege 
could not connect to it. Make sure that the Protege server is running, 
and that you can connect to it from the Protege rich client, using u/p: 
webprotege/webprotege

If you still have problems, please send also the protege.log files from 
tomcat/logs.

I hope that the tomcat policy file will fix the problem.

Tania



Michal Trna wrote:
> Hello Jennifer,
>
> Jennifer Vendetti escribió:
>> Hello Michal,
>>
>> Michal Trna wrote:
>>   
>>> I have installed Webprotege according to instructions [1] on Ubuntu 
>>> machine in these two configurations:
>>> Tomcat 5.5, Protege 3.4 release, WebProtege 0.5 alpha, build 102.
>>> Tomcat 6, Protege 3.4 release, WebProtege 0.5 alpha, build 102.
>>>     
>>
>> We have not tested WebProtege with Tomcat 6.  Only with 5.5.
>>
>>   
>>> To both of them it is possible to connect through Protege Client. Both 
>>> also fail when I try to connect via WebProtege. For both cases, 
>>> WebProtege screen shows all the control elements like the frames and 
>>> buttons, but the list of ontologies is empty and it is not possible to 
>>> log in.
>>>
>>> My log files look like:
>>> Tomcat 5.5, catalina.log:
>>> May 19, 2009 7:29:19 PM org.apache.commons.modeler.Registry 
>>> registerComponent
>>> SEVERE: Error registering 
>>> Catalina:type=Valve,name=StandardContextValve,path=/webprotege,host=localhost 
>>>
>>> javax.management.MBeanException: Cannot instantiate ModelMBean of 
>>> class org.apache.commons.modeler.BaseModelMBean
>>>    at 
>>> org.apache.commons.modeler.ManagedBean.createMBean(ManagedBean.java:385)
>>>    at 
>>> org.apache.commons.modeler.Registry.registerComponent(Registry.java:835)
>>> ...
>>> Caused by: java.security.AccessControlException: access denied 
>>> (java.io.FilePermission 
>>> /var/lib/tomcat5.5/webapps/webprotege/WEB-INF/classes/logging.properties 
>>> read)
>>>
>>>     
>>
>> I notice in the exception above that you are getting an access denied error:
>>
>> java.io.FilePermission 
>> /var/lib/tomcat5.5/webapps/webprotege/WEB-INF/classes/logging.properties 
>> read
>>
>> Did you check that you have the proper access permissions for this file?
>>   
> the file originaly didn't exist. The error didn't dissapear after I 
> have created the file and set read/write permissions to everybody to 
> everything in the webprotege folder in webapps.
> (In my windows version, the file doesn't exist either and there is no 
> problem)
>> Jennifer
>> _______________________________________________
>> protege-discussion mailing list
>> protege-discussion at lists.stanford.edu
>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>
>> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 
>>
>>
>>   
> Thanks,
> Michal
> ------------------------------------------------------------------------
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 
>