Skip to main content

ADF: weblogic cluster endless loop 401 Unauthorised _afrLoop infinite loop AGAIN

Finally fixed the third incarnation of this problem - when we deployed onto our dev cluster and our application deployed fine but when the login page was accessed the app went into an infinite loop. NOTE: Deploying onto the Admin server worked perfectly.

In the access logs you see 302 http codes with _afrLoop parameters (302 - redirect).

Really could not figure this one out. I added failover and clustering removed them. Reconfigured the security. Created a test app with one page used weblogics default security provider but still NOTHING. I even setup a cluster on my machine and everything worked (Note: I did not setup our dev cluster)

So in desperation I check the system-jazn-data.xml file deployed on weblogic an lo and behold none of my application security configurations where setup in the file. I stopped everything and added what I had on my local cluster to the system-jazn-data.xml and everything just works. I need to find out what in our dev configuration is causing the system-jazn-data.xml file not to be updated and will post here when found.

Hope this save someone some time becuase it wasted a LOT of my time.

Final Word: Always a good idea to read the documentation:
 http://docs.oracle.com/cd/E12839_01/core.1111/e10043/addlsecfea.htm#CFHFAIGE

Under the heading 7.3.1 Deploying to a Test Environment

Other Considerations

When deploying an application to multiple managed servers, be sure to include the administration server so that data is migrated as expected.

This fixed it for me.

Comments

Popular posts from this blog

ADF Encountered deferred syntax #{ in template text.

OracleJSP error: oracle.jsp.parse.JspParseException:  Error: Encountered deferred syntax #{ in template text.  If intended as a literal, escape it or set directive  deferredSyntaxAllowedAsLiteral This normally happens when you have some tag lib dependancy problems but this was  not the case for me... My problem: For some reason my model project had web stuff in it(public html etc)  so I had to remove the public html stuff from my project and manually edit the Model.jpr project file and remove the tag lib entries at the bottom o the file. Go figure.    

JBO-25013: TooManyObjectsException

oracle.jbo.TooManyObjectsException: JBO-25013: Too many objects match the primary key oracle.jbo.Key[Key null ]. Ok so for you it may be trying to insert a duplicate record this should explain your problem (also check trigger they could be the cause.) NOTE: You can also try to create a new duplicate EO if you have a page with two VO's using the same EO. This could sort your problems. For me I needed to add a launch listener on my LOV and clear the cache of my vo. LOV <af:inputListOfValues id="NameId" popupTitle="#{bindings.Name.hints.label}" value="#{bindings.RolName1.inputValue}" label="#{bindings.RolName1.hints.label}" model="#{bindings.RolName1.listOfValuesModel}" required="#{bindings.RolName1.hints.mandatory}" columns="#{bindings.RolName1.hints.displayWidth}" shortDesc="#{bindings.RolName1.hints.tooltip}" launchPopupListener="#{backingBeanScope.backingBean.launchPop

MANIFEST.MF merge JDeveloper for an executable jar

Goto your project > properties. Then click on deployment in the menu. Edit or add a jar deployment profile. Fill in the details under jar options (select Include manifest and give it a main class name) Also remember that the merge functionality only works with a BLANK line at the end of the merge file. REALLY this caught me. My merge file contents: Class-Path: commons-codec-1.3.jar [...empty line here CRLF...]