7 Replies Latest reply: Apr 22, 2013 3:43 PM by 613826 RSS

    ADFapplication stops working after few days of uptime : invalidobjname

    613826
      We are currently doing uptime testing of our prodcut. We are using JDEVADF_11.1.1.7.0_GENERIC_130226.1400.6493. After 3 days uptime our application stops working and we are seeing following errors in the log :-
      oracle.jbo.InvalidObjNameException: JBO-25005: Object name ViewDefMetadataManager4569314_-2147483397 of type View Row Set is invalid.
      at oracle.jbo.server.ViewObjectImpl.getRowSetName(ViewObjectImpl.java:12683)
      at oracle.jbo.server.ViewObjectImpl.createViewRowSet(ViewObjectImpl.java:12728)
      at oracle.jbo.server.ViewObjectImpl.createViewRowSet(ViewObjectImpl.java:12718)
      at oracle.jbo.server.ViewObjectImpl.getDefaultRowSet(ViewObjectImpl.java:2567)
      at oracle.jbo.server.ViewObjectImpl.setIterMode(ViewObjectImpl.java:11165)
      at oracle.adf.model.bean.DCDataVO.init(DCDataVO.java:148)
      at oracle.adf.model.bean.DCBeanDataControl.executeIteratorBindingIfNeeded(DCBeanDataControl.java:996)
      at oracle.adf.model.binding.DCIteratorBinding.executeQueryIfNeeded(DCIteratorBinding.java:2168)
      at oracle.adf.model.binding.DCBindingContainer.internalRefreshControl(DCBindingContainer.java:3253)
      at oracle.adf.controller.internal.binding.TaskFlowRegionController.doRegionRefresh(TaskFlowRegionController.java:253)
      at oracle.adf.controller.internal.binding.TaskFlowRegionController.refreshRegion(TaskFlowRegionController.java:119)
      at oracle.adf.model.binding.DCBindingContainer.internalRefreshControl(DCBindingContainer.java:3211)
      at oracle.adf.controller.internal.binding.TaskFlowRegionController.doRegionRefresh(TaskFlowRegionController.java:253)
      at oracle.adf.controller.internal.binding.TaskFlowRegionController.refreshRegion(TaskFlowRegionController.java:119)
      at oracle.adf.model.binding.DCBindingContainer.internalRefreshControl(DCBindingContainer.java:3211)
      at oracle.adf.controller.internal.binding.TaskFlowRegionController.doRegionRefresh(TaskFlowRegionController.java:253)
      at oracle.adf.controller.internal.binding.TaskFlowRegionController.refreshRegion(TaskFlowRegionController.java:119)
      at oracle.adf.model.binding.DCBindingContainer.internalRefreshControl(DCBindingContainer.java:3211)
      at oracle.adf.model.binding.DCBindingContainer.refresh(DCBindingContainer.java:2889)
      at oracle.adf.model.binding.DCBindingContainer.internalRefreshControl(DCBindingContainer.java:3202)
      at oracle.adf.model.binding.DCBindingContainer.refresh(DCBindingContainer.java:2889)
      at oracle.adf.controller.faces.lifecycle.FacesPageLifecycle.prepareRender(FacesPageLifecycle.java:82)
      at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener$5.before(ADFPhaseListener.java:516)
      at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener.beforePhase(ADFPhaseListener.java:77)
      at oracle.adfinternal.controller.faces.lifecycle.ADFLifecyclePhaseListener.beforePhase(ADFLifecyclePhaseListener.java:45)
      at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:237)
      at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
      at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
      at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
      at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
      at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
      at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205)
      at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
      at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:131)
      at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:447)
      at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
      at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:447)
      at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177)
      at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
      at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
      at oracle.epm.fm.servlets.ExternalHfmSecurityServlet.doFilter(ExternalHfmSecurityServlet.java:60)
      at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
      at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:181)
      at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
      at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
      at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
      at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
      at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
      at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:163)
      at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
      at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
      at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
      at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
      at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

      Looking at the trace it iloks weird that it is adding a -ve integer -2147483397 into the instance name.

      Edited by: Abhishek on Apr 20, 2013 8:20 AM

      Edited by: Abhishek on Apr 20, 2013 4:16 PM
        • 1. Re: ADF APPLICATION STOPS WORKING AFTER FEW DAYS OF UPTIME : INVALIDOBJNAME
          Timo Hahn
          why are you shouting?
          i don't even see question.
          how can we help you?

          Timo
          • 2. Re: ADF APPLICATION STOPS WORKING AFTER FEW DAYS OF UPTIME : INVALIDOBJNAME
            613826
            Sorry I did mean to shout.
            I wanted to know why this is happening and how to resolve it.
            • 3. Re: ADF APPLICATION STOPS WORKING AFTER FEW DAYS OF UPTIME : INVALIDOBJNAME
              dvohra21
              http://www.technicalerrors.com/2012/03/oracleappsfndframeworkoaexception_822.html
              • 4. Re: ADF APPLICATION STOPS WORKING AFTER FEW DAYS OF UPTIME : INVALIDOBJNAME
                Timo Hahn
                This kind of error is hard to diagnose. We can't really give much advice right now, as we don't know much about the application and what you where trying to do when the error showed.

                Have you tested the application with application module pooling turned off? It might be an activation/passivation problem.
                Do you work in a cluster environment?
                Do you see any more nested errors in the log?
                Try to find out what the last action has been when the application still worked. Our are there multiple use cases which error out after three days?
                Is it always three days before the error does up?
                Does the application work after a refers or new login?
                Which operating system does the server run on? How much memory is installed?
                Was there a high cpu usage at the time of the error?

                You see that there are all kind of questions you need to take into account to analyse this kind of problem.

                Timo
                • 5. Re: ADF APPLICATION STOPS WORKING AFTER FEW DAYS OF UPTIME : INVALIDOBJNAME
                  613826
                  After looking at ADF source code, ApplicationModuleImpl.doCreateViewObject() is referring to JboNameUtil.getInstNameFromDefName() which is using a static counter (int value) as suffix. The counter being an int value is reaching the upper limit and then turning out to negative when incremented and then leading to above exception.
                  In above stack trace the instance name is ViewDefMetadataManager4569314_-2147483397 , has a negative number at the end. So JboNameUtil.isNameValid(rsName) is returning false and the exception InvalidObjNameException is thrown at that point.
                  If this is the case, it appeared to be ADF bug.


                  Have you tested the application with application module pooling turned off? It might be an activation/passivation problem.
                  We use bean data control, no pooling configuration set.

                  Do you work in a cluster environment?
                  Yes but ADF is installed on a single server (Weblogic)

                  Do you see any more nested errors in the log?
                  This was the first error . After that we see same error whenever any of the UI is opened but with different VO name

                  Is it always three days before the error does up?
                  This is the first time uptime test is spawned to 3 days for this release

                  Does the application work after a refers or new login?
                  No, on new login , we see same error whenever any of the UIs is opened but with different VO name with -ve number at the end

                  Which operating system does the server run on? How much memory is installed?
                  Windows server 2008 , 16GB

                  Was there a high cpu usage at the time of the error?
                  We are testing it using load runner and multiple users
                  • 6. Re: ADF APPLICATION STOPS WORKING AFTER FEW DAYS OF UPTIME : INVALIDOBJNAME
                    Timo Hahn
                    MY advice is to open a SR with support and let them work on this. Your analysis points to this be a bug. But it only gets a bug if you file an SR.

                    Timo
                    • 7. Re: ADF APPLICATION STOPS WORKING AFTER FEW DAYS OF UPTIME : INVALIDOBJNAME
                      613826
                      Thanks Timo
                      I have put a bug for it against ADF/JBO. I also wanted to find out if anyone else has seen this issue or us doing something fundamentally wrong.
                      -Abhishek