Bug 899200 (JBEWS-216)
| Summary: | EWS - ssl on solaris10 sparc broken | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Web Server 1 | Reporter: | Aleksandar Kostadinov <akostadinov> | ||||||||
| Component: | unspecified | Assignee: | Permaine Cheung <pcheung> | ||||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||||||
| Severity: | urgent | Docs Contact: | |||||||||
| Priority: | urgent | ||||||||||
| Version: | EWS 1.0.1 | ||||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | EWS 1.0.1 | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| URL: | http://jira.jboss.org/jira/browse/JBEWS-216 | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: |
solaris10 sparc64
|
|||||||||
| Last Closed: | 2010-02-16 15:58:00 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Aleksandar Kostadinov
2010-02-05 16:56:53 UTC
Mladen, please take a look. Thanks! If it's not observed on other platforms (Solaris especially) I presume it's a missing Solaris update of some kind. There are also some reports that this doesn't happen if using IE7, so it might be that IE7 doesn't treat this as an error Tried the same from dev92 and from a rhel machine: wget https://dev92/ --14:15:15-- https://dev92/ => `index.html' Resolving dev92... 10.16.88.161 Connecting to dev92|10.16.88.161|:443... connected. OpenSSL: error:140943FC:SSL routines:SSL3_READ_BYTES:sslv3 alert bad record mac Unable to establish SSL connection. Also it is the same with EWS installed on a sol9-2. Odd is that the wget executable on the sol9-2 machine (actually a solaris 10 machine), is not throwing errors connecting to dev92. Wget on sol9-2 is older though 1.9. openssl version is 0.9.7 on both. But definitely it seems like a problem on the server. JBPAPP-1786 and JBPAPP-1657 - seems like we had the same with solaris10 x86 so I wonder what can we do if we are already using sun studio 12? Are we? Link: Added: This issue depends JBPAPP-1786 Link: Added: This issue depends JBPAPP-1657 Link: Added: This issue related JBPAPP-1786 Link: Added: This issue related JBPAPP-1657 Link: Removed: This issue depends JBPAPP-1786 Link: Removed: This issue depends JBPAPP-1657 Certainly not an EWS issue. I really do not understand your question. You said It works witth older wget, and doesn't with FireFox, so what do you expect me to do? Let's do some recap then: 1. which build number you are using for testing. 2. Please specify which boxes is this on (I have access to dev12 only. dev12 has SunStudo12, not sure if dev92 has, and some builds were done on that box AFAICT Attachment: Added: step1.jpg Attachment: Added: step2.jpg Attachment: Added: step3.jpg So logged to dev92 $> cd /opt $> sudo wget http://hudson.qa.jboss.com/hudson/job/RHATews-1-solaris10-sparc/181/artifact/rhews/hudson/artifacts/bin/RHATews-1.0.1_0-solaris10-sparc64.zip $> sudo unzip -q RHATews-1.0.1_0-solaris10-sparc64.zip $> cd redhat/ews/etc $> sudo ./.postinstall $> sudo vi httpd/conf/httpd.com changed Listen 80 to Listen 8880 $> sudo vi httpd/conf.d/ssl.conf changed Listen and VirtualHost to 8843 from 443 $> cd ../sbin $> sudo ./apachectl start voila! Please close this case once and for all Thanks Thanks, I can confirm that with this build ssl is working very well. Has the build environment been updated between the old and current build or you implemented some fix? Anyways, this can now really get closed. Build you were using for testing probably came from dsp-sol10-2-sparc box. This box AFAICT doesn't have the needed build tools, so it only gave the partial build. In next version I'll make sure the build doesn't finish if one of the components fails. verified in CR2 |