Hi I am sorry. This problem is on the application side of our team and they asked me to look into possible Apache issues.
Basically, they have submitted a case with Oracle, and they responded with the following: ****** Oracle Support - May 20, 2010 10:21:59 AM GMT-04:00 Comments -------- === ODM Knowledge Management === Knowledge content not created because this issue is customer specific and would not benefit anyone else. Oracle Support - May 20, 2010 10:21:17 AM GMT-04:00 Comments -------- === ODM Solution / Action Plan === Do not use the reverse proxy to access Primavera web services. Use the FQDN of the app server to access. Oracle Support - May 20, 2010 10:20:11 AM GMT-04:00 Comments -------- === ODM Proposed Solution Justif === We do not certify the use of a reverse proxy. While this configuration may in fact work we only support the product to the extent we can reproduce the issue on a supported configuration. Oracle Support - May 20, 2010 10:17:42 AM GMT-04:00 Comments -------- === ODM Proposed Solution === Do not use reverse proxy with app server. Oracle Support - May 20, 2010 10:17:14 AM GMT-04:00 Comments -------- === ODM Cause Justification === When accessing without using the reverse proxy, even if there is a significant delay it will process. With reverse proxy it will times out quickly. Oracle Support - May 20, 2010 10:16:16 AM GMT-04:00 Comments -------- === ODM Cause Determination === Apache reverse proxy timing out. Oracle Support - May 20, 2010 10:15:42 AM GMT-04:00 Comments -------- === ODM Issue Verification === Verified 502 Proxy error displayed while working in application. As far as the Timeout/Proxy error goes, we have found through our research that this was actually a bug in Apache (bug 37770) so it might be worth exploring with Apache to see if it can be resolved. We do not support an Apache configuration but if you work with them directly you may be able to get your reverse proxy working correctly. ***** I would like to understand if this bug 37770 which they reference does in fact exist in Apache 2.0.59 or not? I read the bug report on this and it seems the bug started in 2005, however Apache 2.0.59 was released in 2007. Since this issue is only happening intermittently -- according to a user it happens about 30% of the time -- would it be due to this bug, or could this be more of an issue on the application itself? I just want to try to get some opinions on this so we can look into possible resolutions. Tuyen.
