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] Help : Protege 4 client server (Bleeding edge version)

Timothy Redmond tredmond at stanford.edu
Mon Nov 5 15:39:22 PST 2012


I am running 32-bit windows in a virtualbox and have replicated a 
problem with your symptoms.   The windows error messages are aweful!  I 
will have to see if there is anything that I can do about this as I 
refine this process.

I also realized that there is an important step that is not yet 
documented - to be able to interact with the server you need to install 
the Protege client jars.  When the Protege OWL server is released, these 
will be included in the Protege distribution.  In the meantime, I have 
attached two jar files that you can put in the Protege plugins directory.

First do an svn update on the server directory - I have fixed a couple 
of typos.  Second, I have determined that if the server has been 
deployed then if the deploy target is called it will fail with exactly 
the "exec returned: 8" error message.  The solution is to run "ant 
undeploy" to clean up and then run "ant deploy" to put the service back.

I hope that this fixes the problem for you but if it doesn't I will soon 
write a .bat script that will let you manually start running the 
server.  This script would not resume running on a reboot but it will 
allow you to proceed even if my scripts to configure the apache daemon 
don't work.

You can monitor if the OWL server has been installed by looking at the 
Services application.  You can find this by going to the "Start" menu 
and searching for "services".  When you run this program it will show 
all the installed services and the OWL Server will show up as 
"OWLServer".  This is shown in the diagram that I have included below.

-Timothy.






