-
Bug
-
Resolution: Done
-
Critical
-
EAP_EWP 5.1.1 ER2
-
None
-
rhel, solaris sparc64, i386
-
Rsolved with
MODCLUSTER-239. Verified on EWS 1.0.2 CR5 (mod_cluster MOD_CLUSTER_1_0_10_GA_CP01 )
The behavior stated in the JBPAPP-6451 and commented on by rhn-engineering-jclere takes place in EAP 5.1.1 ER2 as well.
Solaris 10 SPARC64
- Client's log (500 Internal Server Error)
34-eap-5x-mod_cluster-solaris10-sparc64-failover-console.zip - Httpd error_log
34-eap-5x-mod_cluster-solaris10-sparc64-failover-error_log.zip - Httpd access_log
34-eap-5x-mod_cluster-solaris10-sparc64-failover-access_log.zip - Httpd configuration
34-eap-5x-mod_cluster-solaris10-sparc64-failover-config.zip
Solaris 9 i386
- Client's log (500 Internal Server Error)
10-eap-5x-mod_cluster-solaris9-i386-failover-httpd-client.zip - Httpd logs (access and error)
10-eap-5x-mod_cluster-solaris9-i386-failover-httpd-logs.zip - Httpd configuration
10-eap-5x-mod_cluster-solaris9-i386-failover-httpd-conf.zip
Solaris 9 SPARC64
- As above...
RHEL 6 x86_64
- Client's log, Httpd logs and confs as well as Jboss configurations and logs linked below:
18-eap-5x-mod_cluster-rhel6-x86_64-failover.zip
Based on the experience with EAP 5.1.1 ER1, I assume that the RHELx would be all the same...
- is blocked by
-
-
- Closed
-
