Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Gemini » WAB not reacheable after deployment on Gemini WEB(Unable to access deployed WAB by Gemini WEB on a standalone Tomcat)
WAB not reacheable after deployment on Gemini WEB [message #1792963] Thu, 26 July 2018 15:19 Go to next message
Abba Soungui YOUNOUSS is currently offline Abba Soungui YOUNOUSSFriend
Messages: 2
Registered: July 2018
Junior Member

I am trying to use Gemini WEB on a standalone Tomcat (not the embedded). I successfully deployed Gemini WEB on Tomcat, using servlet bridge. Now, I can deploy WAB using the webbundle scheme and start the bundles, however I cant reach them.

After the deployment of Equinox on Tomcat, I can access to the framework using this URL : http://localhost:8080/bridge. The Web-ContextPath of the bundle that I am deploying is /bundle, so my WAB should be accessible at http://localhost:8080/bridge/bundle, but it doesn't work. I receive a HTTP 404 error, with the message ProxyServlet: /bundle The requested ressource is not available.

I've searched on Internet, but there aren't so much informations about Gemini WEB's deployment in a servlet container, most of them talk about using the embedded Tomcat. I tested my WEB with Virgo, and it work, so I guess that my WAB is OK, but there is a missing bundle or a bad configuration in my deployment.

So I have some questions:
1 - Is Gemini WEB meant to be installed in a standalone servlet container, or is it mandatory to use the embedded Tomcat.
2 - If it's possible, can you tell me if I'm missing something.

Here is the output of the command ss in Equinox shell:

osgi> ss
"Framework is launched."

id State Bundle
0 ACTIVE org.eclipse.osgi_3.13.0.v20180409-1500
1 ACTIVE org.eclipse.equinox.console_1.3.0.v20180119-0630
2 ACTIVE org.eclipse.equinox.common_3.10.0.v20180412-1130
3 ACTIVE org.eclipse.equinox.registry_3.8.0.v20180426-1327
4 ACTIVE org.apache.felix.gogo.shell_1.0.0.v20170914-1324
5 ACTIVE org.apache.felix.gogo.runtime_1.0.6.v20170914-1324
6 ACTIVE org.apache.felix.gogo.command_1.0.2.v20170914-1324
7 RESOLVED org.eclipse.equinox.servletbridge.extensionbundle_1.3.0
8 ACTIVE org.eclipse.equinox.http.servletbridge_1.1.0.v20180120-0803
9 ACTIVE org.eclipse.equinox.http.registry_1.1.500.v20171221-2204
10 ACTIVE javax.servlet_3.1.0.v201410161800
11 ACTIVE org.eclipse.equinox.http.servlet_1.5.0.v20180501-1936
12 ACTIVE org.eclipse.osgi.services_3.7.0.v20180223-1712
13 ACTIVE org.eclipse.osgi.util_3.5.0.v20180219-1511
14 INSTALLED org.apache.catalina.tribes_8.5.16
15 INSTALLED org.apache.coyote_8.5.16
16 ACTIVE javax.servlet_3.1.0.20170128
17 ACTIVE com.springsource.javax.activation_1.1.1
18 ACTIVE org.eclipse.virgo.util.parser.manifest_3.6.3.RELEASE
19 INSTALLED org.apache.jasper_8.5.16
20 ACTIVE org.eclipse.virgo.util.osgi_3.6.3.RELEASE
21 INSTALLED org.apache.tomcat.util_8.5.16
22 INSTALLED org.apache.tomcat.util.scan_8.5.16
23 RESOLVED org.slf4j.nop_1.7.2.v201212060727
24 ACTIVE org.apache.juli_8.5.16
25 ACTIVE org.apache.el_8.5.16
26 ACTIVE javax.mail_1.4.0.v201005080615
27 ACTIVE javax.transaction_1.1.0.v201205091237
28 ACTIVE org.eclipse.virgo.util.osgi.manifest_3.6.3.RELEASE
29 ACTIVE org.apache.tomcat.jni_8.5.16
30 ACTIVE org.eclipse.virgo.util.common_3.6.3.RELEASE
31 ACTIVE org.slf4j.api_1.7.2.v20121108-1250
33 ACTIVE org.eclipse.jdt.core.compiler.batch_3.11.0.v20150602-1242
34 ACTIVE org.apache.tomcat.api_8.5.16
35 ACTIVE javax.xml.rpc_1.1.0.v201005080400
36 ACTIVE org.eclipse.virgo.util.math_3.6.3.RELEASE
37 ACTIVE javax.servlet.jsp_2.3.0.20170128
38 ACTIVE javax.persistence_2.1.0.v201304241213
39 ACTIVE javax.annotation_1.2.0.v201401042248
40 ACTIVE javax.xml.soap_1.3.0.v201105210645
41 ACTIVE org.eclipse.virgo.util.io_3.6.3.RELEASE
42 INSTALLED org.apache.tomcat.websocket_8.5.16
43 ACTIVE javax.el_3.0.0.20170128
44 ACTIVE javax.ejb_3.1.1.v201204261316
45 INSTALLED org.apache.catalina.ha_8.5.16
46 ACTIVE javax.websocket_1.1.0.20170128
47 INSTALLED org.apache.catalina_8.5.16
48 ACTIVE org.eclipse.gemini.web.extender_3.0.3.RELEASE
49 ACTIVE org.eclipse.gemini.web.core_3.0.3.RELEASE
50 INSTALLED org.eclipse.gemini.web.jaspic.fragment_3.0.3.RELEASE
51 ACTIVE mybundle_1.0.0.qualifier
Re: WAB not reacheable after deployment on Gemini WEB [message #1840730 is a reply to message #1792963] Thu, 22 April 2021 21:46 Go to previous messageGo to next message
Pablo  eltrán is currently offline Pablo eltránFriend
Messages: 20
Registered: November 2014
Junior Member
We plan to follow the same approach. Did you succeed in running Gemini Web under the Servlet bridge?
Re: WAB not reacheable after deployment on Gemini WEB [message #1841445 is a reply to message #1840730] Mon, 17 May 2021 08:37 Go to previous messageGo to next message
Abba Soungui YOUNOUSS is currently offline Abba Soungui YOUNOUSSFriend
Messages: 2
Registered: July 2018
Junior Member
No, I finally gave up since I already wasted too much time trying to make it work and I didn't got response to know if it's even possible.
Re: WAB not reacheable after deployment on Gemini WEB [message #1841516 is a reply to message #1841445] Wed, 19 May 2021 17:22 Go to previous message
Pablo  eltrán is currently offline Pablo eltránFriend
Messages: 20
Registered: November 2014
Junior Member

The problem seems like Gemini Web (when deployed under the servlet bridge) still starts its own Tomcat server instance listening to a TCP port (8080 default).

In your case, as you are running Tomcat on the same TCP port than the Gemini Web's default (8080) probably Gemini Web is not properly started up due the port number conflict. So you must change one of them: the Host Tomcat or the Gemini Web (embedded Tomcat) TCP port.

In the initial part of this recorded session (animated gif)...


...Gemini Web is installed under the Servlet Bridge that is reachable at:


The Web-ContextPath of the WAB is /test so it would be expected that the /hello servlet would be accessible at:


which returns a 404 Not found Error. Instead Gemini Web starts its own Tomcat instance as mentioned above and the WAB is reachable at:


As you see, this is useless because the user logged in against application deployed in the host Tomcat (http://localhost:2990/jira), so the user session is missing when you access via Gemini Web (http://localhost:8080)

If you are interested, the second part of the "video", it shows the same WAB example running on PAX-WEB under the same servlet bridge, that almost works: the WAB is detected and the servlet registered (like it happens with Gemini Web) but the Web-ContextPath ignored because a bug.

It would be nice if Gemini Web supports the Servlet Bridge.

This might seem a bit strange architecture but it would be really useful for the real World where reality overcomes software architects' imagination.

Best regards,
Previous Topic:blueprintContainer bean not found
Next Topic:Status of Gemini DbAccess
Goto Forum:

Current Time: Mon Dec 11 23:32:53 GMT 2023

Powered by FUDForum. Page generated in 0.02826 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top