Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
AW: RE: [smila-user] SMILA M1 remote connection via jconsole

Hi Marc,

This is great news!

Thank you for your feedback. I'll write some lines about this in our FAQ so that other people can profit from you experiences.

Regards
Igor



> -----Ursprüngliche Nachricht-----
> Von: smila-user-bounces@xxxxxxxxxxx [mailto:smila-user-bounces@xxxxxxxxxxx]
> Im Auftrag von Wieneke, Marc (K-SIO-C/2)
> Gesendet: Mittwoch, 10. Juni 2009 17:46
> An: smila-user@xxxxxxxxxxx
> Betreff: RE: RE: [smila-user] SMILA M1 remote connection via jconsole
> 
> Hi Juergen, hi Igor,
> I'm very pleased that you helped me out if this so fast. (-;
> I've followed your hints and solved both problems.
> 
> 1. I've changed the /etc/hosts entry to the servers ip. --> Connecting
> via remote jconsole works now.
> 2. I've put some data into the directory and started the crawler for the
> first time. --> Loading the SearchServlet even works now.
> 
> BTW: SMILA M2 does work for me yet! (-:
> 
> 
> Thank you!
> Cheers,
> Marc.
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Wed, 10 Jun 2009 14:44:03 +0200
> From: <Juergen.Schumacher@xxxxxxxxxxx>
> Subject: RE: RE: [smila-user] SMILA M1 remote connection via jconsole
> To: <smila-user@xxxxxxxxxxx>
> Message-ID:
> 
> <653C8E101491144F9B644FFA6652F5E5014ACF8F@xxxxxxxxxxxxxxxxxxxxxxxxx>
> Content-Type: text/plain;	charset="iso-8859-1"
> 
> Hi Marc
> 
> still don't have a idea about your jconsole problem, but this...
> 
> > root cause
> > org.eclipse.smila.search.index.IndexException: index does not exist in
> data dictionary [test_index]
> 
> ... happens as long as no index has yet been created by a crawler or
> agent being run.
> After you start a crawler or agent (and wait a moment) you can just
> reload the search page
> and it should work. Yes, we should probably add a check for this to
> produce a better message.
> 
> Or you have changed the configuration such that an index with another
> name is created.
> In this case you should also change the default index name in
> configuration\org.eclipse.smila.processing.bpel\pipelines\searchpipeline
> .bpel
> in this element:
> 
> <extensionActivity name="invokeLuceneSearchService">
>   ...
>   <rec:An n="org.eclipse.smila.lucene.LuceneSearchService">
>     <rec:V n="indexName">test_index</rec:V>
>   </rec:An>
> 
> Cheers,
> Juergen.
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Wed, 10 Jun 2009 17:21:12 +0200
> From: <Igor.Novakovic@xxxxxxxxxxx>
> Subject: AW: RE: [smila-user] SMILA M1 remote connection via jconsole
> To: <smila-user@xxxxxxxxxxx>
> Message-ID:
> 
> <653C8E101491144F9B644FFA6652F5E50146640C@xxxxxxxxxxxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="us-ascii"
> 
> Hi Marc,
> 
> 
> 
> well I do have Ubuntu (8.10) on one of my machines and since I always
> connect to SMILA with the local jconsole, the problem that you have
> never occurred to me - until today, when I tried to access SMILA
> (running on my Ubuntu desktop) with jconsole (running on my WinXP
> laptop).
> 
> 
> 
> First, to make things clear: This is not a SMILA issue. This seems to be
> a Java issue solely on Ubuntu (at least for 8.04 and newer)
> installations.
> 
> 
> 
> As always, Google is our friend, so I found out that you and I are not
> the only people having the same problem J
> 
> Some of them provide different solutions:
> 
> 1.       http://labs.scireum.de/?p=23 - did not work for me (perhaps
> because I have an newer Ubuntu distro)
> 
> 2.
> http://myjavanotebook.blogspot.com/2008/03/jmx-remote-connection-failure
> -to-java.html - did not work for me too
> 
> But from these two links I've got some ideas and came up with my own
> solution:
> 
> The only thing I had to change is the configuration of /etc/hosts file.
> 
> The default setting is:
> 
> 127.0.0.1 localhost
> 
> 127.0.1.1 jupiter        ("Jupiter" is the name of my Ubuntu machine)
> 
> ...
> 
> some IPv6 settings
> 
> 
> 
> When I changed the second line with:
> 
> 192.168.220.101 jupiter         (192.168.220.101 is the actual IP of
> Ubuntu machine)
> 
> Then I was able to connect remotely.
> 
> 
> 
> Please try this out and let me know if it worked for you.
> 
> 
> 
> Cheers
> 
> Igor
> 
> 
> 
> 
> 
> Von: smila-user-bounces@xxxxxxxxxxx
> [mailto:smila-user-bounces@xxxxxxxxxxx] Im Auftrag von Wieneke, Marc
> (K-SIO-C/2)
> Gesendet: Mittwoch, 10. Juni 2009 14:32
> An: smila-user@xxxxxxxxxxx
> Betreff: RE: RE: [smila-user] SMILA M1 remote connection via jconsole
> 
> 
> 
> Hi,
> 
> at first thank you for the quick response. English is ok for me but I'm
> not so good in English. J
> 
> Though I didn't changed anything now I can load the SearchServlet of
> SMILA M2 on Linux. I'm a little bit confused about that but nevertheless
> it's nice that it's running now.
> 
> For testing purposes I've already deactivated the firewall on ubuntu
> temporary but I can't get a connection with jconsole. There is only 1
> network interface active and there are no other applications running on
> the server because I've installed the server just for SMILA. The IP
> should be right because I can access the SearchServlet.
> 
> On my local Windows client I get the following errors with SMILA M2
> which I had before on my Linux machine too:
> 
> type Exception report
> 
> message
> 
> description The server encountered an internal error () that prevented
> it from fulfilling this request.
> 
> exception
> 
> javax.servlet.ServletException: error processing search request
> 
> 
> org.eclipse.smila.search.servlet.SMILASearchServlet.processRequest(SMILA
> SearchServlet.java:199)
> 
> 
> org.eclipse.smila.search.servlet.SMILASearchServlet.doGet(SMILASearchSer
> vlet.java:99)
> 
>         javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> 
>         javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> 
> root cause
> 
> org.eclipse.smila.processing.ProcessingException: Error processing BPEL
> workflow SearchPipeline: Invocation of pipeline element
> SearchPipeline/extensionActivity-activity-line-35 failed: Error
> processing message
> src:10.180.157.0|key:<d263b151-7e6d-42f9-95cf-a2e6f7310a4d>
> 
> 
> org.eclipse.smila.processing.bpel.ODEWorkflowProcessor.process(ODEWorkfl
> owProcessor.java:283)
> 
> 
> org.eclipse.smila.search.api.internal.SearchServiceImpl.search(SearchSer
> viceImpl.java:89)
> 
> 
> org.eclipse.smila.search.api.internal.SearchServiceImpl.searchAsXml(Sear
> chServiceImpl.java:118)
> 
> 
> org.eclipse.smila.search.api.helper.QueryBuilder.executeRequestXml(Query
> Builder.java:482)
> 
> 
> org.eclipse.smila.search.servlet.SMILASearchServlet.processRequest(SMILA
> SearchServlet.java:175)
> 
> 
> org.eclipse.smila.search.servlet.SMILASearchServlet.doGet(SMILASearchSer
> vlet.java:99)
> 
>         javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> 
>         javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> 
> root cause
> 
> org.eclipse.smila.processing.ProcessingException: Invocation of pipeline
> element SearchPipeline/extensionActivity-activity-line-35 failed: Error
> processing message
> src:10.180.157.0|key:<d263b151-7e6d-42f9-95cf-a2e6f7310a4d>
> 
> 
> org.eclipse.smila.processing.bpel.ExtensionManager.newProcessingExceptio
> n(ExtensionManager.java:275)
> 
> 
> org.eclipse.smila.processing.bpel.ExtensionManager.invokeAdapter(Extensi
> onManager.java:239)
> 
> 
> org.eclipse.smila.processing.bpel.ExtensionManager.invokeActivity(Extens
> ionManager.java:164)
> 
> 
> org.eclipse.smila.processing.bpel.SMILAExtensionBundle$InvokeServiceActi
> vity.run(SMILAExtensionBundle.java:126)
> 
> 
> org.eclipse.smila.processing.bpel.SMILAExtensionBundle$InvokeServiceActi
> vity.run(SMILAExtensionBundle.java:138)
> 
> 
> org.apache.ode.bpel.rtrep.v2.EXTENSIONACTIVITY.run(EXTENSIONACTIVITY.jav
> a:62)
> 
>         sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source)
> 
>         sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> 
>         java.lang.reflect.Method.invoke(Unknown Source)
> 
> 
> org.apache.ode.jacob.vpu.JacobVPU$JacobThreadImpl.run(JacobVPU.java:451)
> 
>         org.apache.ode.jacob.vpu.JacobVPU.execute(JacobVPU.java:139)
> 
> 
> org.apache.ode.bpel.rtrep.v2.RuntimeInstanceImpl.execute(RuntimeInstance
> Impl.java:639)
> 
> 
> org.apache.ode.bpel.engine.BpelRuntimeContextImpl.execute(BpelRuntimeCon
> textImpl.java:593)
> 
> 
> org.apache.ode.bpel.engine.BpelRuntimeContextImpl.executeCreateInstance(
> BpelRuntimeContextImpl.java:581)
> 
> 
> org.apache.ode.bpel.engine.ODEProcess.executeCreateInstance(ODEProcess.j
> ava:373)
> 
> 
> org.apache.ode.bpel.engine.ODEProcess$2.call(ODEProcess.java:295)
> 
> 
> org.apache.ode.bpel.engine.ODEProcess$2.call(ODEProcess.java:294)
> 
> 
> org.apache.ode.bpel.engine.ODEProcess$ProcessCallable.call(ODEProcess.ja
> va:1206)
> 
> 
> org.apache.ode.bpel.engine.BpelInstanceWorker.doInstanceWork(BpelInstanc
> eWorker.java:174)
> 
> 
> org.apache.ode.bpel.engine.BpelInstanceWorker.execInCurrentThread(BpelIn
> stanceWorker.java:108)
> 
> 
> org.apache.ode.bpel.engine.ODEProcess.doInstanceWork(ODEProcess.java:487
> )
> 
> 
> org.apache.ode.bpel.engine.ODEProcess.invokeProcess(ODEProcess.java:293)
> 
> 
> org.apache.ode.bpel.engine.MyRoleMessageExchangeImpl.doInvoke(MyRoleMess
> ageExchangeImpl.java:122)
> 
> 
> org.apache.ode.bpel.engine.UnreliableMyRoleMessageExchangeImpl$1.call(Un
> reliableMyRoleMessageExchangeImpl.java:44)
> 
> 
> org.apache.ode.bpel.engine.UnreliableMyRoleMessageExchangeImpl$1.call(Un
> reliableMyRoleMessageExchangeImpl.java:43)
> 
> 
> org.apache.ode.bpel.engine.ODEProcess$ProcessCallable.call(ODEProcess.ja
> va:1206)
> 
> 
> org.apache.ode.bpel.engine.Contexts.execTransaction(Contexts.java:106)
> 
> 
> org.apache.ode.bpel.engine.BpelServerImpl$TransactedCallable.call(BpelSe
> rverImpl.java:968)
> 
> 
> org.apache.ode.bpel.engine.BpelServerImpl$ServerCallable.call(BpelServer
> Impl.java:948)
> 
>         java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> 
>         java.util.concurrent.FutureTask.run(Unknown Source)
> 
>         java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
> Source)
> 
>         java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
> Source)
> 
>         java.lang.Thread.run(Unknown Source)
> 
> root cause
> 
> org.eclipse.smila.search.index.IndexException: index does not exist in
> data dictionary [test_index]
> 
> 
> org.eclipse.smila.search.index.IndexManager.getInstance(IndexManager.jav
> a:74)
> 
> 
> org.eclipse.smila.lucene.LuceneSearchService.search(LuceneSearchService.
> java:207)
> 
> 
> org.eclipse.smila.lucene.LuceneSearchService.process(LuceneSearchService
> .java:171)
> 
> 
> org.eclipse.smila.processing.bpel.ProcessingServiceManager.doInvoke(Proc
> essingServiceManager.java:125)
> 
> 
> org.eclipse.smila.processing.bpel.ExtensionManager.invokeAdapter(Extensi
> onManager.java:228)
> 
> 
> org.eclipse.smila.processing.bpel.ExtensionManager.invokeActivity(Extens
> ionManager.java:164)
> 
> 
> org.eclipse.smila.processing.bpel.SMILAExtensionBundle$InvokeServiceActi
> vity.run(SMILAExtensionBundle.java:126)
> 
> 
> org.eclipse.smila.processing.bpel.SMILAExtensionBundle$InvokeServiceActi
> vity.run(SMILAExtensionBundle.java:138)
> 
> 
> org.apache.ode.bpel.rtrep.v2.EXTENSIONACTIVITY.run(EXTENSIONACTIVITY.jav
> a:62)
> 
>         sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source)
> 
>         sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> 
>         java.lang.reflect.Method.invoke(Unknown Source)
> 
> 
> org.apache.ode.jacob.vpu.JacobVPU$JacobThreadImpl.run(JacobVPU.java:451)
> 
>         org.apache.ode.jacob.vpu.JacobVPU.execute(JacobVPU.java:139)
> 
> 
> org.apache.ode.bpel.rtrep.v2.RuntimeInstanceImpl.execute(RuntimeInstance
> Impl.java:639)
> 
> 
> org.apache.ode.bpel.engine.BpelRuntimeContextImpl.execute(BpelRuntimeCon
> textImpl.java:593)
> 
> 
> org.apache.ode.bpel.engine.BpelRuntimeContextImpl.executeCreateInstance(
> BpelRuntimeContextImpl.java:581)
> 
> 
> org.apache.ode.bpel.engine.ODEProcess.executeCreateInstance(ODEProcess.j
> ava:373)
> 
> 
> org.apache.ode.bpel.engine.ODEProcess$2.call(ODEProcess.java:295)
> 
> 
> org.apache.ode.bpel.engine.ODEProcess$2.call(ODEProcess.java:294)
> 
> 
> org.apache.ode.bpel.engine.ODEProcess$ProcessCallable.call(ODEProcess.ja
> va:1206)
> 
> 
> org.apache.ode.bpel.engine.BpelInstanceWorker.doInstanceWork(BpelInstanc
> eWorker.java:174)
> 
> 
> org.apache.ode.bpel.engine.BpelInstanceWorker.execInCurrentThread(BpelIn
> stanceWorker.java:108)
> 
> 
> org.apache.ode.bpel.engine.ODEProcess.doInstanceWork(ODEProcess.java:487
> )
> 
> 
> org.apache.ode.bpel.engine.ODEProcess.invokeProcess(ODEProcess.java:293)
> 
> 
> org.apache.ode.bpel.engine.MyRoleMessageExchangeImpl.doInvoke(MyRoleMess
> ageExchangeImpl.java:122)
> 
> 
> org.apache.ode.bpel.engine.UnreliableMyRoleMessageExchangeImpl$1.call(Un
> reliableMyRoleMessageExchangeImpl.java:44)
> 
> 
> org.apache.ode.bpel.engine.UnreliableMyRoleMessageExchangeImpl$1.call(Un
> reliableMyRoleMessageExchangeImpl.java:43)
> 
> 
> org.apache.ode.bpel.engine.ODEProcess$ProcessCallable.call(ODEProcess.ja
> va:1206)
> 
> 
> org.apache.ode.bpel.engine.Contexts.execTransaction(Contexts.java:106)
> 
> 
> org.apache.ode.bpel.engine.BpelServerImpl$TransactedCallable.call(BpelSe
> rverImpl.java:968)
> 
> 
> org.apache.ode.bpel.engine.BpelServerImpl$ServerCallable.call(BpelServer
> Impl.java:948)
> 
>         java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> 
>         java.util.concurrent.FutureTask.run(Unknown Source)
> 
>         java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
> Source)
> 
>         java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
> Source)
> 
>         java.lang.Thread.run(Unknown Source)
> 
> note The full stack trace of the root cause is available in the Apache
> Tomcat/6.0-snapshot logs.
> 
> I hope this messages will help you.
> 
> Kind regards,
> 
> Marc
> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> https://dev.eclipse.org/mailman/private/smila-user/attachments/20090610/
> 5fc5b405/attachment.html
> 
> ------------------------------
> 
> _______________________________________________
> smila-user mailing list
> smila-user@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/smila-user
> 
> 
> End of smila-user Digest, Vol 8, Issue 4
> ****************************************
> _______________________________________________
> smila-user mailing list
> smila-user@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/smila-user


Back to the top