Bug 959993
| Summary: | Show "No Java compiler available" when access jbossews app after update jbosseap6.1 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | xjia <xjia> | ||||||
| Component: | Containers | Assignee: | Brenton Leanhardt <bleanhar> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 1.1.1 | CC: | libra-onpremise-devel, lmeyer, pruan, wdecoste, xtian | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: |
Cause:
With both JBoss EAP and JBoss EWS 1 channels enabled, the version of Tomcat installed was incompatible with JBoss EWS 1.
Consequence:
JBoss EWS apps would fail to execute with errors like "java.lang.IllegalStateException: No Java compiler available"
Fix:
This is not so much an OpenShift bug as a requirement to manage dependencies exactly right. Follow directions in https://access.redhat.com/site/articles/316613 to get the correct Tomcat for JBoss EWS under OSE 1.1. For OSE 1.2, this still applies and the documentation and example scripts have been adjusted.
Result:
This problem should no longer occur.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-07-09 18:59:28 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
xjia
2013-05-06 11:22:04 UTC
Created attachment 744080 [details]
mysql.jsp
Created attachment 744081 [details]
mysql-connector-java-5.1.20-bin.jar
If fresh install this environment with http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-6.1.0.ER5/rpms/jbappplatform-6-x86_64-server-6-rpm/ , this issue also happens. Not seeing this problem in a devenv. JSPs compile without issue. I was able to reproduce this. The reason it wasn't happening before was because my test environment have the EAP 6.1 repo and EWS 2.0 enabled. For OpenShift Enterprise we instruct users to have only EAP and EWS 1.0 repos enabled. I'll track down exactly which package is causing the issue. When the EWS 2.0 yum repository is enabled a newer version of tomcat6 is installed: tomcat6-lib-6.0.35-29_patch_06.ep6.el6.noarch tomcat6-6.0.35-29_patch_06.ep6.el6.noarch tomcat6-servlet-2.5-api-6.0.35-29_patch_06.ep6.el6.noarch tomcat6-jsp-2.1-api-6.0.35-29_patch_06.ep6.el6.noarch tomcat6-el-1.0-api-6.0.35-29_patch_06.ep6.el6.noarch apache-commons-pool-tomcat-eap6-1.5.6-8.redhat_2.ep6.el6.1.noarch apache-commons-logging-tomcat-eap6-1.1.1-6.9_redhat_1.ep6.el6.noarch apache-commons-dbcp-tomcat-eap6-1.4-13.1.redhat_2.ep6.el6.noarch apache-commons-daemon-eap6-1.0.15-2.redhat_1.ep6.el6.noarch apache-commons-collections-tomcat-eap6-3.2.1-13.redhat_2.ep6.el6.1.noarch With those packages installed the issue goes away. EWS1 contains tomcat 5 and 6 EWS2 contains tomcat 6 and 7 The solution for now is to enable the EWS 2.0 content set and disable EWS 1.0. We are planning to update https://access.redhat.com/site/articles/316613 if it passes the tests. yum-config-manager --enable jb-eap-6-for-rhel-6-server-rpms yum-config-manager --enable jb-ews-2-for-rhel-6-server-rpms yum-config-manager --disable jb-ews-1-for-rhel-6-server-rpms yum-config-manager --disable jb-eap-5-for-rhel-6-server-rpms Verify: Follow comment #10 , I can get the expected results. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2013-1032.html |