On 11/1/12 12:27 PM, Timothy Redmond wrote:
>
> I am sorry for the delay on looking at this.  I am trying to get my 
> hands on a 32-bit windows image for testing.  But I did have one 
> thought.  Make sure that the memory.mb setting in the local.properties 
> file is less than 2048 because a 32-bit windows process can't handle 
> more than 2 gig of memory.  When I was testing this before I noticed 
> that some of the errors under windows are a bit obscure.
>
> -Timothy
>
>
> On 10/31/12 5:04 AM, Dinbandhu Laxman Gauda wrote:
>> The below issue  is resolved by fixing this line in build.xml file.
>>
>>
>> <target name="install.windows32.files" depends="jar, install.noarch.files" if="is.windows32">
>>      	<!--copy file="${service64.src}"  tofile="${service}"/>   -->
>> 	<copy file="${service32.src}"  tofile="${service}"/>
>> 	</target>
>>
>> But I am seeing other issues like..  Attached is a ant log file..
>>
>> BUILD FAILED
>> D:\work\workspace\protege-server-4\build.xml:35: The following error occurred while executing this line:
>> D:\work\workspace\protege-server-4\org.protege.owl.server.deploy\build.xml:310: exec returned: 8
>> 	at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:646)
>> 	at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:672)
>> 	at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:498)
>> 	at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>> 	at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> 	at java.lang.reflect.Method.invoke(Method.java:597)
>> 	at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>> 	at org.apache.tools.ant.Task.perform(Task.java:348)
>> 	at org.apache.tools.ant.Target.execute(Target.java:392)
>> 	at org.apache.tools.ant.Target.performTasks(Target.java:413)
>> 	at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>> 	at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
>> 	at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>> 	at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
>> 	at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>> 	at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> 	at java.lang.reflect.Method.invoke(Method.java:597)
>> 	at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>> 	at org.apache.tools.ant.Task.perform(Task.java:348)
>> 	at org.apache.tools.ant.Target.execute(Target.java:392)
>> 	at org.apache.tools.ant.Target.performTasks(Target.java:413)
>> 	at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>> 	at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
>> 	at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>> 	at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>> 	at org.apache.tools.ant.Main.runBuild(Main.java:811)
>> 	at org.apache.tools.ant.Main.startAnt(Main.java:217)
>> 	at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
>> 	at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
>>
>>
>>
>> -----Original Message-----
>> From: Dinbandhu Laxman Gauda
>> Sent: Wednesday, October 31, 2012 4:38 PM
>> To: 'protege-discussion at lists.stanford.edu'
>> Subject: RE: [protege-discussion] Help : Protege 4 client server (Bleeding edge version)
>>
>> Hi,
>>
>> I am not able to deploy Protégé 4 server  on Windows 7 (32 bit) even though exe is installed for x32 bit.
>>
>> Similar issue is with clean.full as well
>>
>> Attached is a log from ant build.
>>
>> Thanks
>> -Dinu
>>
>> -----Original Message-----
>> From:protege-discussion-bounces at lists.stanford.edu  [mailto:protege-discussion-bounces at lists.stanford.edu] On Behalf Of Timothy Redmond
>> Sent: Wednesday, 31 October, 2012 12:52
>> To:protege-discussion at lists.stanford.edu
>> Subject: Re: [protege-discussion] Help : Protege 4 client server (Bleeding edge version)
>>
>> On 10/30/2012 10:08 PM, Dinbandhu Laxman Gauda wrote:
>>> Hi Timothy,
>>>
>>> Attached is a log text file.  I looked at org.protege.owl.server.jar
>>> file and looks like SetMetaprojectDataDir.class file is missing. I
>>> infact .java file is also missing from
>>> org.protege.owl.server\src\main\java\org\protege\owl\server\command
>>> folder
>>>
>>> Thanks
>>> -Dinu
>>>
>> Thanks very much for the help.  This problem was completely my mistake - actually I made several mistakes to make this happen.  It has been broken for a bit and I didn't notice.  If you update and try again I think that it will work.  (I just ran the installer in both linux and
>> windows.)
>>
>> One of the things that I changed to fix this was to change the ant clean target and add a clean.full target.  The clean target now just cleans up the built artifacts in the checked out directories.  The clean.full target will also clean up the Protege OWL server files that have been installed in the system directories.
>>
>> You have also helped me see that I can simplify this process when the server is ready for release.  The current version involves two projects (the server project and the server deployer project) that get built.  If anything goes wrong in either one then the build fails.  But really all we need to distribute is the deployer project together with a built copy of the server.
>>
>> -Timothy
>>
>>
>> _______________________________________________
>> 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
>>
>> **************** CAUTION - Disclaimer *****************
>> This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
>> for the use of the addressee(s). If you are not the intended recipient, please
>> notify the sender by e-mail and delete the original message. Further, you are not
>> to copy, disclose, or distribute this e-mail or its contents to any other person and
>> any such actions are unlawful. This e-mail may contain viruses. Infosys has taken
>> every reasonable precaution to minimize this risk, but is not liable for any damage
>> you may sustain as a result of any virus in this e-mail. You should carry out your
>> own virus checks before opening the e-mail or attachment. Infosys reserves the
>> right to monitor and review the content of all messages sent to or from this e-mail
>> address. Messages sent to or from this e-mail address may be stored on the
>> Infosys e-mail system.
>> ***INFOSYS******** End of Disclaimer ********INFOSYS***
>>
>>
>> _______________________________________________
>> 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
>
>
>
> _______________________________________________
> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.stanford.edu/pipermail/protege-discussion/attachments/20121105/40305f8e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: eabajdbe.png
Type: image/png
Size: 281213 bytes
Desc: not available
URL: <http://mailman.stanford.edu/pipermail/protege-discussion/attachments/20121105/40305f8e/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: org.protege.owl.server.jar
Type: application/java-archive
Size: 2036748 bytes
Desc: not available
URL: <http://mailman.stanford.edu/pipermail/protege-discussion/attachments/20121105/40305f8e/attachment-0002.jar>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: org.protege.editor.owl.client.jar
Type: application/java-archive
Size: 60218 bytes
Desc: not available
URL: <http://mailman.stanford.edu/pipermail/protege-discussion/attachments/20121105/40305f8e/attachment-0003.jar>


More information about the protege-discussion mailing list