Not related to main question but noted an inconsistency. "startAiravataServer", "StartOrchestratorServer" and "StartGfacServer". Why AiravataAPIServer is different from others ? and are these "StartXXX" are methods ? then they should probably start with simple case.
Thanks -Thejaka On Tue, Jun 30, 2015 at 11:44 PM, Shameera Rathnayaka < shameerai...@gmail.com> wrote: > Hi Pankaj, > > Here is the set of classes where we bind ports with thrift services. > for API server > - org.apache.airavata.api.server.AiravataAPIServer#startAiravataServer > for Orchestrator > - > org.apache.airavata.orchestrator.server.OrchestratorServer#StartOrchestratorServer > for Gfac - org.apache.airavata.gfac.server.GfacServer#StartGfacServer > > With work queue implementation with rabbitmq, we are not using gfac ports > but others. Let me know if you need more information. > > Thanks, > Shameera. > > On Tue, Jun 30, 2015 at 7:11 PM, Pankaj Saha <psa...@binghamton.edu> > wrote: > >> Hi Shameera, >> >> can you guide me on which java classes are involved in setting the >> airavata API service running. I want to give a try if I can debug the >> docker issue from the java source code. >> Actually I want to add one non apache thrift service to airavata servers >> and see its behavior. >> >> Thanks >> Pankaj >> > > > > -- > Best Regards, > Shameera Rathnayaka. > > email: shameera AT apache.org , shameerainfo AT gmail.com > Blog : http://shameerarathnayaka.blogspot.com/ >
