Hi Jan, Having a look at the logs you sent me I read the following: > INFO 437[main](KIMServiceImpl.java:173) - Sesame [STARTED] on Thu Nov > 23 09:25:54 CET 2006 which obviously means you start KIM with Sesame built-in. Please do: > 1) in ./config/semantic.repository.properties set > - com.ontotext.kim.KIMConstants.SESAME_IS_REMOTE = true and then start KIM so it is forced to connect to the separate Sesame instance instead of starting its own inside KIM's thread. Thus an error should appear, should be printed and logged. While running Sesame in built-in mode KIM will have no problem as it will access its internal instance no matter how many external ones are started.
I didn't ask you but you're running everything on one and the same machine, aren't you? Ilian ----- Original Message ----- From: "Jan Henke" <[EMAIL PROTECTED]> To: "'Ilian Kitchukov'" <[EMAIL PROTECTED]> Sent: 23 November 2006, Thursday 10:30 Subject: AW: KIM Hi Ilian, I'm attaching the logs after doing all the changes (also install.properties) and starting KIM. Best regards Jan > -----Ursprüngliche Nachricht----- > Von: Ilian Kitchukov [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 22. November 2006 18:02 > An: Jan Henke > Cc: [KIM-discussion] > Betreff: Re: KIM > > Hi Jan, > > Well Damian told me about your problem and you say you've > passed through all the steps recommended, but I don't know > what is the current state of cinfigurations and scripts there > at your side. So, please try the following: > 1) in ./config/semantic.repository.properties set > - com.ontotext.kim.KIMConstants.SESAME_IS_REMOTE = true > - com.ontotext.kim.KIMConstants.SESAME_RMI_HOST=<your local IP> > - com.ontotext.kim.KIMConstants.SESAME_RMI_PORT=<some unused port> > 2) in ./bin.config_kim.sh set > - SWAN_RMI_HOST=-D"java.rmi.server.hostname=<your local IP>" > 3) run ./bin/startSesame.sh and wait until it loads > 4) run ./bin/startTomcat.sh > 5) open a browser at http://<your local IP here>:<port if > any>/sesame-web-ui > 6) on the screen that should show type in the text box > rmi://<your local IP>:<sesame port configured above> > and press "Bind>>" > > If this doesn't help please do the following in order to > provide me with some additional information to identify the problem: > 1) in ./config/install.properties set > - com.ontotext.kim.KIMConstants.RMI_HOST=<your local IP> > - com.ontotext.kim.KIMConstants.RMI_PORT=<some unused port> > 2) same as step 2 above > 3) same as step 3 above > 4) run ./bin/startKIM.sh and wait until it loads > 5) send me any error messages that appear in case it doesn't > load normally > > Just in case, before doing all of the above, go to the ./log > folder and empty all its subfolders - after performing those > steps new logs will be created, and the non-empty ones might > potentially contain some error logs. > Send them to me too. > > HTH, > Ilian > > ----- Original Message ----- > From: "Jan Henke" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: 22 November 2006, Wednesday 17:39 > Subject: KIM > > > > Dear Ilian, > > > > I have a question about KIM: I'm still struggling with > refused connections > > with regard to RMI. I think I went through the steps in > > > http://www.ontotext.com/kim/doc/sys-doc/faq-howto-bugs/howto-p rocedures.html > > #q7 but still I get > > > > Unable to connect to Sesame service at 'rmi://localhost:1098 > > > > within the sesame-web-ui > > > > Do you have any further suggestion? > > > > Best regards > > Jan Henke > > > > ------------------------------------ > > DERI Innsbruck > > Jan Henke > > [EMAIL PROTECTED] > > Technikerstraße 21a > > 6020 Innsbruck > > tel: 0043-512-507 6451 > > ------------------------------------ > > > > > > > > __________ NOD32 1877 (20061122) Information __________ > > > > This message was checked by NOD32 antivirus system. > > http://www.eset.com > > > > > __________ NOD32 1878 (20061122) Information __________ This message was checked by NOD32 antivirus system. http://www.eset.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
