Skip to Main Content
Forums

Java Development Tools

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

JDeveloper 12.2.1.3 ADF Application java.lang.NoSuchMethodError: -org.apache.myfaces.trinidadinte

PrakashCMar 11 2022

Hi,
I had a running application. Recently at my work place, some patches were pushed into my windows PC, which made my integrated WebLogic server to fail. On investigation, it was found that there were some privileges that got revoked (specifically on cwallet.sso ). The Desktop admins fixed the issue by granting me the file permissions on the folder, & this resolved the issue.
I now have one application which used to work & is no longer working. I tested one another application & it still works. I am clue less of what needs to be done. May be the patching event is unrelated.
The application gets deployed without any issue, however prior to the sign-in page, I see the following error.
I would appreciate some help.

Regards,
Prakash

ERROR---

<oracle.adf.controller> <AdfcExceptionHandler> <handleException> <ADFc: No exception handler was found for an application exception.>
java.lang.NoSuchMethodError: org.apache.myfaces.trinidadinternal.agent.AgentImpl$AgentType.valueOfDisplayName(Ljava/lang/String;)Lorg/apache/myfaces/trinidadinternal/agent/AgentImpl$AgentType;
at oracle.adfinternal.view.faces.renderkit.rich.RichAdfRenderingContext._getloopbackCapabilities(RichAdfRenderingContext.java:484)
at oracle.adfinternal.view.faces.renderkit.rich.RichAdfRenderingContext._getCapabilityDeltas(RichAdfRenderingContext.java:444)
at oracle.adfinternal.view.faces.renderkit.rich.RichAdfRenderingContext._calculateAgent(RichAdfRenderingContext.java:383)
at oracle.adfinternal.view.faces.renderkit.rich.RichAdfRenderingContext.getAgent(RichAdfRenderingContext.java:367)
at org.apache.myfaces.trinidadinternal.renderkit.core.CoreRendererUtils.supportsBooleanCapability(CoreRendererUtils.java:76)
at org.apache.myfaces.trinidadinternal.renderkit.core.CoreRendererUtils.supportsPartialRendering(CoreRendererUtils.java:59)
at org.apache.myfaces.trinidadinternal.renderkit.core.CoreRenderingContext._initializePPR(CoreRenderingContext.java:744)
at org.apache.myfaces.trinidadinternal.renderkit.core.CoreRenderingContext.<init>(CoreRenderingContext.java:90)
at oracle.adfinternal.view.faces.renderkit.rich.RichAdfRenderingContext.<init>(RichAdfRenderingContext.java:95)
at oracle.adfinternal.view.faces.renderkit.rich.RichRenderKit$CreateARC.encodeBegin(RichRenderKit.java:479)
at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:168)
at oracle.adfinternal.view.faces.lifecycle.ResponseRenderManager.runRenderView(ResponseRenderManager.java:52)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._renderResponse(LifecycleImpl.java:1264)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executeRenderResponse(LifecycleImpl.java:1107)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:348)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:258)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:651)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:286)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:260)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:137)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:350)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:25)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:207)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:105)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:529)
at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:74)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:529)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:354)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:232)
at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at oracle.adf.share.http.ServletADFFilter.doFilter(ServletADFFilter.java:77)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:169)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:207)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at viewsatapp.filter.SessionExpiryFilter.doFilter(SessionExpiryFilter.java:77)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at oracle.security.jps.ee.http.JpsAbsFilter$3.run(JpsAbsFilter.java:172)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:650)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:110)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilterInternal(JpsAbsFilter.java:273)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:147)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:94)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:248)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:32)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3701)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3667)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:326)
at weblogic.security.service.SecurityManager.runAsForUserCode(SecurityManager.java:197)
at weblogic.servlet.provider.WlsSecurityProvider.runAsForUserCode(WlsSecurityProvider.java:203)
at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:71)
at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2443)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2291)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2269)
at weblogic.servlet.internal.ServletRequestImpl.runInternal(ServletRequestImpl.java:1703)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1663)
at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:272)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:644)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:415)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:355)
<oracle.adf.view> <RichExceptionHandler> <_logUnhandledException> <ADF_FACES-60098:Faces lifecycle receives unhandled exceptions in phase RENDER_RESPONSE 6>
java.lang.NoSuchMethodError: org.apache.myfaces.trinidadinternal.agent.AgentImpl$AgentType.valueOfDisplayName(Ljava/lang/String;)Lorg/apache/myfaces/trinidadinternal/agent/AgentImpl$AgentType;
at oracle.adfinternal.view.faces.renderkit.rich.RichAdfRenderingContext._getloopbackCapabilities(RichAdfRenderingContext.java:484)
at oracle.adfinternal.view.faces.renderkit.rich.RichAdfRenderingContext._getCapabilityDeltas(RichAdfRenderingContext.java:444)
at oracle.adfinternal.view.faces.renderkit.rich.RichAdfRenderingContext._calculateAgent(RichAdfRenderingContext.java:383)
This post has been answered by PrakashC on Mar 24 2022
Jump to Answer

