[jira] Commented: (STR-3089) Unable to redirect with aliased server name fronting request

["Paul Benedict (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/struts/browse/STR-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42075 ] 

Paul Benedict commented on STR-3089:
------------------------------------

Sounds like it is a setup problem with production. The fronted webserver should be a proxy which forwards the request to the application server. So that when the target issues a redirect, IAS should rewrite the redirect. If thisn't happening, perhaps you should try installing Apache HTTPD in front and see if you get a different result.

I am surprised that you haven't mimicked this yet on developer boxes. The developer should be hitting an HTTP server which forwards to an application server. This would help diagnose the problem. Definitely get the problem showing on the desktop too.

> Unable to redirect with aliased server name fronting request
> ------------------------------------------------------------
>
>                 Key: STR-3089
>                 URL: https://issues.apache.org/struts/browse/STR-3089
>             Project: Struts 1
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.1
>         Environment: IBM Server, Linux (Red Hut), Oracle Application Server 10.1.0.2, Eclipse 3.2 IDE
>            Reporter: Hayrol Reyes
>            Assignee: Paul Benedict
>
> We are having a rare problem with a new application. This application use Struts 1.1 and Hibernate 3 over a OraclaeAS 10g (10.1.0.2). The Applicatión works very well in the developer's OAS, but doesn't in the production's OAS ...it's supposed that both OAS use the same configuration.
> The problems occurss when the application need to do a ActionForward (redirect true), after a simple update/insert into the DB (with Hibernate). the flow is as follow:
> 1).- The "show_Product.do" is launched and it goes well and show the Product.jsp (with the show part actived) .
> 2).- The user press the "Update" buttom, then the "edit_Product.do" action is executed and the Product.jsp is showed (with the edit part actived).
> 3).- The user modify the product info and press the "Update" buttom, then the "edit_Product.do" action is executed with the parameter "save" ..... then the action class do calls to "save" process of the ProductForm and the next ActionForward is configured to point to "show_Product.do" , afteer the commit to the DB the action es executed and "show_Product.do" show the Product.jsp with relevant changes included.
> All this normal aproach works very well in our developers environment IAS but doesn't in the produccion IAS. In the production environment the application comimited the changes but the last ActionForward (show_Product.do) is not executed and the browser show a "Error Page" related to the conecction problems, however the changes are commited correctly in the DB.
> The only diference between both IAS are that the developer environment use a host like: http://servername:7777/context/ while the production environment use: http://www.host.bla/context .... and internaly it's supposed to be pointing to 7778 port of the IAS server (where the app is installed). Both server can be reached through the intranet.
> The other diference (with no incidence I guess) is the production IAS is accesing a RAC Oracle DB 10g (2 instances) while the developer IAS is accesing a single Oracle DB 10g.
> Some body have a clue about what is happing on he producction IAS?
> I know that it looks like a Oracle AS problem, but we can't found any help nor support, and the worse is that we have not a error to walk around. We only get a Erorr page and no other information neither app log nor IAS log.
> Please if somebady had experiences with this type of issue, I will apreciate the help.
> Regards,
> Hayrol Reyes

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.