0 Replies Latest reply: Aug 30, 2013 4:56 AM by patfmnd RSS

    Problems with listener after a clone and re-install of Apex 4.2

    patfmnd

      Hi,

      We have recently installed apex 4.2.2 into our ERP DEV environment and installed Listener 2.0.2 on Weblogic.  We have been running RESTful services fine in DEV for a couple months now for a project.  We installed same in our TEST environment but then had to re-install after a clone of TEST from our production environment (where Apex did not yet exist).  So we re-installed Apex 4.2.2 and then we re-installed Listener 2.0.2.   We are having a problem in the TEST environment that we cannot resolve related to RESTful services.

       

      Note below some of debugging messages on Weblogic.  It appears APEX_LISTENER pool is found but for some reason in TEST we cannot establish the 'Tenant'?  We are not sure what that means.  The Workspace from which RESTful services are being created are same in both cases.  Right now we are just trying to work with the existing HR sample data RESTful services that come with the install and workspace creation and can't even get that to work.  No error messages come back but you can see that multiple tries are made  'Attempting to process as a RESTful Service.

       

      Is there any debugging we should be doing on the Oracle database side of Apex? Possibly some permissions missing?? Any ideas on where we should look would be appreciated.  We need to have the services available in TEST ASAP.

       

      Should we just try a full re-install of both Apex and Listener?

       

      Thanks,

      Pat

       

      On DEV - works

      ===============

      Mapping request to database pool: PoolMap [_poolName=BNRDEV, _regex=null, _workspaceIdentifier=, _failed=false, _lastUpdate=1367345341205, _template=/bnrws/, _type=BASE_PATH]

      Applied database connection info

      Attempting to process with PL/SQL Gateway

      Not processed as PL/SQL Gateway request

      Attempting to process as a RESTful Service

      Determining if request can be dispatched as a Tenanted RESTful Service

      Request path has one path segment, continuing processing

      No Tenant Principal established yet, continuing processing

      APEX_LISTENER pool exists, continuing processing

       

      Matching tenant exists, continuing processing

      Dispatching as tenanted request, with base: http://dev_server.edu/ace/bnrws/ace/, target: students/course_grades_term/%7Bterm%7D, tenant: TenantPrincipal [name=ACE]

       

       

      On TEST - does not work

      =======================

      Mapping request to database pool: PoolMap [_poolName=BNRTEST, _regex=null, _workspaceIdentifier=, _failed=false, _lastUpdate=1372859385350, _template=/bnrws/, _type=BASE_PATH]

      Applied database connection info

      Attempting to process with PL/SQL Gateway

      Not processed as PL/SQL Gateway request

      Attempting to process as a RESTful Service

      Determining if request can be dispatched as a Tenanted RESTful Service

      Request path has one path segment, continuing processing

      No Tenant Principal established yet, continuing processing

      APEX_LISTENER pool exists, continuing processing

       

      Request Path passes syntax validation

      Mapping request to database pool: PoolMap [_poolName=BNRTEST, _regex=null, _workspaceIdentifier=, _failed=false, _lastUpdate=1372859385350, _template=/bnrws/, _type=BASE_PATH]

      Applied database connection info

      Attempting to process with PL/SQL Gateway

      Not processed as PL/SQL Gateway request

      Attempting to process as a RESTful Service

      Determining if request can be dispatched as a Tenanted RESTful Service

      Request path has one path segment, continuing processing

      No Tenant Principal established yet, continuing processing

        APEX_LISTENER pool exists, continuing processing>

       

      Message was edited by: patfmnd We ended up re-configuring Listener 2.0.2 from scratch but don't know why it started working.  We now have same issue in Production -- no clone involved, but error is the same  -- never finds 'Tenant Principal'.  Is there any other diagnostic tool we should be using to find out the source of the problem???