Comments

Dom Brooks

Your expectations are wrong.

Yes binds are peeked to get some specific information but the execution plan has to assume that the bind values can/will change.

When you are using a literal, the optimizer can eliminate parts of the plan as irrelevant - i.e. we can see that 0=1 is always false and can eliminate part of the sql.

When you are using binds you need a shareable execution plan which is good for all possible supplied binds so 0 = :2 has to be a runtime evaluation in the plan.

1 person found this helpful
fjfranken

Hi Dom,

Thanks for the response.

What you are describing is exactly what I am expecting.

Even if, in the first run, the optimizer does "peek" only the values for partnumber & member_id, I understand that the execution plan would result in a Full Tablescan as the binds for the 0=:1 are unknown and that part of the query has to be taken into account.

However with every next run ( and there are thousands of value-sets in the batch), I would expect that the optimizer with then use all values available and change the execution plan, or create a new one for this situation.

I've been looking at a document of Arup Nanda where Adaptive Cursor Sharing results in execution plans changing, or the generation of multiple execution sub-plans, each one suitable for the related set of binds.

The doc: http://www.oracle.com/technetwork/articles/sql/11g-sqlplanmanagement-101938.html

Or am I missing something here??

Thanks again

michaelrozar17

I may be missing something but I'm quite unable to understand on why you think that Optimizer shouldn't chose different plan for same sql that uses bind variables. This is the reason Adaptive Cursor Sharing was introduced. Check the SQL in question is IS_BIND_AWARE and IS_BIND_SENSITIVE via V$SQL view. If they are Y then optimizer has chosen to use different plan for different bind values. Read https://blogs.oracle.com/optimizer/entry/why_are_there_more_cursors_in_11g_for_my_query_containing_bind_variables_1 and also ensure that statistics on the table are up-to-date

Dom Brooks

ACS might kick in over time...

But you have to have suboptimal executions with different bindsets for the optimizer to recognise that there might be a better plan for a particular bindset.

What you can't have is execution plans which are completely invalid for a particular bindset.

So, in that respect, comparing the plan when you provide a set of literals and comparing a plan where you have binds does not make sense.

On second thoughts, ACS might not kick in.

Bind sensitivity should occur when the bind vairable has been peeked AND the column referring to bind has a histogram - in this case there is no column referring to the :2 and :4.

1 person found this helpful
Mark D Powell

fjfranklen, >> I would expect that the optimizer would "PEEK" all available variables to determine the best execution plan.<<

- -

I just want to add to Dom's pretty good replies to your post that when just talking about bind variable peeking Oracle peeks once on the first execution of a query and then uses that plan for all subsequent executions.  There are events that will cause a re-peek.

- -

HTH -- Mark D Powell --

1 person found this helpful
fjfranken

I suddenly found THE solution.


I created an extra Index that also contains the selected column. Now the optimizer decides that accessing the Index is sufficient, thus bypassing tableaccess and possible (non existing) null values

The batch that ran for 25,5 hrs yesterday now finished in less than 5 minutes !!!



Thanks for all the Input

Jonathan Lewis
Answer

That's an interesting question - at first sight it looks as if adaptive cursor_sharing ought to be able to address your problem.

