Uploaded image for project: 'Apache Taverna'
  1. Apache Taverna
  2. TAVERNA-223

Interface hostnames being cached somewhere?

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: To Do
    • Priority: Blocker
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Taverna Server

      Description

      If a server has multiple hostnames, e.g. localhost and leela.cs.man.ac.uk, then the first of these used to connect to Taverna Server is cached and used to build all future resource URIs in the XML responses.

      Example
      A GET on http://localhost:8080/taverna241i/rest produces

      <ns3:serverDescription xmlns:ns1="http://ns.taverna.org.uk/2010/xml/server/" xmlns:ns2="http://www.w3.org/1999/xlink" xmlns:ns3="http://ns.taverna.org.uk/2010/xml/server/rest/" ns1:serverBuildTimestamp="2013-02-13T15:58:28+0000" ns1:serverRevision="unknownRevision (branch: branches/2.4.1i-branch/server-webapp)" ns1:serverVersion="2.4.1i">
      <ns3:runs ns2:href="http://localhost:8080/taverna241i/rest/runs"/>
      <ns3:policy ns2:href="http://localhost:8080/taverna241i/rest/policy"/>
      <ns3:feed ns2:href="http://localhost:8080/taverna241i/feed"/>
      <ns3:interactionFeed ns2:href="/ah/interaction/notifications"/>
      </ns3:serverDescription>
      

      And a GET on http://leela.cs.man.ac.uk:8080/taverna241i/rest also produces

      <ns3:serverDescription xmlns:ns1="http://ns.taverna.org.uk/2010/xml/server/" xmlns:ns2="http://www.w3.org/1999/xlink" xmlns:ns3="http://ns.taverna.org.uk/2010/xml/server/rest/" ns1:serverBuildTimestamp="2013-02-13T15:58:28+0000" ns1:serverRevision="unknownRevision (branch: branches/2.4.1i-branch/server-webapp)" ns1:serverVersion="2.4.1i">
      <ns3:runs ns2:href="http://localhost:8080/taverna241i/rest/runs"/>
      <ns3:policy ns2:href="http://localhost:8080/taverna241i/rest/policy"/>
      <ns3:feed ns2:href="http://localhost:8080/taverna241i/feed"/>
      <ns3:interactionFeed ns2:href="/ah/interaction/notifications"/>
      </ns3:serverDescription>
      

      The second GET should produce

      <ns3:serverDescription xmlns:ns1="http://ns.taverna.org.uk/2010/xml/server/" xmlns:ns2="http://www.w3.org/1999/xlink" xmlns:ns3="http://ns.taverna.org.uk/2010/xml/server/rest/" ns1:serverBuildTimestamp="2013-02-13T15:58:28+0000" ns1:serverRevision="unknownRevision (branch: branches/2.4.1i-branch/server-webapp)" ns1:serverVersion="2.4.1i">
      <ns3:runs ns2:href="http://leela.cs.man.ac.uk:8080/taverna241i/rest/runs"/>
      <ns3:policy ns2:href="http://leela.cs.man.ac.uk:8080/taverna241i/rest/policy"/>
      <ns3:feed ns2:href="http://leela.cs.man.ac.uk:8080/taverna241i/feed"/>
      <ns3:interactionFeed ns2:href="/ah/interaction/notifications"/>
      </ns3:serverDescription>
      

      The result of this is that if a Taverna Server gets called from localhost first then it is unusable from all other hosts!

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              stain Stian Soiland-Reyes
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: