Time delay in publishing over RMI

Post Reply
sandeepkhanna
Posts: 6
Joined: 30 Jan 2015, 15:54

We recently upgraded to version 5. By running Protege on the server, we are able publish it to viewer without any delay. However, when we run Protege from the client, the publish over RMI takes a long time, and seems stuck at "Rendering repository" and eventually proceeds with the steps (as though there is some timeout happening along the way)
BTW, we noticed that while making the connection to the repository, a warning shows up: "Annotation/Change project for rmi://server/ProjectName not configured on server <use annotation slot> --ChAOKbManager.getChAOKbFromServer()
User avatar
jonathan.carter
Posts: 1087
Joined: 04 Feb 2009, 15:44

Hi Sandeep,

Thanks very much for posting this.

I assume from what you’ve said that this behaviour is different to that which you had with version 4?

The publish to Viewer is achieved using HTTP and from what you’ve said it sounds like that is working fine. However, the overall publish process - although from an Essential perspective is the same - differs slightly at the Protege level when you publish from a server-based repository. In this case, the client must load the complete repository in order to create the snapshot and publish it to Viewer. In your first case, the repository is already fully loaded. However, in client-server mode, Protege is smart about what it loads into the client from the server and so, until you publish, only those instances that you are using are loaded into the client.

Therefore, there is a delay while your client loads the repository before it can create and publish the snapshot. The length of that delay will depend on your network connection to the server along with the performance capabilities of both the server and client host platforms.

The warning that you are receiving about the Annotation/Change project can be safely ignored. If you have defined but not implemented a ‘changes ontology’ for your repository in the definition of the Project instance in the Protege metaproject, then it is worth removing that in the Project instance for your repository. However, assuming that you have left this slot empty, this is simply a warning that you have not defined a changes ontology - which is fine.

In terms of the performance, I would be very interested to know what the difference is between version 4 and version 5. There are a few changes to the Essential Viewer Tab in Protege but these should improve performance rather than make things worse.

We’ve been working on some things that will improve all this behaviour that I’d be happy to discuss with you offline.

Jonathan
Essential Project Team
Post Reply