However, I think the optimizer has to produce a plan that will ALWAYS produces the right result regardless of the actual values supplied. Since your query could require the optimizer to find rows where memberid and partnumber are both null, and you index (presumably) doesn't have a mandatory column in it then the only legal execution plan is the full tablescan.

Depending on the relative frequency of values, and the number of nulls for each column, you might find that the generic solution (rather than the index-only solution that you got for this specific query) is to create an index on (partnumber, member_id, 1) or (member_id, partnumber, 1) then the optimizer could use CONCATENATION to pick one of two alternative paths.

Regards

Jonathan Lewis

Marked as Answer by fjfranken · Sep 27 2020
fjfranken

Thanks Jonathan,

Your solution of creating the Index on (partnumber, member_id, 1) forces the optimizer in the direction we need.

I executed :

create  unique index cat_test on catentry(partnumber, member_id,1)

nologging  noparallel compute statistics;

and now the execution plan shows:

Execution Plan

----------------------------------------------------------

   0       SELECT STATEMENT Optimizer Mode=ALL_ROWS (Cost=6 Card=2 Bytes=46)

   1    0    CONCATENATION

   2    1      FILTER

   3    2        TABLE ACCESS BY INDEX ROWID WCSADMIN.CATENTRY (Cost=2 Card=1 Bytes=23)

   4    3          INDEX RANGE SCAN WCSADMIN.CAT_TEST (Cost=2 Card=1)

   5    1      TABLE ACCESS BY INDEX ROWID WCSADMIN.CATENTRY (Cost=4 Card=1 Bytes=23)

   6    5        INDEX RANGE SCAN WCSADMIN.I0000064 (Cost=3 Card=1)

The CAT_TEST index being "your" index,

The I0000064 Index being the Index on (partnumber, member_id) that already existed and of which we wanted it to be used ;-)

Your solution will actually be better than the Index I created, as this one also supports multi-column selects

Thanks

Jonathan Lewis

I tried to modify my answer moments after I published it - but I couldn't retrieve it (even though the inbox said it was the latest item that I had posted).

Just a tiny change - if you use 0 instead of 1 as the extra column on the index then the index will be slightly smaller since 0 is stored internally as 0x80, which 1 is stored as C1 02.

Regards

Jonathan Lewis

fjfranken

And that is how you recognize a super DBA !!  

Thanks Jonathan

Jonathan Lewis

I've just noticed you created the test index as unique:

  create  unique index cat_test on catentry(partnumber, member_id,1)


Presumably because the current index is unique; but a unique index allows multiple entries where all columns are null - which means this new index could raise a "uniqueness" data-entry error where the old index doesn't. To be safe you need this index to be non-unique.


If you want to drop the other index (if the columns are in the same order it's redundant) you could still create this index as a non-unique index then create a unique constraint based on just the first two columns.


Regards

Jonathan Lewis


fjfranken

Jonathan,

Just one final question.

I still don't understand the mechanism of why the optimizer does now use the Index when that extra literal column ( the 1 or the 0 ) is added.

Can you elaborate on this?

Thanks

Frank-Jan

GS613

Both columns in your index (partnumber and member_id) can be null.

In order for your query to use an index the entry in the index needs to exist - if both columns are null then there will be no index entry.

An index entry does not exist if ALL the fields in the index are null.

In order to ensure that those records for nullable columns are included in the index a work-around is to add a literal to the index key - in this case a 0. Now one of the fields in the index will always have a value (0 is not null) and therefore will be indexed and can be accessed as such.

Correct me if I am wrong, Jonathan!

GS613

To add to my answer:

there is a explanation in the following article - read from code listing 3.

Ask Tom: On Constraints, Metadata, and Truth

Jonathan Lewis

Gary,

No correction needed.

(Though someone may eventually get the urge to point out that bitmap indexes and cluster indexes are allowed to hold entries for completely column sets)

Regards

Jonathan Lewis

1 person found this helpful
1 - 15

Post Details

Added on Mar 11 2022
#adf, #application-development-in-java, #jdeveloper, #jdeveloper-and-adf
9 comments
272 views