Accesing protectred URIs on Solaris (sparcv9) with WLS 10.3.5 and Apache2

Question

I had started to ask questions about this on another thread of mine, but since I had listed that one as answered and this being different from the original question on that thread...I felt it better to create its own thread.
Problem Description: Environment Details:
- Server1 -- 64 bit Intel RHEL5
Fusion Middleware Identity Management - 11.1.1.2
WLS 10.3.2
ODSM,OID,OVD
DB 10.2.0.4
- Server 2 32-bit Intel RHEL5
OAM 10.1.4.3
OHS 11.1.1.2
- Server 3 64-bit SparcV9 Webhost -- deployed app as protected uri
WLS 10.3.5
Apache2
Webgate 10.1.4.3
We believe we have completed everything in regard to being able to include a solaris host in our list of hosts that are tied to OAM. We have installed webhost with XP and RHEL5.6 successfully using OHS 11.1.1.2. This is the first time creating a webhost on Sparc. The webgate was created and software installed, the deployed app protected, etc... Everything that we have done for Linux and XP in the past we have done for this Sparc host. The only differences are the SUN OS, Apache2, and WLS 10.3.5. I believe those are all acceptable for these Oracle products and versions.
When we try to access the Sparc's protected uri... nothing happens. The browser stays blank... the url does not change to display the oamsso login.html (as the other installs do)... nothing is returned... no error, no remarks, ... just a blank browser.
Doing an apachectl -l I receive the following:
Compiled in modules:
core.c
prefork.c
http_core.c
mod_so.c
So mod_so.c is included.
If I go directly to the protected uri through 7001 instead of the 8890 -- the port httpd.conf has configured to listen on -- the page displays. If I open the oamsso/login.html using 8890... it displays. But if I use 8890 to bring up the protected uri... as described above nothing displays.
One other thing, since the Sparc host is "headless" -- as described by our SysAdmin... no access directly through the sun console and no gui access via the sun host since there is no sun console just the server -- we have to access the gui via a browser on the same network. The browser is actually on the OAM host.
From apache2 error_log on SUN host:
15-7-2011 14:35:51Sending message: 0 13
protocol=NAP version=3 oldest=1
15-7-2011 14:35:51Received message: 0 13
protocol=NAP version=3 oldest=1
15-7-2011 14:35:51Sending NMP STS negotiation message: 0 0
sts=open
15-7-2011 14:35:51Received NMP STS negotiation message: 0 0
sts=open
15-7-2011 14:35:51Sending message: 0 14
cm=mtisunfireHost_AG challenge=b516f1a00c2a95ee
15-7-2011 14:35:51Received message: 0 14
cm=access_svrid1 challenge=95520d6315ad3865 st=ma%3d25 rt=1
15-7-2011 14:35:51Sending message: 0 15
response=531be0a851cb2773c90aa0c91d9f779c
15-7-2011 14:35:51Received message: 0 15
response=2b62c22a9458e962c35d8d7d358f4fc1 st=ma%3d25 rt=1
15-7-2011 14:35:51Sending message: 0 8
cm=mtisunfireHost_AG ct=0 version=3
15-7-2011 14:35:51Received message: 0 8
ci=id%3dmtisunfireHost_AG%20maxConnections%3d1%20debug%3d0%20maxSessionTime%3d24%20sleepFor%3d60%20security%3dopen%20failoverThreshold%3d1%20aaaTimeoutThreshold%3d%20cookieSessionTime%3d3600%20maxCacheElems%3d100000%20cacheTimeout%3d1800%20configLastUpdateTime%3d1310754351%20preferredHost%3dmtisunfire:8890%20state%3dEnabled%20primaryCookieDomain%3d%20idleSessionTimeout%3d3600%20accessClientPasswd%3d02434564584046435641510409%20primaryServer1%3dhost%253dirsam-oam.dchc.smil.mil%2520port%253d8887%2520numOfConnections%253d1%20denyOnNotProtected%3d0%20cachePragmaHeader%3dno-cache%20cacheControlHeader%3dno-cache%20ipValidation%3d1 st=ma%3d25%20mi%3d2%20sg%3d32%20sm%3d rt=1
[Fri Jul 15 14:35:52 2011] [notice] child pid 18581 exit signal Segmentation fault (11)
[Fri Jul 15 14:35:58 2011] [notice] child pid 18582 exit signal Segmentation fault (11)
[Fri Jul 15 14:36:01 2011] [notice] child pid 18583 exit signal Segmentation fault (11)
[Fri Jul 15 14:36:04 2011] [notice] child pid 18585 exit signal Segmentation fault (11)
[Fri Jul 15 14:36:07 2011] [notice] child pid 18586 exit signal Segmentation fault (11)
[Fri Jul 15 14:36:11 2011] [notice] child pid 18590 exit signal Segmentation fault (11)
[Fri Jul 15 14:36:12 2011] [notice] child pid 18591 exit signal Segmentation fault (11)
[Fri Jul 15 14:36:14 2011] [notice] child pid 18592 exit signal Segmentation fault (11)
[Fri Jul 15 14:36:15 2011] [notice] child pid 18593 exit signal Segmentation fault (11)
[Fri Jul 15 14:36:16 2011] [notice] child pid 18594 exit signal Segmentation fault (11)
[Fri Jul 15 14:38:35 2011] [notice] child pid 18595 exit signal Segmentation fault (11)
[Fri Jul 15 14:38:38 2011] [notice] child pid 18596 exit signal Segmentation fault (11)
I believe that apache is currently setup correctly at this point, but cannot understand what we are missing.

Answer 1

I would say that OAM does support Apache (according to the certified Apache versions and OS's). However, there are so many distributions out there and it can be configured with countless options, be compiled with a number of different compilers, and include any number of modules that some compatibility issues are bound to arise. The Solaris distribution - also Oracle - is a case in point. I have also encountered issues with the Apache version bundled with some Linux versions (for different reasons than the Solaris bundle) for which the easiest solution has also been to download and build from source. I would imagine that is the reason for what you were told about support for generic Apache, though of course I do not know the context.
Regards,
Colin