Hi Steven,

It appears that the KIM's cache is corrupted. It was probably caused by 
a crash or an sudden shutdown. The latest version of KIM 2.3 tries to 
recover its cache in that case, so that error message should be followed 
by other messages like Trying to recover and so on. That error should 
not be caused by network changes. If KIM cannot recover its cache for 
some reason, stop KIM, delete the cache from 
KIM/context/default/populated/cache and start KIM again. That's provided 
that you run an embedded Sesame as is by default. Are you getting such 
messages in the logs after this error?

Regarding the proxy server, remember that you cannot use a proxy between 
the KIM Server and the KIM Web UI or between KIM and a standalone 
Sesame. You can use a proxy only between KIM and any remote web servers 
that you annotate pages from. If that is that case, try the Sun's RMI 
network troubeshooting guide at 
http://java.sun.com/javase/6/docs/technotes/guides/rmi/faq.html#netcontact 
for Java 6 and 
http://java.sun.com/j2se/1.5.0/docs/guide/rmi/faq.html#netcontact for Java 5

Hope that helps,
Marin Nozhchev

steven shingler wrote:
> hi all
> we've had some network changes, and it seems to have affected our KIM 
> server - not getting any results back at all!
> i've set the logging to DEBUG, and i'm seeing a lot of:
>
> ERROR 1090516[RMI TCP Connection(8)-146.80.94.12 
> <http://146.80.94.12>](EntitiesCache.java:934) - addNS() with unknown 
> prefix 1 was called. (localName=1:CountryAdj_T.29)
>
> the network changes have involved adding a proxy server, and so i am 
> starting up KIM with the proxyHost parameter - so hopefully that part 
> is right - it is as if KIM can't send messages back to the client...? 
> but both machines can ping each other...
> i wish i knew more about networking at this point! :(
> any advice gratefully received,
> thanks
> steven
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> NOTE: Please REPLY TO ALL to ensure that your reply reaches all members of 
> this mailing list.
>
> KIM-discussion mailing list
> [email protected]
> http://ontotext.com/mailman/listinfo/kim-discussion_ontotext.com
>   


_______________________________________________
NOTE: Please REPLY TO ALL to ensure that your reply reaches all members of this 
mailing list.

KIM-discussion mailing list
[email protected]
http://ontotext.com/mailman/listinfo/kim-discussion_ontotext.com

Reply via email to