| Summary: | Clustering the Gemini.Web cannot be done because of the missing import packages | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [RT] Gemini.Web | Reporter: | Violeta Georgieva <milesg78> | ||||||
| Component: | unknown | Assignee: | Glyn Normington <glyn.normington> | ||||||
| Status: | CLOSED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | glyn.normington, zteve.powell | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | 1.1.0.M04-incubation | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows XP | ||||||||
| See Also: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=315349 | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Violeta Georgieva
Created attachment 176870 [details]
tomcat-server.xml with cluster configuration
Violeta, Gemini.web depends upon the tomcat and catalina bundles version 6.0.20.S2-r5956 which are all resolved from the Enterprise Bundle Repository. To change the meta-data of these bundles is now not possible. The versions of these bundles we use have been specially created for two reasons: one is that the meta-data required to be OSGi-deployable is not present in the originals (the raison-d'etre of the EBR) and two is that to embed tomcat in a project like Gemini.Web (and Virgo -- G.W's sister project) requires some adjustments to its base configuration. This is the reason for the S2-r5956 qualifier. We are in the process of upgrading the version of tomcat (and related bundles) which Gemini.Web depends on, and this involves putting newer bundles in the EBR. We therefore have some control over what appears in the meta-data for those new bundles. When the team leader (Glyn Normington) is available (presently he is on holiday) I will be consulting him on the necessary steps to take. Ref to CQ on Virgo (https://dev.eclipse.org/ipzilla/show_bug.cgi?id=4398) and CQ on Gemini.Web (https://dev.eclipse.org/ipzilla/show_bug.cgi?id=4399. [Bug 315349] appears to be related to this issue. Thanks Steve! I played further with the cluster scenario and I have one more proposal. We can think about making com.springsource.org.apache.catalina.ha.springsource and com.springsource.org.apache.catalina.tribes.springsource as fragment bundles to com.springsource.org.apache.catalina.springsource I will look forward to your comments. Regards Violeta Part of the Tomcat 6.0.29 upgrade. I am trying to reproduce the failure before investigating proposed solutions. Unfortunately, I cannot download the tomcat-server.xml attachment. Please could you attach a zip of it? Also please could you spell out how you provide this file to Gemini Web to recreate the problem. Thanks. Created attachment 178312 [details]
tomcat-server.xml with cluster configuration
Hi Glyn,
Here is the zipped tomcat-server.xml file.
On my Gemini.Web installation it is located:
<Gemini-Web-Home>/config/tomcat-server.xml
Regards
Violeta
Thanks Violeta. I can now recreate the problem. I have tested the fragment approach and it seems to work very nicely. The next step is to cut a milestone of Gemini Web to include this level. Milestone 4 is created and will be publicised tomorrow. Milestone 4 is available from the Gemini Web download page. Hi Violeta Please would you close this bug if you are happy with the outcome. Thanks, Glyn Thanks |