glassfish
  1. glassfish
  2. GLASSFISH-9699

[Blocking] got exception Unsupported endpoint address: REPLACE_WITH_ACTUAL_URL

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Won't Fix
    • Affects Version/s: V3
    • Fix Version/s: V3
    • Component/s: upgrade_tool
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: Sun

    • Issuezilla Id:
      9,699

      Description

      Sidebyside upgrade from glassfish v2.1 to glassfish v3 on linux5.0 using CLI
      mode. Deploy jbi application in V2 Quicklooks tests

      After upgrade, I ran the application and got the following error from the
      console. See attached server.log (please ignore the NPE exception seen in log
      belongs to another application)

      Error seen at console:

      1. ant run
        Buildfile: build.xml

      run:

      setOSConditions:

      setToolWin:

      setToolUnix:

      setToolProperty:

      setS1ASclassPath:

      init-common:

      run-local-client:
      [java] Host [localhost] port (8080)
      [java] Calling Servlet /callMessagesEJB/TestServlet?test=testPing
      [java] HTTP/1.1 200 OK
      [java] X-Powered-By: Servlet/3.0
      [java] Server: GlassFish/v3
      [java] Content-Type: text/html;charset=UTF-8
      [java] Content-Length: 3167
      [java] Date: Wed, 23 Sep 2009 16:15:47 GMT
      [java] Connection: close

      [java] Calling test : testPing
      [java] testPing:FAIL
      [java] Value of key is:jbi.helloca.messages.testPing
      [java] javax.xml.ws.WebServiceException: Unsupported endpoint address:
      REPLACE_WITH_ACTUAL_URL
      [java] at
      com.sun.xml.ws.api.pipe.TransportTubeFactory.create(TransportTubeFactory.java:144)
      [java] at
      com.sun.xml.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:129)
      [java] at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:629)
      [java] at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:588)
      [java] at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:573)
      [java] at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:470)
      [java] at com.sun.xml.ws.client.Stub.process(Stub.java:319)
      [java] at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:157)
      [java] at
      com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:109)
      [java] at
      com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
      [java] at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:140)
      [java] at $Proxy167.ping(Unknown Source)
      [java] at outbound.servlet.TestServlet.testPing(TestServlet.java:54)
      [java] at outbound.servlet.TestServlet.processRequest(TestServlet.java:40)
      [java] at outbound.servlet.TestServlet.doGet(TestServlet.java:128)
      [java] at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
      [java] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
      [java] at
      org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1522)
      [java] at
      org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:292)
      [java] at
      org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:188)
      [java] at
      org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:641)
      [java] at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:97)
      [java] at
      com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:85)
      [java] at
      org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:185)
      [java] at
      org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:332)
      [java] at
      org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:233)
      [java] at
      com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:209)
      [java] at
      com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:753)
      [java] at
      com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:661)
      [java] at
      com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:914)
      [java] at
      com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:166)
      [java] at
      com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135)
      [java] at
      com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102)
      [java] at
      com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88)
      [java] at
      com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
      [java] at
      com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53)
      [java] at
      com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57)
      [java] at com.sun.grizzly.ContextTask.run(ContextTask.java:69)
      [java] at
      com.sun.grizzly.util.FixedThreadPool$BasicWorker.dowork(FixedThreadPool.java:379)
      [java] at
      com.sun.grizzly.util.FixedThreadPool$BasicWorker.run(FixedThreadPool.java:360)
      [java] at java.lang.Thread.run(Thread.java:619)

      Steps to produce:
      1) install glassfish v2.1
      2) asadmin start-domain, asadmin start-database
      3) check out V2 Quicklooks workspace, choose test case reside under <workspace
      directory>/sqetests/jbi/helloca/scripts/messages

      set environment variables APS_HOME pointing to v2 workspace, ANT_HOME,
      JAVA_HOME. S1AS_HOME, PATH to $ANT_HOME/bin:$JAVA_HOME/bin:$PATH

      4) execute "ant setup"

      5) asadmin stop-domain
      asadmin stop-database

      6) install v3 nightly build 9/22/09

      7) run <v3 install>/bin/asupgrade -c

      8) asadmin start-domain
      asadmin start-database

      9) cd appserv-tests/sqetests/jbi/helloca/scripts/messages
      type "ant run"

        Activity

        Hide
        1xpert added a comment -

        Created an attachment (id=3281)
        log

        Show
        1xpert added a comment - Created an attachment (id=3281) log
        Hide
        1xpert added a comment -

        More details on Step 3 of this issue.

        Easy way to checkout V2 quicklooks test:

        1) set variables:
        set CVSROOT to :pserver:<your java.net id>@cvs.dev.java.net:/cvs
        set APS_HOME to point to <quicklooks workspace>/appserv-tests
        set S1AS_HOME to point to appserver or glassfish server
        set JAVA_HOME to point to 1.6.0_14
        set ANT_HOME to point to 1.6.5
        set PATH to point to $ANT_HOME/bin:$JAVA_HOME/bin:$PATH

        2) cvs login
        cvs co -r SJSAS91_FCS_BRANCH glassfish/appserv-tests

        3) cd <workspace
        directory>/sqetests/jbi/helloca/scripts/messages

        Show
        1xpert added a comment - More details on Step 3 of this issue. Easy way to checkout V2 quicklooks test: 1) set variables: set CVSROOT to :pserver:<your java.net id>@cvs.dev.java.net:/cvs set APS_HOME to point to <quicklooks workspace>/appserv-tests set S1AS_HOME to point to appserver or glassfish server set JAVA_HOME to point to 1.6.0_14 set ANT_HOME to point to 1.6.5 set PATH to point to $ANT_HOME/bin:$JAVA_HOME/bin:$PATH 2) cvs login cvs co -r SJSAS91_FCS_BRANCH glassfish/appserv-tests 3) cd <workspace directory>/sqetests/jbi/helloca/scripts/messages
        Hide
        1xpert added a comment -

        Per Abhijit and Alex's requests, I add keyword Blocking for tracking purpose

        Show
        1xpert added a comment - Per Abhijit and Alex's requests, I add keyword Blocking for tracking purpose
        Hide
        Hong Zhang added a comment -

        The JBI is not enabled out of box in v3, we are currently talking with JBI team
        to figure out how to support the upgrade scenario for JBI applications in v3.

        Show
        Hong Zhang added a comment - The JBI is not enabled out of box in v3, we are currently talking with JBI team to figure out how to support the upgrade scenario for JBI applications in v3.
        Hide
        Hong Zhang added a comment -

        add mohit (from jbi team) and myself to cc

        Show
        Hong Zhang added a comment - add mohit (from jbi team) and myself to cc
        Hide
        Bobby Bissett added a comment -

        Adding Vella to cc list as well. Am adding this information here and will check with the powers that be.

        From part of a separate email conversation about how to handle this, I wrote:
        "My suggestion: document that JBI isn't supported out of the box, mark 9699 as a feature request, and
        make sure that upgrade still works even if one application fails to deploy. Does anyone see a serious issue
        with that?"

        It was pointed out that even if we can't make this a part of an automated upgrade, we should figure out
        the manual steps to do so.

        Show
        Bobby Bissett added a comment - Adding Vella to cc list as well. Am adding this information here and will check with the powers that be. From part of a separate email conversation about how to handle this, I wrote: "My suggestion: document that JBI isn't supported out of the box, mark 9699 as a feature request, and make sure that upgrade still works even if one application fails to deploy. Does anyone see a serious issue with that?" It was pointed out that even if we can't make this a part of an automated upgrade, we should figure out the manual steps to do so.
        Hide
        Bobby Bissett added a comment -

        Have heard back that we can forget this one for v3. Right now we should not do any testing that involved
        JBI. Please just make sure there are other web service tests so that the endpoint address issue isn't general
        and not part of JBI support.

        Show
        Bobby Bissett added a comment - Have heard back that we can forget this one for v3. Right now we should not do any testing that involved JBI. Please just make sure there are other web service tests so that the endpoint address issue isn't general and not part of JBI support.

          People

          • Assignee:
            Bobby Bissett
            Reporter:
            1xpert
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: