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
Sat Nov 3 04:42:58 PDT 2012


I apologize that this is taking a bit.  I very much appeciate the test 
of the code.

At the end of the day today I loaded a virtual copy of Windows 7 
(32-bit) so I should be able to test it on Monday.  It also occurred to 
me that I could test the 32-bit code on a 64-bit machine and see if it 
works there. I should be able to test that sooner.

-Timothy


On 11/03/2012 03:09 AM, Dinbandhu Laxman Gauda wrote:
> Hi,
>
> I tried to set the Jmx parameter to smaller between 1000- 2000. This change does not seems to have any impact. This is the error I am seeing in error log  while trying to start the service..
>
> owlserver-stderr.2012-11-03:
> 2012-11-03 15:33:23 Commons Daemon procrun stderr initialized
> The data area passed to a system call is too small. Failed to start service
>
> Throw by :
> <exec dir="${server.prefix}"
>          	  executable="${service}"
>          	  failifexecutionfails="true" failonerror="true">
>              <arg value="//ES//OWLServer"/>
>          </exec>
>
> Thanks
> -Dinu
>
> -----Original Message-----
> From: protege-discussion-bounces at lists.stanford.edu [mailto:protege-discussion-bounces at lists.stanford.edu] On Behalf Of protege-discussion-request at lists.stanford.edu
> Sent: Saturday, November 03, 2012 12:35 AM
> To: protege-discussion at lists.stanford.edu
> Subject: protege-discussion Digest, Vol 76, Issue 2
>
> Send protege-discussion mailing list submissions to
> 	protege-discussion at lists.stanford.edu
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://mailman.stanford.edu/mailman/listinfo/protege-discussion
> or, via email, send a message with subject or body 'help' to
> 	protege-discussion-request at lists.stanford.edu
>
> You can reach the person managing the list at
> 	protege-discussion-owner at lists.stanford.edu
>
> When replying, please edit your Subject line so it is more specific than "Re: Contents of protege-discussion digest..."
>
>
> Today's Topics:
>
>     1. Re: Help : Protege 4 client server (Bleeding edge version)
>        (Timothy Redmond)
>     2. Re: Term created time stamp recorded? (Samson Tu)
>     3. Re: Term created time stamp recorded? (Samson Tu)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 01 Nov 2012 12:27:38 -0700
> From: Timothy Redmond <tredmond at stanford.edu>
> To: protege-discussion at lists.stanford.edu
> Subject: Re: [protege-discussion] Help : Protege 4 client server
> 	(Bleeding edge version)
> Message-ID: <5092CD2A.6010107 at stanford.edu>
> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
>
>
> 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
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mailman.stanford.edu/pipermail/protege-discussion/attachments/20121101/410a06eb/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 01 Nov 2012 14:34:02 -0700
> From: Samson Tu <swt at stanford.edu>
> To: User support for Core Protege and the Protege-Frames editor
> 	<protege-discussion at lists.stanford.edu>
> Subject: Re: [protege-discussion] Term created time stamp recorded?
> Message-ID: <5092EACA.4010306 at stanford.edu>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> In a Protege 3.x frame ontology, you can go to Project/configure menu item, in the Options tab, check "Update modification slots." Protege will keep track of the user and time stamp of frame creation and modification in 4 system properties (:CREATION/:MODIFIER TIMESTAMP, :CREATOR, and :MODIFIER) In Protege frame, you can attach the properties to a class or metaclass, and see the information in their instances.
>
> I don't know how to make these system properties visible in a Protege 3.x OWL ontology.
>
>
> Samson
>
>
>
>
> On 10/17/2012 10:30 AM, Timothy Redmond wrote:
>> To my knowledge I don't think that either Protege 3 or Protege 4 have
>> this capability out of the box.
>>
>> -Timothy
>>
>> On 10/17/12 10:10 AM, Yu Lin wrote:
>>> Hi,  Protege developers,
>>>
>>> As a user, I wonder if the protege 4 or 3 has the function to
>>> automatically save the time stamp when a new term has been created.
>>> Please let me know, thanks.
>>>
>>> Asiyah Yu Lin @ University of Michigan
>>>
>>>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 01 Nov 2012 14:34:02 -0700
> From: Samson Tu <swt at stanford.edu>
> To: protege-discussion at lists.stanford.edu
> Subject: Re: [protege-discussion] Term created time stamp recorded?
> Message-ID: <5092EACA.4010306 at stanford.edu>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> In a Protege 3.x frame ontology, you can go to Project/configure menu
> item, in the Options tab, check "Update modification slots." Protege
> will keep track of the user and time stamp of frame creation and
> modification in 4 system properties (:CREATION/:MODIFIER TIMESTAMP,
> :CREATOR, and :MODIFIER) In Protege frame, you can attach the properties
> to a class or metaclass, and see the information in their instances.
>
> I don't know how to make these system properties visible in a Protege
> 3.x OWL ontology.
>
>
> Samson
>
>
>
>
> On 10/17/2012 10:30 AM, Timothy Redmond wrote:
>> To my knowledge I don't think that either Protege 3 or Protege 4 have
>> this capability out of the box.
>>
>> -Timothy
>>
>> On 10/17/12 10:10 AM, Yu Lin wrote:
>>> Hi,  Protege developers,
>>>
>>> As a user, I wonder if the protege 4 or 3 has the function to
>>> automatically save the time stamp when a new term has been created.
>>> Please let me know, thanks.
>>>
>>> Asiyah Yu Lin @ University of Michigan
>>>
>>>
>
>
> ------------------------------
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
>
> End of protege-discussion Digest, Vol 76, Issue 2
> *************************************************
> _______________________________________________
> 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



More information about the protege-discussion mailing list